I have installed a 'hwinj' application at both sites that handle opportunistic hardware injections for the detchar and stochastic groups:
ifo: H1
waveform root: /ligo/groups/cal/H1/hwinj
config file: /ligo/groups/cal/H1/hwinj/hwinj.yaml
GraceDB url: https://gracedb-playground.ligo.org/api/
GraceDB group: Test
GraceDB pipeline: HardwareInjection
excitation channel: H1:CAL-INJ_TRANSIENT_EXC
must specify injection group and name, options are:
'detchar': ['safety']
'stochastic': ['short', 'long']
jameson.rollins@opslogin0:~ 1$
The command takes two arguments: the injection group (in this case "detchar" or "stochastic"), and a specific injection name. The available injection names/waveforms are configured in the hwinj.yaml config file. By default injections are scheduledf or 10 seconds after the command is executed. You need to pass the '--run' option to actually execute the injection (see --help for more info). The detchar injection will be followed by a GraceDB upload, and the script should handle automatically fetching the authentication cert for the user executing it. The '--dry' option can be used to test everything without actually initiating the injection or gracedb upload.
These injections should happen in nominal low noise. Assuming everything is configured correctly and the DIAG_EXEC guardian nodes are properly tied into the overall guardian IFO status, initiation of these nodes should take us out of OBSERVING automatically.
The setup current supports three different injections, one "safety" injection for detchar (~7 min), and a long (30 min) and short (13 min) injection for the stochastic group. The relevant injection commands would then be:
We should coordinate with the detchar and stochastic groups to run these injections during this last week of engineering run.
Before performing the Detchar Safety injections, please go through the checks in this google document.