A leap second was added to UTC at midnight UTC time yesterday (17:00 local time). I was on site and watched the control room clock, which dissapointingly did not show the "60" second.

I tested the IRIGB ADC channel on the H2 DAQ frame and verified it is now indeed 16 seconds off UTC (was 15 seconds off prior to the adjustment). Daniel showed that the IRIGB timing unit in the MSR had extinguished its "leap second pending" LED and was now reporting 16 leap seconds between UTC and GPS.

Greg verified that the frame did not increment its GPS-TAI difference

ULeapS stayed at 34 (it should be 35)

This is causing some problems with the frame verification programs

$ /usr/bin/framecpp_verify --verbose

VerifyException: METADATA_INVALID: Bad ULeapS value ( for gpstime: 1025136600.000000000 expected: 35 read: 34 )

We will work with Alex on upgrading frame cpp on the frame writers to permit ULeapS to be corrected.