Reports 1-1 of 1 Clear search Modify search
MIF (General)
takaaki.yokozawa - 12:12 Wednesday 05 November 2025 (35490) Print this report
Lock loss investigation 251104night - 05morning
I performed the lock loss investigation for the night run 4th -5th Nov.

Total 9 locked loss.

One would come from nearby earthquake
#1534

One would come from the large earthquake
#1542

Most locked losses were so called "fast locked loss"
OMC DCPD suddenly saturated with about 1 msec.
After OMC DCPD saturation detected, IMC/PMC locked loss detected.
LSC_LOCK guardian comment is "USERMSG 0: IMC seems to be unlocked"
We need to check the locked loss reason.

(Fig.1.) One locked loss had noisy time series in OMC DCPD
#1539

Full log can be seen in file
Images attached to this report
Non-image files attached to this report
Comments to this report:
takaaki.yokozawa - 12:44 Wednesday 05 November 2025 (35491) Print this report
In some cases of reduction of binary range may come from f^-2 noise below 100 Hz.
(Not calibrated yet)
Images attached to this comment
takaaki.yokozawa - 13:12 Wednesday 05 November 2025 (35494) Print this report
I checked the ~5 hour locked data carefully.
From the time series in Fig.1., We can obviously detected several glitches.

I checked in larger glitch around -15h in Fig.2.
Once, the saturation detected, but no locked loss.
The main frequency was about the 158.8 Hz (may not the violin frequency).

Fig.3 showed the glitch between -15h and -14h mainly detected in OMC-TRANS_DC_SUM_OUT_DQ
That would be suspension excitation around 10 Hz.

Fig.4. showed the second largest glitch betweem -14h and -13h
There are beat signal in ~190 Hz and 2.6 Hz

Anyway, several large kick in suspension and if this kick is large, lock loss like fast locked loss would be detected.
We need to consider why this suspension kick occurred.
Images attached to this comment
Search Help
×

Warning

×