Create combined sky map and spacetime coincidence FAR automatically
Similar to waiting for g-events to be complete, we will wait to compare or combine sky maps until the external event is complete:
- comparing: when there is a coincidence (
EM_COINC), and both sky maps are available (se:SKYMAP_READY, ext:LUMIN_GO) - combine: when there is a raven alert (
RAVEN_ALERT), and both sky maps are available (se:SKYMAP_READY, ext:LUMIN_GO)
If the external event is not complete we will look whether a superevent sky map is available and apply SKYMAP_READY if it is. Note we also apply SKYMAP_READY to all related external events when the superevent sky map is first available. The first case catches times where the superevent sky map comes in after the coincidence is found (EM_COINC applied) and the latter case catches time where the superevent sky map comes in before the coincidence is found.
Merge request reports
Activity
added External Triggers Sky Maps labels
- Resolved by Brandon Piotrzkowski
@brandon.piotrzkowski Please articulate about the meaning of the label
LUMIN_GOits function and the rationale for the chosen name. It is the label already supported by graceDB ? - Last reply by Brandon Piotrzkowski
added 14 commits
-
24bddb1b...26f87403 - 13 commits from branch
emfollow:master - 49147685 - Automate sky map comparison; Fixes #248
-
24bddb1b...26f87403 - 13 commits from branch
-
I've made a lot of changes to this merge request (when testing I found several systems were broken, including combining sky maps and calculating spatial coinc FAR) and finally got the automation to work. Here's an example:
https://gracedb-test.ligo.org/superevents/S191225c/view/
You can see the spatial coinc FAR was automatically calculated without intervention, as well as a combined sky map.
- Resolved by Brandon Piotrzkowski
What does this have to do with sky map comparison?
- Last reply by Brandon Piotrzkowski
added 9 commits
-
dfc32088...a1c8a095 - 8 commits from branch
emfollow:master - 3487d1d4 - Automate GW-external sky map comparison
-
dfc32088...a1c8a095 - 8 commits from branch
- Resolved by Brandon Piotrzkowski
By taking into account the sequence of the Fermi GCN/Notice as describe here I'd like to suggest to add in the fits header the
NOTICE_TYPE:and theNOTICE_DATE:This can help to manage the fits file in any postprocessing analysis. - Last reply by Brandon Piotrzkowski
@brandon.piotrzkowski Since there are corners case in which the skymaps can be really different it is important to know to which notice the skymap correspond to. Example of a corner case is: The FERMI event: https://gcn.gsfc.nasa.gov/other/599160109.fermi The corresponding E-event: https://gracedb-test.ligo.org/events/E30400/view/
added 19 commits
-
3487d1d4...ac882fde - 18 commits from branch
emfollow:master - a9dcf7a6 - Create combined sky map and spacetime coincidence FAR automatically
-
3487d1d4...ac882fde - 18 commits from branch
