SYMPTOMS

This evening during the Operator Handoff, Jeff noticed that the GWI.stat state for H1 (see attached) was in a YELLOW "No good h(t)" state (this was after he had taken it to OBSERVING minutes earlier).

• On the 4/24/17 Daily Summary Page, the DMT SenseMon plot (see attached) shows a red GDS BNS Range of 30Mpc for this new current lock (the gray "Front End range" is at a more normal 65Mpc).
• On the CAL:  h(t) generation Calibration state plot (see attached), we are in the RED state for:  h(t) OK,  Kst smooth, Kpu smooth, Ka smooth, & Ka median
• DMT SPI Page:  No obvious issues listed
• Current Network Status for Nagois Core Page:  We have the following CRITICAL alarm for H1 Intent Bit:
  • Critical: at 1177056402 we found a total of 600.0 seconds where h(t) ok was off but intent was on. This happened for a total of 1 blocks. The worst offender had length 600.0 seconds (maximum allowed 270.0 ) starting at 1177055800.0 (buffer begin) and ending at 1177056400.0 (buffer end)

Summary:  Only symptom viewable in the Control Room is the GWI.stat.  Range looks fine on the BNS FOM on nuc0.

Do Not Think This Is EY CRC Error....

Travis noticed my note about the h(t) issue in my alog and just sent me a text about the issue he had during his graveyard shift & how he fixed it last week (alog35702:  EY CRC Error 9:51 UTC).  

I do not think this is the issue because we:

1. Did NOT receive an "EY CRC error"  Verbal Alarm
2. And all CRC values on the CDS Overview are 0.

My Action

Since, there are no alarms/notifications here, will send an email out to the DetChar Group (due to Summary Page), Peter Shawan (due to GWI.stat), & Greg Mendel/Dan Moreu/Dave Barker (due to nagois CRITICAL alarms).  Will then wait for any instructions for further action.