Reports 1-1 of 1 Clear search Modify search
MIF (General)
takafumi.ushiba - 14:12 Thursday 06 November 2025 (35505) Print this report
Frequent kick of suspensions

To check if the lockloss reason is suspension or not, I kept IFO at 10W PRFPMI RF lock state and see how frequently suspensions are kicked.
Figure 1 shows the DARM error signals with 10-60 Hz bandpass filter.
Y cursor shows the rough threshold that causes the lockloss when IFO is OBSERVATION state.
The time distance between two T cursors is 1 hour, so large kick, which would cause the lockloss when OBSERVATION, happens four times in one hour.

Figure 2 shows the spectrum measured at the time including suspension kick.
In all cases, the 44.6 Hz peak was the largest, likely due to the ETMX resonance.

To mitigate the DARM residul motion due to the suspension kick, I implemented resonant gain at FM8 of DARM1 filter bank.
However, the lockloss happens due to the oscillation at 47Hz (fig3) roughly 3 minutes after engaging resonant gain.
I'm not so sure this oscillation comes from engaging resonant gain, it might not be a good way to engage resonant gains to mitigate the effect of suspension kick.

Note:

During this work, I modified the following filter banks and epics values.
FM8 of DARM1, FM1 of SRCL1, FM1 of ETMX_NBDAMP_V5, FM1 of SC-AA_DARM_ERR, FM1 of K1:LSC-AA_DARM_CTRL, and K1:VIS-ETMX_NBDAMP_INMTRX_15_36 (from 0 to 1).

Images attached to this report
Comments to this report:
takafumi.ushiba - 17:20 Thursday 06 November 2025 (35510) Print this report

To check if the reason of OMC DC PD saturation is the suspension kick, I locked PRFPMI without engaging whitening filter for OMC DC PDs.
It degrades the ADC noise and noise floor got slightly worse, ADC range at high frequency increases by a factor of 10.
So, if the large suspension kick is the reason of the lockloss, it would help t keep the lock.
To keep this configuration, I modified the OMC_LSC guardian as shown in fig1.

Images attached to this comment
takafumi.ushiba - 18:02 Friday 07 November 2025 (35530) Print this report

I checked the OMC DC PD signals in each lock from last night.

Figure 1 shows the OMC DC PD signals at the lock from 2025/11/6 06:03:48 UTC.
Since the speed of glitches is very fast, the signals would be enhanced by a factor of 10 if the whitening filter is off.
So, if the glitch reached around upper Y-cursor, the signals would be saturated if the whitening filter is on.
There are four glitches that exceeds the upper Y cursor, so the lockloss should be happened if the whitening filter was turned on.

Figure 2 shows the enlarged view of one glitch in fig1.
Clear ring down can be seen, so it seems due to the kick of suspensions.

For the lock from 2025/11/6 11:41:06 UTC, these is no large glitch that exceeds the threshold.
For the lock from 2025/11/6 12:22:33 UTC, these is also no large glitch that exceeds the threshold but the glitches close to te threshld can be seen as shown in fig3.

For the lock from 2025/11/6 13:55:08 UTC, there is 2 glitches that exceed the thresold.
One of them is smilar glitch as shown in fig2 but the other is different: very short glitch calmed down within 1 second (fig4).
The similar short glitch can be seen in the lock from 2025/11/6 21:48:58 UTC, which seems very clear sine gaussian noise (fig5).

So, some DC PD saturation seemed suspension kick but there might be another reason of sudden glitch in OMC DC PD.

Images attached to this comment
Search Help
×

Warning

×