I've scheduled 9 burst injections to be injected coherently into both IFOs. They will begin at 10:10 UTC (2:10 PT) and are spaced 20 minutes apart. The IFO will need to be in observation mode for these injections to go in. Here are the relevant lines in the schedule file.
1164276617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_9_0.2.txt
1164277817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_13_0.6.txt
1164279017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_20_0.99.txt
1164280217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_12_0.4.txt
1164281417 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_16_0.9.txt
1164282617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_20_0.9.txt
1164283817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_4.0e-22_8.9_70.txt
1164285017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_153.txt
1164286217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_285.txt
The waveforms are on the hardware injection svn. The schedule file gives the path to the text files from the Details directory.
If for some reason these injections need to be stopped, follow these instructions:
Here is a link to the Burst groups ER10/O2 hardware injection plans - https://dcc.ligo.org/LIGO-G1601528
In the schedule file - ADI = Acretion Disk Instability, SG = Sine Gaussian.
At LHO, the first injection that went in was the 6th scheduled injection (ADI-e_20_0.9.txt). Unfortunately this was the only injection that went in at LHO, and the only one that was coherently injected at both sites. The remaining three injections were stopped by the guardian because there was an external trigger alert, which I'm guessing was due to the injection itself.
I've attached the relevant section of the INJ_TRANS guardian log.