Change Log¶
Version 3 (2019-02-13)¶
Alert Contents
- Remove the
skymap_png
parameter from the VOEVents. The sky map plots take longer to generate than the FITS files themselves, so they would have needlessly delayed the preliminary alerts. - Change the IVORN prefix from
ivo://gwnet/gcn_sender
toivo://gwnet/LVC
, because GCN traditionally uses the text after the/
to indicate the name of the mission, which most closely corresponds to “LVC,” short for “LIGO/Virgo Collaboration.” Note that this IVORN is used for historical purposes and continuity with the GCN notice format used in O1 and O2, and is likely to change in the future with the commissioning of additional gravitational-wave facilities. - Retraction notices now get a separate GCN notice packet type,
LVC_RETRACTION=164
. TheRetraction
parameter has been removed from the<What>
section.
Version 2 (2018-12-13)¶
Alert Contents
- Removed the
Vetted
parameter from GCN Notices. It was intended to indicate whether the event had passed human vetting. However, it was redundant beacuse by definition Preliminary events have not been vetted and all Initial and Update alerts have been vetted. - The type of the
Retraction
parameter in the GCN Notices was changed from a string (false
ortrue
) to an integer (0
or1
) for consistency with other flag-like parameters. - Remove the
units
attribute from parameters that are not numbers.
Sample Code
- GCN has now begun publicly broadcasting sample LIGO/Virgo GCN Notices. Updated the sample code accordingly with instructions for receiving live sample notices.
Version 1 (2018-11-27)¶
Getting Started Checklist
- Updated instructions for joining the OpenLVEM Community.
Observing Capabilities
- Changed the expected number of BNS events in O3 from 1-50, as stated in the latest version of the Living Review, to 1-10 events, as stated in the more recent rates presentation.
Alert Contents
- In the example VOEvents, moved the Classification and Inference quantities
from the
<Why>
section to the<What>
section so that they validate against the VOEvent 2.0 schema.