Skip to content

Release version 2.5.1 "Cactus cat"

Git ref: 47fb9800

Checklist

Basics

  1. The CI pipeline succeeded, including all unit tests and code quality checks.
  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 branch 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.
  5. [ ] Check the versions of the following packages in the poetry.lock file have been approved by the SCCB (i.e. either has the status:deploy or status:deployed label).

Test deployment

  1. Sentry does not show any new unresolved issues on playground that indicate new bugs or regressions.
  2. The playground deployment has run for at least 10 minutes.
  3. The Flower monitor is reachable and shows no unexpected task failures.
  4. The Flask dashboard is reachable.
  5. 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).
  6. The playground deployment is connected to GCN (in Flower, find the voevent gwcelery-worker, click Other, and look at the list of receiver peers).

Mock events

  1. The playground deployment has produced an MDC superevent.
  2. The MDC superevent has the following annotations.
    • bayestar.multiorder.fits
    • bayestar.fits.gz
    • bayestar.png
    • bayestar.volume.png
    • bayestar.html
    • gstlal.p_astro.json
    • gstlal.p_astro.png
    • em_bright.json
    • em_bright.png
  3. The MDC superevent has the following labels.
    • EMBRIGHT_READY
    • GCN_PRELIM_SENT
    • PASTRO_READY
    • SKYMAP_READY
  4. 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
  5. 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.
  6. DQR_REQUEST label is applied to the superevent. The application happens at the time of launching the second preliminary alert.
  7. The MDC superevent has either an ADVOK or an ADVNO label.
  8. Issuing an ADVOK signoff through GraceDB results in an initial VOEvent.
  9. Issuing an ADVNO signoff through GraceDB results in a retraction VOEvent.
  10. Requesting an update alert through the Flask dashboard results in an update VOEvent.
  11. 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).
  12. 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
  13. The joint MDC superevent has the following labels.
    • EM_COINC
    • RAVEN_ALERT
    • COMBINEDSKYMAP_READY
    • GCN_PRELIM_SENT
  14. 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.
  15. 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

  1. 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.em_bright.json
    • Bilby.multiorder.fits
    • Bilby.html
    • Bilby.fits.gz
    • Bilby.png
    • Bilby.volume.png
    • PE_READY
    • Link to PEsummary page (log message in parameter estimation section).
Edited by Deep Chatterjee
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information