Displaying report 1-1 of 1.
Reports until 13:41, Friday 29 January 2016
H1 SYS
keita.kawabe@LIGO.ORG - posted 13:41, Friday 29 January 2016 (25245)
We didn't see GPS anomaly

There was a report of GPS glitch as large as 13 microsec (http://www.itnews.com.au/news/satellite-failure-caused-global-gps-timing-anomaly-414237) starting around "January 26 12.49 am local time", presumably Mountain Standard Time, so it's probably around Jan 26 07:49 UTC, and was fixed by "6.10 am Mountain Standard Time".

I looked at the timing comparator for the cesium clock (H1:SYS-TIMING_C_MA_A_PORT_2_SLAVE_CFC_TIMEDIFF_1) as well as X end GPS receiver (H1:SYS-TIMING_X_FO_A_PORT_9_SLAVE_CFC_TIMEDIFF_3) and Y end GPS (H1:SYS-TIMING_Y_FO_A_PORT_9_SLAVE_CFC_TIMEDIFF_3).

(It seems like end station GPS units are connected to the second input of timing comparators at each end station at LLO, but here they are to the third input.)

Right plot shows 6-days, and the left one is 4 hours around the reported glitch, and I see no timing jump.

Images attached to this report
Displaying report 1-1 of 1.