Reports until 10:17, Tuesday 08 November 2016
H1 DAQ (CDS, DAQ)
jonathan.hanks@LIGO.ORG - posted 10:17, Tuesday 08 November 2016 - last comment - 16:02, Tuesday 08 November 2016(31310)
Rebuilt h1fw2 using a ldastools framecpp at the same version as LLO 
I have rebuilt daqd fw on h1fw2 using a new ldas-tools build (2.5.2).  This is the version in use at LLO and contains updated leap second tables.

The plan is to compare the output from h1fw2 to h1fw0 and h1fw1 for a week and then migrate h1fw0 and h1fw1 to use the newer framecpp releases next week.

In the mean time the daq status page will show differences in the frames between h1fw2 and the other frame writers. This is due to framecpp encoding a different version string in the frame file.  Dave will update the daq overview screen to help minimize the differences.

This is under workpermit 6303.
Comments related to this report
jonathan.hanks@LIGO.ORG - 16:02, Tuesday 08 November 2016 (31334)
Link 

As Dave was reworking the DAQ overview screen we noticed an artifact of the daqd fw code.

The framecpp version information is only written to full frames (science/commissioning) not to trend frames.  So the switch to a newer FrameCPP version introduces a difference in checksum and file length in the science frame as the version string has changed.  However there is no change to the minute or second trend files.

It would probably be good to have the version string injected into the minute/second trend as well to help figure out issues (if they arise)...