-
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
Use API to query ampel #1
Labels
Comments
simeonreusch
added a commit
that referenced
this issue
May 14, 2021
simeonreusch
added a commit
that referenced
this issue
May 19, 2021
simeonreusch
added a commit
that referenced
this issue
May 19, 2021
simeonreusch
added a commit
that referenced
this issue
May 19, 2021
simeonreusch
added a commit
that referenced
this issue
May 20, 2021
simeonreusch
added a commit
that referenced
this issue
May 21, 2021
simeonreusch
added a commit
that referenced
this issue
May 21, 2021
simeonreusch
added a commit
that referenced
this issue
May 21, 2021
I think this issue is not fully complete, because https://github.com/desy-multimessenger/ampel_followup_pipeline/blob/master/mmapy/gw_multi_process.py has not been ported yet. |
There is also some usage of |
Note: This is still open because the GW and GRB part of the code still needs to be ported. |
Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm always frustrated when the Ampel database access changes like every 30 seconds.
Describe the solution you'd like
Swap from using
ampel-ztf-archive
to the ampel API.All references to
ampel_client
in ampel_magic.py must be purged.Describe alternatives you've considered
Leaving things as they are. It'll require many urgent updates/hot-fixes, but will add a certain sense of adventure to our otherwise mundane lives.
The text was updated successfully, but these errors were encountered: