The problem of F3 GAS LVDT in 2022 might remain (klog).
The problem of F3 GAS LVDT in 2022 might remain (klog).
We accepted the following SDFs.
All diffs are related to the initial alignment work, so they should be accepted.
All diffs are also relted to the initial alignment work, so they should be accepted.
This change is related to the work reported in klog35544.
So, it should be accepted.
EY GASs show strange oscillations maybe originated from F1 at the level of 1000 counts with ~ 30 minutes period. This oscillation seemed to exist over 1 year or more.
IX F2 or F3 has also strange oscillation with very long period (~ 12 hours) as Fig.1 from 11days ago. If this is related with the tidal motion, why only this GAS is sensitive? Please check it. (Fig.1)
In addition, F3 still has an strange "excitation" at the level of 100 counts. (Fig.2/3)
In addition to this ~Hz level oscillation, it has also 0.04Hz (~25 seconds period) osccullation as Fig.1/2/3 just after the big earth recovery and yesterday.
It is better to check the relation between tehse strange oscillation (1~2 Hz and 0.04Hz(25 seconds period) ) and OMC PD satulation.
Around 0:30, IFO cpuld reach PRFPMI+RF. Around 6:00 I requested OBSERVATION, and IFO could reached it.
I also reduced IM heaters current for 15W PRFPMI+DC lock.
I performed the Initial Alignment from 23:00 to 24:00. After it, IFO could pass through ENGAGE PRMI 3F and reached IR handover. PRMI alignment seemed to be degraded before.
After the handover, the AS image showed split spots like TEM01. Although the ASC started, IFO was unlocked several times. IFO at present could not reach PRFPMI+RF lock state.
Around 0:30, IFO cpuld reach PRFPMI+RF. Around 6:00 I requested OBSERVATION, and IFO could reached it.
I also reduced IM heaters current for 15W PRFPMI+DC lock.
It is better to check the relation between tehse strange oscillation (1~2 Hz and 0.04Hz(25 seconds period) ) and OMC PD satulation.
Do you have any particular reason to increasing the set point value but not decreasing it?
ITMX was oscillating at the 1urad level in pitch. I found the LVDT signal of the F3 GAS is strange. The F3 GAS started oscillations around 1Hz when the LVDT signal crossed the setpoint. I changed the setpoint from 554 to 560. Though the LVDT signal was still a little strange, the fluctuation became smaller.
Do you have any particular reason to increasing the set point value but not decreasing it?
In addition to this ~Hz level oscillation, it has also 0.04Hz (~25 seconds period) osccullation as Fig.1/2/3 just after the big earth recovery and yesterday.
IX F2 or F3 has also strange oscillation with very long period (~ 12 hours) as Fig.1 from 11days ago. If this is related with the tidal motion, why only this GAS is sensitive? Please check it. (Fig.1)
In addition, F3 still has an strange "excitation" at the level of 100 counts. (Fig.2/3)
EY GASs show strange oscillations maybe originated from F1 at the level of 1000 counts with ~ 30 minutes period. This oscillation seemed to exist over 1 year or more.
The problem of F3 GAS LVDT in 2022 might remain (klog).
Operator name: Miyoki, Takahashi
Shift time: 09-17 JST
Check Items:
VAC: No issues were found.
CRY cooler: No issues were found.
Compressor: No issues were found.
Temp check: No issues were found.
VIS GAS filter output check: No issues were found.
IFO state (JST):
09:00 Start of shift: STANDBY
09:20~09:50 Initial alignment
10:24 Start of calibration: OBSERVATION WITHOUT LINES
17:00 End of shift: LOCKING
Operator name: Miyoki, Takahashi
Shift time: 09-17 JST
Check Items:
VAC: No issues were found.
CRY cooler: No issues were found.
Compressor: No issues were found.
Temp check: No issues were found.
VIS GAS filter output check: No issues were found.
IFO state (JST):
09:00 Start of shift: STANDBY
17:00 End of shift: LOCKING
Because ITMX was tripped due to large earthquakes around Sanriku-Oki in the Tohoku area around 17:00 last day, I requested
TMSX trip seemed to be recovered. GRX trans shows ~ 0.5, while GRY shows ~ 1.1. So, PR3 or I/ETMSX alignment should be adjusted?
I requested DOWN for LSC_LOCK guardian.
I have also adjusted IM heater current for IY and EX to avoid too much cooling around 18:00 last day.
IFO could not pass FIND IR RESONANCE after the successive earthquakes around Tohoku area.
GRX trans became 0.6~0.5, while GRY ~ 1.0. The max IR tans XY was ~0.6. So, PR3 alignment is not good?
I checked the Innolight MOPA 15NE (15W) at the Kashiwa campus. Anyway, it seemed to emit IR. I will check its power and frequency noise in the future. We can use its master laser part if it is healthy.
I also found one Mephisto 2000NE (maybe very old and Hasegawa-kun used bout 10 years ago. 2.3A for 2W output). I sent it to Kamioka and want to check it in the system that is being constructed in Toyama University.
The temperatures of IY and EX IM could be stabilized, while EY IM temperature is increasing due to the heat absorption of ETMY.
For checking that the frequency points at the swept sine of calibration measurements are contaminated by spectral peaks, I made a latest ASD with fine (~mHz) resolution.
Then I found that 4.17Hz and 9.77Hz combs came back which were seen also on OMC dark and CARM error signal, respectively as shown in Fig.1 and Fig.2.
These two plots were made with the data around 15:00 JST and 23:00 JST on Nov. 6th. Former and latter locks can be seen in Fig.3 as t = 6h-11h and t = 14h-20.5h, respectively. The lock duration of these two were ~5hr and ~6.5hr and there was no human activities in order to check the stability with disabling the whitening filter stage for the DCPD (probably for former lock and surely for latter lock in my memory).
These two combs were loud during O4a and were mitigated before before O4c (Comparison around 100Hz would be the easiest to understand). I couldn't remember how to mitigate the 4.17Hz combs on OMC (pin assignment of ZSW, cabling route around AS table, or else?). Though there was possibility that noise itself became louder than before, disabling the whitening filter makes SNR of these series peaks louder. If so, there may be no way to suppress them for now because stable IFO is unavailable with engaging whitening filter. In my memory about 9.77Hz combs on CARM, they were able to mitigated by adjusting the input gain of CMS as positive. Though I was not able to track recent activities about replacing IMC-CMS precisely, now the original common mode servo chassis were used for IMC and input gain were set as positive. So I have no idea why 9.77Hz combs came back. replacing chassis and/or re-cabling changed some situation around electrical connections...?
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.
Operator: YokozaWashimi
Shift time: 9:00-17:00 JST
Check Items:
VAC: No issues were found.
CRY temp: No issues were found.
CRY cooling water: No issues were found.
Temp: No issues were found.
VIS GAS filter: No issues were found.
IFO state(JST):
9:00 : STANDBY
17:00 : CALIB NOT READY