Reports 1-1 of 1 Clear search Modify search
DetChar (General)
shoichi.oshino - 17:11 Friday 08 November 2024 (31553) Print this report
Restart Omicron process
[Yuzurihara, Oshino]

We started a regular Omicron trigger run under commissioning conditions.

Details:
Interferometers have been kept locked at night in recent days.
We have therefore resumed regular Omicron runs to probe for glitches during this time.
We adopted "K1:GRD-IFO_STATE_N=100" as the interferometer state.
The corresponding segment is "K1-GRD_LOCKED".
We changed the script and ran Omicron and got an error.
This is because the old frame file directory is still in the cache file.
We deleted the corresponding information and Omicron started running.
Comments to this report:
shoichi.oshino - 14:26 Sunday 10 November 2024 (31569) Print this report
After resuming the Omicron process, k1sum1 hung due to a disk error.
I copied the system to a new HDD and started up k1sum1. I will verify if the operation is stable.
shoichi.oshino - 12:07 Tuesday 12 November 2024 (31599) Print this report
It turns out that the k1sum1 hunged up because the Omicron process, which runs every 15 minutes, is stacking up.
This is because the new segment file creation script outputs the day's segment information every 15 minutes.
After discussion with Yuzuhara-san, it was decided that in the future a new script would be created to cut out segments every 15 minutes from the existing file.

As a first aid, the previously used script to create a segment every 15 minutes was modified to create a segment only for GRD_LOCKED.
shoichi.oshino - 13:26 Friday 15 November 2024 (31652) Print this report
I have made two backups of the k1sum1 system disk.
I confirmed that the system is up and running on one of these backup disks.
Search Help
×

Warning

×