Due to to the issue reported in klog, we needed to update the script to generate the Segment files and reproduced segment files. After several confirmation with the administractor of the DQSEGDB, we will start the rsync process.
Details
- We changed the channel names to detect the overflow
- ETMX: K1:FEC-103* --> K1:FEC-104*
- ETMY: K1:FEC-108* --> K1:FEC-109*
- IPC glitch: K1:FEC-103_TIME_DIAG --> K1:FEC-104_TIME_DIAG
- The script runs at k1det1 every 15 minutes for the regular segment generation. Sometimes due to the unexpected trouble, it's possible to stop the regular segment generation such as this time. I updated the script to generate and fill the missing segment. This update contributed to the automation of segment file generation very much. We don't need to care much at the recovery from the power outage.
- The script was pushed to the github.
- By using the updated script, I reprocuded the segment files on 2025/02/8, 2/9, and 2/10.
- The regular segment generation was already started. The generated segment files are stoped in /users/DET/tools/Segments/Script/Partial . In the morning, these segment files will be copied to /users/DET/Segments and copied to the DQSEGDB. But, I stopped the copy process now. After several confirmation with the administractor of the DQSEGDB, we will start the copy process for the release of the Segment files.
- It was too late to realize that the SEGMENT generation was failing. For the countermeasure next time, I implemented the alert to send Slack's detchar-alert channel when segment generation failed.
- For the segment data at 2025/02/07, we gave up the reproduction because (1) channel names changed during one day, and it requires special handling. (2) The interferometer was down, and it was a maintenance day, so it's low necessity.
