Chris B., Adam M.

Summary:

We tested scheduling CBC waveforms with tinj. We had two successful coherent H1L1 hardware injections and one failure.

I've attached omega scans of the hardware injections, except for the L1 omegscan for the injection scheduled at 1127789367 (will post this one later, there was an error generating it).

Waveforms:

All waveforms used are in the hardware injection SVN at: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/${IFO}/coherentbbh*_*_${IFO}.out

And the parameter files are: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/coherentbbh*_*.xml

Test 1:

Originally we scheduled one hardware injection. It was successful:
1127783813 1 1.0 coherentbbh0_1126259455_

The GraceDB events for this injection are L1 and H1.

Test 2:

We then scheduled another injection. It was successful at L1 and unsuccessful at H1:
1127784860 1 1.0 coherentbbh1_1126259455_

The GraceDB events for this injection are L1 and H1.

At the moment GraceDB is set up to treat hardware injections like EM alerts. In order to override the EM alert pausing of tinj and be able to schedule injections closer together on h1hwinj1/l1hwinj1 we did:
ezcawrite H1:CAL-INJ_EXTTRIG_ALERT_TIME 112775939

The command worked. And the injection was successful at L1. At H1 the injection did not go in. Checking the MEDM screen for hardware injections we saw that tinj was paused. We were not able to unpause it. We thought that maybe there was an outside process (GraceDB?) that was keeping tinj paused.

Therefore we removed the following scheduled injections from the schedule file:
1127785760 1 1.0 coherentbbh2_1126259455_
1127786667 1 1.0 coherentbbh3_1126259455_
1127787567 1 1.0 coherentbbh4_1126259455_
1127788467 1 1.0 coherentbbh5_1126259455_
1127790274 1 1.0 coherentbbh7_1126259455_

Since none of them would have been successful at H1.

Test 3:

We scheduled one last injection. It was successful:
1127789367 1 1.0 coherentbbh6_1126259455_

The GraceDB events for this injection are L1 and H1.

We checked that tinj was unpaused before this hardware injection and it was.