-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declutter main/elasticc
#165
Comments
8 tasks
troyraen
changed the title
The next PR: There are a lot of things in this repo that currently just amount to "clutter" w.r.t. our ELAsTiCC broker. So, the next PR into
Declutter Sep 20, 2022
elasticc/main
should probably get rid of everything that we're not currently using for that broker. Right now, that means the only module that stays is the Consumer... but I hope to have the BigQuery and Cloud Storage modules working shortly (I think they just need a couple of quick fixes). All modules currently in the Science pipeline have already been (condensed and) put in pittgoogle-user. We are not currently using the Metadata Collector (aka, night-conductor) -- its design probably needs to be re-thought before operating on an LSST-like stream. For now, we will be at the mercy of tom_desc, which will be collecting similar data into a Postgres database that we can query. (tom_desc will be listening to the brokers' outgoing alert streams that will contain our classifications of ELAsTiCC alerts.)elasticc/main
Merged
Closed by #166 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue elaborates on a specific step in #164: Declutter
main/elasticc
.There are a lot of things in this repo that currently just amount to "clutter" w.r.t. our ELAsTiCC broker. So, the next PR into
main/elasticc
should probably get rid of everything that we're not currently using for that broker.Right now, that means the only module that stays is the Consumer... but I hope to have the BigQuery and Cloud Storage modules working shortly (I think they just need a couple of quick fixes).
All modules currently in the Science pipeline have already been (condensed and) put in pittgoogle-user.
We are not currently using the Metadata Collector (aka, night-conductor) -- its design probably needs to be re-thought before operating on an LSST-like stream. For now, we will be at the mercy of tom_desc, which will be collecting similar data into a Postgres database that we can query. (tom_desc will be listening to the brokers' outgoing alert streams that will contain our classifications of ELAsTiCC alerts.)
The text was updated successfully, but these errors were encountered: