Displaying report 1-1 of 1.
Reports until 16:20, Monday 24 February 2020
H1 CDS
david.barker@LIGO.ORG - posted 16:20, Monday 24 February 2020 - last comment - 19:06, Monday 24 February 2020(55270)
command to set owl operator's lock-loss-alerting configuration

To set an operator's lock-loss alert configuration prior to their shift type the following command:

owl_op operator.name

Where operator.name is the operator's ligo.org name. These settings rely on the Guardian IFO_NOTIFY node to alert for both lock-loss and out-of-observation events. GraceDB events are disabled, and alerting times restricted to the shift times.

I've added the IFO_NOTIFY node status and link to the LOCKLOSS ALERT Overview page. Anyone with voice-call option selected is shown with an ORANGE phone indicator.

Comments related to this report
david.barker@LIGO.ORG - 17:36, Monday 24 February 2020 (55273)

I've updated the lock-loss-alert DCC document T2000061

thomas.shaffer@LIGO.ORG - 19:06, Monday 24 February 2020 (55277)

I made a REMOTE_OWL_SELECTION.adl that has names listed as cammand buttons (only my name currently). This launches a shell script that calls Dave's owl_op and changes the IFO mode & IFO_NOTIFY state. Should make it easy.

Displaying report 1-1 of 1.