Draft: Produce internal-only GCN Notices for subthreshold events

added GCN Notices Orchestrator labels

added 3 commits

• b28ab220...66e1154a - 2 commits from branch emfollow:master
• 704c49d2 - Produce internal-only GCN Notices for subthreshold events

Compare with previous version

why do we need this?

To handle alerts uniformly, whether they are above threshold or below threshold. So that the cleanup is applied to sub-threshold events too. Also, it will make life easier for the Swift follow-up to have a GCN notice that they can listen for.

added 2 commits

• ec122d16 - 1 commit from branch emfollow:master
• d7f72220 - Produce internal-only GCN Notices for subthreshold events

Compare with previous version

added 2 commits

• 9258bebe - 1 commit from branch emfollow:master
• 64a5ebf5 - Produce internal-only GCN Notices for subthreshold events

Compare with previous version

added 1 commit

• bb158356 - Produce internal-only GCN Notices for subthreshold events

Compare with previous version

resolved all threads

added 1 commit

• 87efa4f7 - Produce internal-only GCN Notices for subthreshold events

Compare with previous version

@leo-singer I do not understand if producing internal-only GCN Notices for subthreshold events amount to sent out to the collaboration information on all the S-event generated in gracedb by the online trigger. Pleae give more details.

mentioned in issue #263 (closed)

mentioned in merge request !676 (merged)

changed milestone to %v0.9.1

changed milestone to %v0.9.2

changed milestone to %v0.10.0

removed milestone

@leo-singer this seems useful for O4, can you confirm?

Yeah, this is still useful. This should be the basis of Fermi and Swift sub-threshold searches in O4.