Skip to content

removing duplicate skymaps and keeping the lowest latency ones

Removing duplicate skymaps & keeping the lowest latency ones in the case of duplicates.

This takes care of issue: #6 (closed)

Before:::

Nine sky maps are available at this time and can be retrieved from the GraceDB event page:

  • bayestar.fits.gz, an updated localization generated by BAYESTAR, distributed via GCN notice about 4 hours after the event
  • bayestar.fits.gz, an initial localization generated by BAYESTAR, distributed via GCN notice about 5 hours after the event
  • bayestar.fits.gz, an initial localization generated by BAYESTAR, distributed via GCN notice about 6 hours after the event
  • bayestar.fits.gz, an updated localization generated by BAYESTAR, distributed via GCN notice about 2 days after the event
  • LALInference_skymap.fits.gz, an updated localization generated by LIB, distributed via GCN notice about 2 days after the event
  • bayestar.fits.gz, an updated localization generated by BAYESTAR, distributed via GCN notice about 2 days after the event
  • LALInference_r2.fits.gz, an updated localization generated by UNKNOWN, distributed via GCN notice about 2 days after the event
  • LALInference_r2.fits.gz, an updated localization generated by UNKNOWN, distributed via GCN notice about 15 days after the event
  • LALInference_f.fits.gz, an updated localization generated by LIB, distributed via GCN notice about 3 months after the event

After:::

Four sky maps are available at this time and can be retrieved from the GraceDB event page:

  • bayestar.fits.gz, an updated localization generated by BAYESTAR, distributed via GCN notice about 4 hours after the event
  • LALInference_skymap.fits.gz, an updated localization generated by LIB, distributed via GCN notice about 2 days after the event
  • LALInference_r2.fits.gz, an updated localization generated by UNKNOWN, distributed via GCN notice about 2 days after the event
  • LALInference_f.fits.gz, an updated localization generated by LIB, distributed via GCN notice about 3 months after the event

Updates on our analysis of this event will be sent as they become available.

Merge request reports

Loading