Not sure whether this is new or we've seen it in the past, but we have observed temporary glitches in the two microsecond bytes in the binary files for run 001_0000494.
Originally we realized there was a problem because the timestamps for the run were distributed over some 9 (!) days. A closer inspection of the root file from Pixy showed a fair number of jumps in the timestamps
Not sure whether this is new or we've seen it in the past, but we have observed temporary glitches in the two microsecond bytes in the binary files for run 001_0000494.
Originally we realized there was a problem because the timestamps for the run were distributed over some 9 (!) days. A closer inspection of the root file from Pixy showed a fair number of jumps in the timestamps
The root cause of the problem was actually traced back to a problem in the binary file
(Mind the mismatch in the event number is due to the fact that in Pixy we do not write in the output file events with no clusters.)