Reports until 10:55, Thursday 07 January 2016
H1 INJ (INJ)
cregg.yancey@LIGO.ORG - posted 10:55, Thursday 07 January 2016 - last comment - 14:13, Tuesday 12 January 2016(24747)
HWInjReport 1132963217 - 1136155727

HWInjReport 1132963217 - 1136155727

Performed a run spanning the time period from 1132963217 (Dec 01 2015 00:00:00 UTC) to 1136155727 (Jan 06 2016 22:48:30 UTC)

Parameters

The following parameters were used for this run:

Scheduled Injections

During this time period, 12 scheduled injections were found to have occurred

Only 1 injection was found to not occur:

Network and IFO Injections

Of the occurring scheduled injections, only two occurred as single-IFO injections:

All other scheduled injections occurred as H1-L1 coincident injections. The only UNSCHEDULED injections were 5 CALRESETs at L1 and 1 CALRESET at H1.

Discussion of Anomalies

The CALRESET injections have the same pattern of occurring with only certain paired combinations of the frame flags indicated by HWInjReport, as seen previously. However, all of the occurring scheduled injections have the anomaly of not occurring in the CAL-INJ channel and not having the TRANSIENT bit set to “off” to indicate the presence of a transient injection. They do occur, consistently, in the ODC-MASTER channel for HOFT, RAW, and RDS frames and the GDS-CALIB channel for HOFT frames.

Non-image files attached to this report
Comments related to this report
cregg.yancey@LIGO.ORG - 11:01, Thursday 07 January 2016 (24748)

Minor correction made to report.  There were, in fact, 2 single-IFO injections that occurred, both in L1.  I missed the second one due to an eyeball error.

cregg.yancey@LIGO.ORG - 14:42, Monday 11 January 2016 (24874)

As reported by Chris B. in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=24282, the two single-IFO injections were the result of H1 losing lock.

cregg.yancey@LIGO.ORG - 14:13, Tuesday 12 January 2016 (24901)

The absence of occurrence of the injections in the CAL-INJ channel turns out to not be an anomaly but the result of a deliberate change to using the new CAL-PINJX_ODC_CHANNEL_OUT_DQ channel to record the information that was originally in CAL-INJ_ODC_CHANNEL_OUT_DQ.  Currently, HWInjReport does not check the CAL-PINJX channel, however, it should not be difficult to add checking on this channel.