Release version 2.1.9 "Ghost Deer"

Git ref: fd0e474b

Checklist

Basics

1. The CI pipeline succeeded, including all unit tests and code quality checks. Link to pipeline
2. CHANGES.rst lists all significant changes since the last release. It is free from spelling and grammatical errors.
3. The latest Readthedocs documentation build passed and the latest docs are correctly rendered. Autodoc-generated API docs for tasks are shown.
4. If there is milestone for this release, then the list of issues and merge requests that have been addressed is accurate. Any unaddressed issues and merge requests have been moved to another milestone.

Playground deployment

4. Sentry does not show any new unresolved issues on playground that indicate new bugs or regressions.

• #734 started showing up at a high rate, but it doesn't seem connected to any build changes.

5. The playground deployment has run for at least 10 minutes.
6. The Flower monitor is reachable and shows no unexpected task failures.
7. The Flask dashboard is reachable.
8. The playground deployment is connected to IGWN Alert (in Flower, find the main gwcelery-worker, click Other, and look at the list of subscribed IGWN Alert topics).
9. The playground deployment is connected to GCN.

Mock events

10. The playground deployment has produced an MDC superevent.
11. The MDC superevent has the following annotations.
    • bayestar.multiorder.fits
    • bayestar.fits.gz
    • bayestar.png
    • bayestar.volume.png
    • bayestar.html
    • p_astro.json
    • p_astro.png
    • em_bright.json
    • em_bright.png
12. The MDC superevent has the following labels.
    • EMBRIGHT_READY
    • GCN_PRELIM_SENT
    • PASTRO_READY
    • SKYMAP_READY
13. The MDC superevent has two automatic preliminary VOEvents, JSON packets, and Avro packets if GCN_PRELIM_SENT is applied.
    • 2 preliminary VOEvents
    • 2 preliminary JSON packets
    • 2 preliminary Avro packets
14. Issuing a manual preliminary alert from the Flask dashboard sends another preliminary alert.
    • The alert is sent successfully if ADVOK or an ADVNO label is not applied this time.
    • Alternatively, a preliminary alert is blocked due to presence of ADVOK or ADVNO.
15. DQR_REQUEST label is applied to the superevent. The application happens at the time of launching the second preliminary alert.
16. The MDC superevent has either an ADVOK or an ADVNO label.
17. Issuing an ADVOK signoff through GraceDB results in an initial VOEvent.
18. Issuing an ADVNO signoff through GraceDB results in a retraction VOEvent.
19. Requesting an update alert through the Flask dashboard results in an update VOEvent.
20. Playground has recently produced an MDC superevent with an external coincidence, i.e. with an EM_COINC label. Use the Flask dashboard to do this manually (note that joint events with Swift may not pass publishing conditions and or have a combined sky map, indicated by the lack of RAVEN_ALERT and COMBINEDSKYMAP_READY label respectively).
21. The joint MDC superevent has the following annotations.
    • coincidence_far.json
    • combined-ext.multiorder.fits or combined-ext.fits.gz
    • combined-ext.png
    • overlap_integral.png
22. The joint MDC superevent has the following labels.
    • EM_COINC
    • RAVEN_ALERT
    • COMBINEDSKYMAP_READY
    • GCN_PRELIM_SENT
23. The joint MDC superevent is sending alerts with coincidence information.
    • At least one VOEvent with <Group name="External Coincidence">.
    • At least one Kafka JSON packet with an external_coinc field.
    • At least one circular w/ -emcoinc- in filename.
24. Issue a manual RAVEN alert using the Flask dashboard for a coincidence (i.e. has EM_COINC label) that has does not have the RAVEN_ALERT label yet. Choose a recent joint coincidence that meets this criteria and ensure that a RAVEN_ALERT label is applied to the associated superevent, external event, and preferred event.

Replay events

24. A Production superevent labeled GCN_PRELIM_SENT has the following parameter estimation annotations and the PE_READY label.
    • bilby_config.ini
    • Bilby.posterior_samples.hdf5
    • Bilby.multiorder.fits
    • Bilby.html
    • Bilby.fits.gz
    • Bilby.png
    • Bilby.volume.png
    • PE_READY

Note about this particular release.

This release is created from the repo in a non-standard way. Instead of being a tagged commit on main, this is a tagged commit on a separate branch. This branch diverged from main at v2.1.7 tag, i.e. this branch is v2.1.7 plus a few local commits. These local commits are already applied on main, one is just a cherry pick of d7c4c10f and the other is basically 97fe5c2a but not cherry picked due to merger conflicts with the lock file.