Abstract

As a test of detecting lockloss due to MN OpLev glitches, I saw locklosses from observing state during this weekend.
Oplev glitches can be seen within 1 second before lockloss time in all lockloss cases except ones related to earthquakes by eye-scan.
A detection script (see also klog#31517) could detect 21 of 22 lockloss events.
 

Details

On Nov. 9th UTC, there were 10 lockloss events from observation state.
2 of 10 events were related to the earthquakes.
Remaining 8 events seems to be related to oplev glitches (Fig.1-8).
One of these 8 events were missed by the detection script (Fig.6).
In the case of Fig.4, glitches was presence but its amplitude was much smaller than other cases. It might be better to check that this lockloss was really caused by oplev glitches more carefully.

On Nov. 10th UTC, there were 15 lockloss events.
1 of 15 event is related to earthquake (but lockloss guardian was missed it).
Remaining 15 events seems to be related to oplev glitches and all of them can be detected by the script (Fig.9-22).