Start LSST stream looper. Remove LSST counter subscription. #292
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have started a stream looper for LSST. It pulls messages from subscription
lsst-alerts-reservoirand publishes them to topiclsst-loopat a rate of 1 per second. This PR documents the commands used to do this.The looper is running on the VM
stream-looper, which also runs the ZTF looper. It runs inside of a screen, which unfortunately means that I am the only one who can access it. Someone else can always start a new looper inside their own screen, but then please let me know so I can properly close mine. Note that the python script is very old and could be replaced with much simpler code using pittgogle-client, but there is no need right now. The ZTF looper has been running consistently for a long time (years), so I don't expect trouble as long as there are alerts in the subscription.Unrelated, I noticed that we have a subscription
lsst-alert_avros-counter. We don't use counter subscriptions for LSST, so this PR removes that from our deploy script. I manually deleted the resource from GCP.