-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Currently, someone needs to manually "expose" the GraceDB record of an event candidate so that LV-EM partners can see the content tagged with 'lvem'. Only a limited set of people have the ability to do that (noted on https://wiki.ligo.org/Bursts/EMFollow/FollowupAdvocates - search for "expose/hide"). There is a risk of a delay if none of those people is available to do that step, or a mistake if no one remembers to do it. Approval Processor can be modified to expose the GraceDB record in this way automatically when it sends an alert with internal=0, to ensure that partners will be able to see it. This should only require a couple of lines of code; in fact, Approval Processor did do this during O1.
To go along with that, the childConfig file can be modified to set force_all_internal to "no". That way, when an Initial or Update alert goes out, it will to out to the LV-EM partners immediately. Currently, re-sending an alert with internal=0 is another manual operation that only a small number of people are able to do, because it requires logging in to the emfollow machine.