[YamaT, Yuzurihara]
I tried to validate the script. When we compare the Segment generated by the new script and the Segment of regular generation with 15 cadences, there was a slight difference due to missing frame data by rebooting the computer at Kamioka. This was happening only on the maintenance day (11/08). So, it will not affect providing the Segment for the data analysis purpose.
Detail
The Segment generated by the new script is stored in /users/yuzu/work/20250115_segment . The differences between the generated Segment by the new script and the Segment of regular generation with 15 cadences are summarized below:
For the following Segments of 2024/11/08, the period of rebooting the computer was flagged in the Segment of regular generation with 15 cadences, not flagged in the Segment generated by the new script. We guess the cause is related to rebooting the computer.
- K1-ETMX_OVERFLOW_OK
- K1-ETMY_OVERFLOW_OK
- K1-OMC_OVERFLOW_OK
- K1-GRD_UNLOCKED
For the K1-DAQ_IPC_ERROR Segment of 2024/11/08, the period of 1415118400 ~ 1415118592 was flagged in the Segment of regular generation with 15 cadences, not flagged in the Segment generated by the new script. As I heard from YamaT-san, there was multiple rebooting of k1fr0 during the maintenance day. If there was no frame data in /frame0/, the script to make a cache file will use the frame file in /frame1/ . This time, it seems not to be happening. We will check it for future maintenance days. Anyway, this happens during maintenance day. It will not affect providing the Segment for the data analysis purpose.
For following Segments of other dates, there was no difference.
For the following Segments, there was no difference for all the dates.
- K1-ETMX_OVERFLOW_VETO
- K1-ETMY_OVERFLOW_VETO
- K1-OMC_OVERFLOW_VETO
- K1-GRD_PEM_EARTHQUAKE
- K1-GRD_LOCKED
- K1-GRD_SCIENCE_MODE
The script was uploaded in the git repo.