We just had a second instance of a DAQ CRC error from h1sush2b to DC0 at 08:41:46 Wed 30 Aug 2023 PDT.
This is identical to the one we had 05:56:09 Sun 27 Aug 2023 PDT. FRS28945 was opened for the Sun event, I have added today's event to it.
The event is characterized as:
for one of the1/16th second data blocks in GPS second 1377445324 all of the DAQ data originating from h1sush2b's local DC to DAQ-DC0 was invalid. However for the same 1/16th second, the data block sent to DAQ-DC1 was valid.
Yesterday Jonathan configured the frame writers to store the MD5 checksum of the frame files. The error occured at GPS=1377445324, taking the modulo-64 of this time gives the full frame file name, and we can verify the checksums for these files differ between FW0 and FW1
>>> 1377445324 - (1377445324 % 64)
1377445312
Using the NDS to view the files (it mounts them read-only):
ssh root@h1daqnds0 "cat /frames/full/13774/H-H1_R-1377445312-64.md5"
fa59b37c1f1f02aeda8123ea81e70009
ssh root@h1daqnds1 "cat /frames/full/13774/H-H1_R-1377445312-64.md5"
1347619a6b8e18e103ceb86b5df75380
And they are indeed different (as are the frame file sizes, not shown).
As before, we can say that the FW0 frame is bad, and the FW1 frame is good and should be archived instead.