Reports of 35128
ISC (ITF Control)
kentaro.komori - 5:09 Wednesday 18 November 2026 (37872) Print this report
Trial of shifting the sideband frequency

[Fujimoto, Komori]

We started investigating whether shifting the RF sideband frequency could improve the MICH signal.
As a first trial, we decreased the seed frequency by 300 Hz. We then adjusted the demodulation phase of RF51 to -170 degree so as to minimize the SRCL contribution in the Q phase, and measured the MICH response.

The attached figure shows the result of the MICH excitation, with the blue trace representing the Q-phase spectrum.
The peak-to-floor ratio is approximately 10, which is higher than the value of approximately 4 obtained in the previous measurement (klog:37832).

This result suggests that the MICH signal may be recovered by adjusting the SRCL.
Tomorrow, we will perform the decoupling and attempt to lock the DRMI using the 3f signals with this sideband frequency.

Images attached to this report
ISC (General)
takahiro.yamamoto - 3:09 Wednesday 18 November 2026 (37870) Print this report
Comment to [Important] Resonance splitting issue in the PMC (37859)

> For some reason, the slow-output offset at the final stage of the IMC CMS slow path (K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET) had increased to 5.8 V.
Setting 5.8V to K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET seems default behavior of DOWN state of FSS guardian (see also attachment).
At line 25, offset value is defined as 5.825V
At line 205, offset value is set to EPICS channel.

I have no idea how to enter the run() function without executing the main() function when there is no 'return' in the main() function.
And also, it's strange that we haven't encountered this problem before.

If we won't use RefCav again, FSS guardian which is just a trouble maker should be removed.

Images attached to this comment
PEM (EX)
tatsuki.washimi - 22:35 Tuesday 17 November 2026 (37869) Print this report
Comment to Magnetic field measurments at X-arm (37856)

[Abe, Washimi]

In this eveneng, we restarted the measurments for tonight. Tow Mag-13MCL are used in this test.

  1. about 20 cm from the beam duct, Y- side
  2. about 200 cm from the beam duct, Y- side

We will clean them tomorrow morning.

Images attached to this comment
PEM (EX)
tatsuki.washimi - 22:32 Tuesday 17 November 2026 (37868) Print this report
Comment to Magnetic field measurments at X-arm (37856)

[Abe, Ohsawa, Washimi]

In this morning, just after the morning meeting, we cleaned our setup for other workers' passing. The battery had been empty around 2 a.m.
The Schumann resonanses are cleary found in the Z-axis of each sensors (and also the permanent outside sensors)

Images attached to this comment
DGS (General)
takahiro.yamamoto - 21:06 Tuesday 17 November 2026 (37867) Print this report
mx_stream on k1ey0 was relaunched
Because of a hang-up of mx_stream on K1EY0, data was not recorded from 16:08 to 20:20 for TMS-Y, PCAL-Y, and PEM-EY.
mx_stream on K1EY0 was relaunched and now DAQ for these models are resumed.

-----
DAQ bit in STATE_WORD of k1iopey0 was raised due to hang-up of mx_stream (Fig.1). It is unclear why mx_stream crashed, but the following error appeared in the mx_stream logs.
isendxxx failed with status Remote Endpoint Unreachable
disconnected from the sender


Since the DAQ of the affected models stopped around 16:08, this is believed to be the time when mx_stream stopped (Fig.2-3). In addition, a network outage lasting several seconds was observed only on K1EY0 shortly after 2:00 p.m (Fig.4). Should we suspect a connection between these issues and the fire alarm going off during the fire drill? Anyway, we restarted mx_stream on K1EY0 and restored the DAQ for the affected models around 20:20.

By the way, I heard Initial alignment was done in this evening. In normal case, we often use test points on k1lsc and k1asc as a reference of arm trans. PD/QPDs which are sent from k1tms{x,y} to k1lsc via RFM. So an initial alignment work was hopefully not affected by this issue. But if raw values on k1tmsy was recorded as good values, please check them. They were contaminated by DAQ error.
Images attached to this report
DGS (General)
hirose.chiaki - 18:07 Tuesday 17 November 2026 (37866) Print this report
Comment to HWP device is unreachable (37862)

As a temporary workaround, I renamed `lsclib.py` in the `asc` directory to `lsclib_asc.py`.

DGS (General)
takahiro.yamamoto - 17:55 Tuesday 17 November 2026 (37865) Print this report
Comment to HWP device is unreachable (37862)
[Ikeda, YamaT]

We found finally that the HWP issue was caused by missing packages on which the script depended, so we installed the necessary packages on k1grd1. Installation manual of the guardian server was also updated (klog#17316).

Since testing the Guardian code does not extend to checking external code called via `subprocess` (as this requires running the code on an actual device to be considered a valid test), this issue had been overlooked. Because it increases the difficulty of migration, the use of `subprocess` in Guardian should be avoided. Alternative methods include `Threading` and `concurrent.future`.

By the way, we found two lsclib.py as
- lsc/common/guardian/lsclib.py
- asc/k1/guardian/lsclib.py
Which one is called depends on the Python path order: if a current hard-coded configuration file is used, the `lsc` version is called, while in an automatically generated environment, the `asc` version (which appears first in alphabetical order) is called. Which code was actually used in O3GK and O4a/c? Science Mode may be no longer reliable. Stop such sloppy quality management and operation.

ISC (General)
Hiroki Fujimoto - 16:04 Tuesday 17 November 2026 (37864) Print this report
Comment to [Important] Resonance splitting issue in the PMC (37859)

I investigated other signals around the time when the IMC CMS slow-output offset changed (10:55:14 JST) and found that the IMC CMS IN1 switch had been turned on just before the offset change (Fig. 1).
Before this occurred, the IO Guardian had been down for more than an hour, and the IN1 switch had remained off.
However, it is still unclear why the IN1 switch was suddenly turned on and why the offset changed immediately afterward.

Images attached to this comment
ISC (General)
kentaro.komori - 14:42 Tuesday 17 November 2026 (37863) Print this report
Comment to [Important] Resonance splitting issue in the PMC (37859)

[Miyakawa, Fujimoto, Sugioka, Hirose, Komori]

Abstract:

We resolved the issue related to the PMC and successfully locked it with the nominal transmitted power.

The issue was caused by phase modulation through the laser PZT.
An unexpected 5.8 V offset from the IMC CMS was applied to the SR560, causing the SR560 to overload and produce a large oscillation at approximately 1 MHz, and then applied to the laser PZT.

Details:

We entered the PSL room to investigate the PMC issue reported in the original post.
Upon entering the room, we found that the SR560 used as a 30-kHz low-pass filter immediately before the laser PZT actuator was indicating an overload condition (Fig. 1).

We then found that the SR560 output had a DC offset of 3.2 V together with an oscillation of 0.26 V at 1.1 MHz (Fig. 2), which was responsible for the observed ~1 MHz sidebands.
Please note that the voltage displayed on the oscilloscope was measured with a 50-Ω input impedance.
The oscillation amplitude was smaller than expected from the estimated modulation depth.
However, the actuator efficiency may be higher than our nominal estimate because the laser PZT has multiple mechanical resonances above 100 kHz.

Next, we found that the input to the SR560 had a DC offset exceeding 5 V, originating from the IMC CMS output.
For some reason, the slow-output offset at the final stage of the IMC CMS slow path (K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET) had increased to 5.8 V.
This value had remained at 0 V for a long period and suddenly went up to 5.8 V at 10:55 JST yesterday (Fig. 3).

After returning this offset to zero, the double-peak structure disappeared during the cavity scan. We then successfully locked both the PMC and the IMC.
Finally, we aligned the steering mirrors upstream of the PMC and maximized the PMC transmission (Fig. 4).
The dotted lines in the upper panel show the transmission with the frequency modulation (Y1) and that before this maximization (Y2).

In summary, the abnormal PMC behavior was originated from the unexpectedly large DC offset at the input of the SR560.
This caused the SR560 to produce the 1-MHz oscillation, which was applied to the laser PZT and resulted in frequency modulation of the laser.

The origin of the unexpected offset at the IMC CMS output is still under investigation.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 12:06 Tuesday 17 November 2026 (37862) Print this report
HWP device is unreachable
I heard guardian was stopped during the operation of INITIAL_ALIGNMENT guardian and then found that HWP device was unreachable from k1hwp.
Guardian log is as follows.
2026-11-17_02:52:21.237913Z -oStrictHostKeyChecking=no -i /kagra/apps/agilis/id_ed25519_agilis_p_callback x.x.x.x 1 1 ******* IFO_REFL
2026-11-17_02:52:21.652699Z VendorID 4173
2026-11-17_02:52:21.652699Z ProductID 12294
2026-11-17_02:52:21.655325Z Traceback (most recent call last):
2026-11-17_02:52:21.655325Z File "/kagra/apps/agilis/agilis-p_control_with_callback.py", line 387, in
2026-11-17_02:52:21.655325Z node, channel, axis, cur_pos = main(device)
2026-11-17_02:52:21.655325Z File "/kagra/apps/agilis/agilis-p_control_with_callback.py", line 298, in main
2026-11-17_02:52:21.655325Z device.init(iserial,axis)
2026-11-17_02:52:21.655325Z File "/kagra/apps/agilis/agilis-p_control_with_callback.py", line 46, in init
2026-11-17_02:52:21.655325Z raise ValueError('Device is not connected')
2026-11-17_02:52:21.655325Z ValueError: Device is not connected


I also tried to directly access the USB devices on k1hwp, but valid device cannot be found. This means that we need to try rebooting k1hwp once. After the reboot, finding 0 position of HWP is necessary and it requires to stop INITIAL_ALIGNMENT guardian once. But current INITIAL_ALIGNMENT guardian has user code error as follows.
File "/opt/rtcds/userapps/release/lsc/k1/guardian/INITIAL_ALIGNMENT.py", line 4, in
from lsclib import check_io, check_als_x, check_als_y, check_ir_x, check_ir_y, check_ir_x_or_y, check_prmi3f, check_src1f, check_omc, check_srmi1f, check_drmi
ImportError: cannot import name 'check_ir_x_or_y' from 'lsclib' (/opt/rtcds/userapps/release/asc/k1/guardian/lsclib.py)

Because of this error, some guardian command doesn't work and I cannot understand why INITIAL_ALIGNMENT guardian works now with such fundamental code bug.

Unfortunately we have no time to fix it today's daytime due to the fire drill. It will be fix later.
Comments to this report:
takahiro.yamamoto - 17:55 Tuesday 17 November 2026 (37865) Print this report
[Ikeda, YamaT]

We found finally that the HWP issue was caused by missing packages on which the script depended, so we installed the necessary packages on k1grd1. Installation manual of the guardian server was also updated (klog#17316).

Since testing the Guardian code does not extend to checking external code called via `subprocess` (as this requires running the code on an actual device to be considered a valid test), this issue had been overlooked. Because it increases the difficulty of migration, the use of `subprocess` in Guardian should be avoided. Alternative methods include `Threading` and `concurrent.future`.

By the way, we found two lsclib.py as
- lsc/common/guardian/lsclib.py
- asc/k1/guardian/lsclib.py
Which one is called depends on the Python path order: if a current hard-coded configuration file is used, the `lsc` version is called, while in an automatically generated environment, the `asc` version (which appears first in alphabetical order) is called. Which code was actually used in O3GK and O4a/c? Science Mode may be no longer reliable. Stop such sloppy quality management and operation.

hirose.chiaki - 18:07 Tuesday 17 November 2026 (37866) Print this report

As a temporary workaround, I renamed `lsclib.py` in the `asc` directory to `lsclib_asc.py`.

FCL (Air)
shinji.miyoki - 10:27 Tuesday 17 November 2026 (37861) Print this report
Comment to Tehrmometer Change and #1 Precision cooler operation start (37848)

The figure showed the temp changes of PT01 ~ 06. 

  • All temp started decreasing after the start of DGS maintenance.
  • PT04, which was touched with the replaced thermometer, showed an instant increase because of my finger touch.
  • All PTs showed increasing by 1) DGS recovery and the target temp of #1 from 21.1 to 21.5 to speed up the temp recovery.
  • I reduced the target temp from 22.5 to 22.2 to compensate for too much heat-up. 
Images attached to this comment
FCL (Air)
shinji.miyoki - 10:26 Tuesday 17 November 2026 (37858) Print this report
Comment to Tehrmometer Change and #1 Precision cooler operation start (37848)

When we scan the PMC length by PZT, two or three peaks can be seen when TEM00 resonates. Actually, all higher-mode resonances seem to have double (triple) peaks. 

So, some strong frequency modulation might be added from somewhere. 

FCL (Air)
shinji.miyoki - 10:26 Tuesday 17 November 2026 (37848) Print this report
Tehrmometer Change and #1 Precision cooler operation start

[miyoki, miyakawa]

Abstract

#1 precision cooler operation started. The position of its reference thermometer was changed. The PID parameters of the #1 precision cooler were adjusted. Then we stopped #2 precision cooler for the near-future inverter maintenance.

 

Background

Error 093 was shown on the #2 precision cooler. This means the inverter's remaining life. Before changing the inverter, we decided to operate the #1 precision cooler, which had been off for a long time, instead of the #2 precision cooler, which had been in use for a long time.

 

Process

For laser safety, the laser was turned off by Miyakawa-kun during my work. Off the amp, off the master laser. (We did not remember whether the noise eater was on or off.)

To operate #2 and to stop #1, we need to change the thermometer position that is used for the temperature reference to keep the constant temperature injection, from at the side of the PMC to at the duct outside the PSL room as #1 (klog#28317). Also, we need to adjust the PID parameters of #1. According to the PID settings of #2, PID = 9.9, 72, and 18. So we changed them for #1 from 7, 45, and 10 to 9.9, 72, and 18., temporally.

We replaced the thermometer position on the air injection duct from the #1 precision cooler as in photos 1, 2, and 3.

We restarted the #1 precision cooler initially with 21.09C target temperature that is the same to the #1's. Before that, we opened the entrance of the PSL room to avoid too much pressure inside the PSL room by operating both #1 and #2 precision coolers.  After the temp stabilization of the air from the #1 precision cooler, we stopped the #2, closed the PLS room's door again, and waited for the stabilization of temps on the PSL optical table. Because the stabilization performance seems to have oscillations, I performed auto PID parameter tuning. Then the parameters became 1.8, 71, and 18.

We are still monitoring the PT01~ PT06 temperatures.

Additional Note

Fujimoto-kun and Hirose-san reported that the PMC trans power decreased a lot! We noticed that the PT04 thermometer, which is set beside PMC, showed a decreasing trend from around AM10:00 by 0.1C. Our work started around PM1:30. According to YamaT-san, he suspected that the PMC body's temperature decreased without heating up in the PMC control. So, one possibility is deformation of the PMC.

Images attached to this report
Comments to this report:
shinji.miyoki - 10:26 Tuesday 17 November 2026 (37858) Print this report

When we scan the PMC length by PZT, two or three peaks can be seen when TEM00 resonates. Actually, all higher-mode resonances seem to have double (triple) peaks. 

So, some strong frequency modulation might be added from somewhere. 

shinji.miyoki - 10:27 Tuesday 17 November 2026 (37861) Print this report

The figure showed the temp changes of PT01 ~ 06. 

  • All temp started decreasing after the start of DGS maintenance.
  • PT04, which was touched with the replaced thermometer, showed an instant increase because of my finger touch.
  • All PTs showed increasing by 1) DGS recovery and the target temp of #1 from 21.1 to 21.5 to speed up the temp recovery.
  • I reduced the target temp from 22.5 to 22.2 to compensate for too much heat-up. 
Images attached to this comment
ISC (General)
kentaro.komori - 3:05 Tuesday 17 November 2026 (37860) Print this report
Comment to [Important] Resonance splitting issue in the PMC (37859)

[Fujimoto, Komori]

Ushiba-san pointed out that this splitting could be caused by deep phase modulation, so we discussed this possibility.

If this hypothesis is correct, the modulation frequency can be estimated to be approximately 1.0 MHz from the peak separation of ~4 ms, the FSR corresponding to ~280 ms in the time-series data during the cavity scan, and the PMC FSR of 147 MHz.
In order for each first-order sideband to reach approximately half the height of the unmodulated resonance peak, the phase modulation depth needs to be approximately 2 rad.

Therefore, two possible scenarios are as follows:

  • A modulation of 3.1 Vpp at 1.0 MHz is applied to the laser PZT, with the laser PZT frequency actuation efficiency of 1.29 MHz/V (klog:36122).
  • A modulation of 3.2 Vpp at 1.0 MHz is applied upstream of the two HV amplifiers for the broadband EOM, with the effective EOM modulation efficiency of 1.25 rad/V (klog:35897) including the HV amplifiers (total gain: 200).
ISC (General)
Hiroki Fujimoto - 2:36 Tuesday 17 November 2026 (37859) Print this report
[Important] Resonance splitting issue in the PMC

[Sugioka, Hirose, T. Yamamoto, Komori, Tanaka (online), Ushiba (online), Miyoki, Fujimoto]

Abstract

After today’s work inside the mine was completed, we noticed that the PMC could not be locked.
Our investigation revealed that the PMC could not be locked because the resonance splitting prevented exceeding the locking threshold.
Although we could rule out several possible causes of the resonance splitting, as described in the Details section below, the actual cause has not yet been identified.
However, it is likely that the laser shutdown during today’s work (klog #37848) triggered this issue.
Tomorrow, we plan to restart the laser again to see if the situation improves.

Details

At around 17:05, after today’s maintenance and work inside the mine were completed, we tried to lock the IMC to resume interferometer commissioning.
However, we found that the PMC could not be locked.

We then checked the PMC cavity scan and noticed that the peak transmitted power (K1:PSL-PMC_TRANS_DC_OUT_DQ) was only about 9.7, approximately half of the value of 21.9 observed during the lock this morning, as shown in Fig. 1.
At the same time, the depth of the resonance dip in the reflected power (K1:PSL-PMC_REFL_DC_OUT_DQ) was also reduced by approximately half. Therefore, the reduction in transmitted power is unlikely to be caused by clipping of the PMC transmitted beam.

We also found that the peak, which appeared to be reduced by half, was actually split into two peaks when zoomed in, as shown in Fig. 2.
This suggests that the power, which originally reached 21.9, was distributed between the two peaks.

We investigated the cause of this splitting. Although we could not identify the actual cause, we were able to rule out the following possibilities.

(Ruled out) Just bad alignment

We adjusted the PMC input alignment using the pico motors. However, the transmitted power was already almost maximized in the initial alignment, and we could not suppress either of the two peaks.
Therefore, poor alignment is unlikely to be the cause.

(Ruled out) The input polarization was rotated by 45 degrees, causing s/p polarization resonance splitting

If the input polarization were rotated by 45 degrees and the observed double peaks were caused by s/p polarization resonance splitting in the PMC, the p-polarized component should be removed by the polarizer located after the EOM downstream of the PMC.
However, as shown in Fig. 3, both peaks remain in the PSL periscope transmitted power (K1:LAS-POW_PSL2_OUT_DQ).
Therefore, this hypothesis can be ruled out.

(Ruled out) Twisting of the PMC cavity axis, causing L/R polarization resonance splitting

If the PMC cavity axis were twisted and the observed double peaks were caused by L/R polarization resonance splitting, the power of each polarization component would be reduced by half by the polarizer downstream of the PMC.
In this case, both peaks would still be visible in the periscope transmitted power.
However, as shown in Fig. 4, the height of each split peak is approximately half of the periscope transmitted power observed during the PMC lock this morning.
If the splitting were caused by L/R polarization resonance splitting, the height of each peak should be reduced to one-quarter of the original value.
Therefore, this hypothesis can also be ruled out.

(Ruled out) Significant change in the laser output mode after the restart, causing a higher-order mode resonance comparable to TEM00

Since the laser was shut down once during today’s work in the PSL, we considered the possibility that the output beam mode had changed significantly after the restart, and that one of the double peaks corresponded to a higher-order mode resonance.
However, when we checked the higher-order mode peaks in the cavity scan, we found that these peaks were also split into two, as shown in Fig. 5.
Furthermore, when we slowly scanned the cavity and observed the transmitted beam with a CCD camera, we confirmed that the two peaks had the same spatial mode.
Therefore, we believe that both of the two largest peaks also correspond to the same TEM00 mode.

(Ruled out) Multimode oscillation near a mode hop

We considered the possibility that the laser temperature happened to be close to a mode-hopping point, causing multimode oscillation that appeared as the double peaks.
However, when we changed the laser temperature, multimode oscillation occurred at a certain temperature.
At this point, the height of the original peaks decreased by approximately half, and a new peak appeared at a different resonance frequency.
Furthermore, this new peak caused by multimode oscillation was also split into two.
Therefore, we ruled out the possibility that the observed resonance splitting was caused by the laser temperature.

Plans for Tomorrow

As described above, although we could rule out several possible causes, the actual cause of the resonance splitting remains unknown.
However, it is likely that the laser shutdown during today’s work in the mine (klog #37848) triggered this issue.
For example,  the restart may have worsened the RIN peak of the Mephisto laser at slightly below 1 MHz, causing this issue, or some problem may have occurred in the power amplifier.

Therefore, we plan to restart the laser again tomorrow to see if the situation improves.

Images attached to this report
Comments to this report:
kentaro.komori - 3:05 Tuesday 17 November 2026 (37860) Print this report

[Fujimoto, Komori]

Ushiba-san pointed out that this splitting could be caused by deep phase modulation, so we discussed this possibility.

If this hypothesis is correct, the modulation frequency can be estimated to be approximately 1.0 MHz from the peak separation of ~4 ms, the FSR corresponding to ~280 ms in the time-series data during the cavity scan, and the PMC FSR of 147 MHz.
In order for each first-order sideband to reach approximately half the height of the unmodulated resonance peak, the phase modulation depth needs to be approximately 2 rad.

Therefore, two possible scenarios are as follows:

  • A modulation of 3.1 Vpp at 1.0 MHz is applied to the laser PZT, with the laser PZT frequency actuation efficiency of 1.29 MHz/V (klog:36122).
  • A modulation of 3.2 Vpp at 1.0 MHz is applied upstream of the two HV amplifiers for the broadband EOM, with the effective EOM modulation efficiency of 1.25 rad/V (klog:35897) including the HV amplifiers (total gain: 200).
kentaro.komori - 14:42 Tuesday 17 November 2026 (37863) Print this report

[Miyakawa, Fujimoto, Sugioka, Hirose, Komori]

Abstract:

We resolved the issue related to the PMC and successfully locked it with the nominal transmitted power.

The issue was caused by phase modulation through the laser PZT.
An unexpected 5.8 V offset from the IMC CMS was applied to the SR560, causing the SR560 to overload and produce a large oscillation at approximately 1 MHz, and then applied to the laser PZT.

Details:

We entered the PSL room to investigate the PMC issue reported in the original post.
Upon entering the room, we found that the SR560 used as a 30-kHz low-pass filter immediately before the laser PZT actuator was indicating an overload condition (Fig. 1).

We then found that the SR560 output had a DC offset of 3.2 V together with an oscillation of 0.26 V at 1.1 MHz (Fig. 2), which was responsible for the observed ~1 MHz sidebands.
Please note that the voltage displayed on the oscilloscope was measured with a 50-Ω input impedance.
The oscillation amplitude was smaller than expected from the estimated modulation depth.
However, the actuator efficiency may be higher than our nominal estimate because the laser PZT has multiple mechanical resonances above 100 kHz.

Next, we found that the input to the SR560 had a DC offset exceeding 5 V, originating from the IMC CMS output.
For some reason, the slow-output offset at the final stage of the IMC CMS slow path (K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET) had increased to 5.8 V.
This value had remained at 0 V for a long period and suddenly went up to 5.8 V at 10:55 JST yesterday (Fig. 3).

After returning this offset to zero, the double-peak structure disappeared during the cavity scan. We then successfully locked both the PMC and the IMC.
Finally, we aligned the steering mirrors upstream of the PMC and maximized the PMC transmission (Fig. 4).
The dotted lines in the upper panel show the transmission with the frequency modulation (Y1) and that before this maximization (Y2).

In summary, the abnormal PMC behavior was originated from the unexpectedly large DC offset at the input of the SR560.
This caused the SR560 to produce the 1-MHz oscillation, which was applied to the laser PZT and resulted in frequency modulation of the laser.

The origin of the unexpected offset at the IMC CMS output is still under investigation.

Images attached to this comment
Hiroki Fujimoto - 16:04 Tuesday 17 November 2026 (37864) Print this report

I investigated other signals around the time when the IMC CMS slow-output offset changed (10:55:14 JST) and found that the IMC CMS IN1 switch had been turned on just before the offset change (Fig. 1).
Before this occurred, the IO Guardian had been down for more than an hour, and the IN1 switch had remained off.
However, it is still unclear why the IN1 switch was suddenly turned on and why the offset changed immediately afterward.

Images attached to this comment
takahiro.yamamoto - 3:09 Wednesday 18 November 2026 (37870) Print this report

> For some reason, the slow-output offset at the final stage of the IMC CMS slow path (K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET) had increased to 5.8 V.
Setting 5.8V to K1:IMC-SERVO_OFS_SLOWOUT_CALI_OFFSET seems default behavior of DOWN state of FSS guardian (see also attachment).
At line 25, offset value is defined as 5.825V
At line 205, offset value is set to EPICS channel.

I have no idea how to enter the run() function without executing the main() function when there is no 'return' in the main() function.
And also, it's strange that we haven't encountered this problem before.

If we won't use RefCav again, FSS guardian which is just a trouble maker should be removed.

Images attached to this comment
PEM (EX)
tatsuki.washimi - 21:37 Monday 16 November 2026 (37856) Print this report
Magnetic field measurments at X-arm

[Abe, Ohsawa, Washimi]

We start the magnetic field measurments at X-arm through a night time. Tow Mag-13MCL are used in this test.

  1. about 2.5~3.0 cm from the beam duct, Y- side
  2. about 300 cm from the beam duct, Y- side

Whitening filters are (4,5,6) for each channel.

We can see th Schumann resonances in the Z-axis of the sensor #1, for the first 2 min data.

Images attached to this report
Comments to this report:
tatsuki.washimi - 22:32 Tuesday 17 November 2026 (37868) Print this report

[Abe, Ohsawa, Washimi]

In this morning, just after the morning meeting, we cleaned our setup for other workers' passing. The battery had been empty around 2 a.m.
The Schumann resonanses are cleary found in the Z-axis of each sensors (and also the permanent outside sensors)

Images attached to this comment
tatsuki.washimi - 22:35 Tuesday 17 November 2026 (37869) Print this report

[Abe, Washimi]

In this eveneng, we restarted the measurments for tonight. Tow Mag-13MCL are used in this test.

  1. about 20 cm from the beam duct, Y- side
  2. about 200 cm from the beam duct, Y- side

We will clean them tomorrow morning.

Images attached to this comment
VAC (EX)
nobuhiro.kimura - 21:22 Monday 16 November 2026 (37855) Print this report
Comment to Vacuum leak test for EXC on Nov. 2 (37796)

[Kimura and Yasui]

 On November 16, we conducted another vacuum leak test on the EXC. For this retest, we used a helium leak detector, which differed from the one used in the previous test.
As a result, no vacuum leaks were detected at the flange section of the EXC that had been retightened, at a sensitivity of 1×10^-10 Pa·m³/s.
 Based on the above, we determined that the vacuum flange of the retightened EXC is leak-free and in good condition.

DGS (General)
takahiro.yamamoto - 19:39 Monday 16 November 2026 (37854) Print this report
Minor update of DAQ guardian code
After upgrading the guardian server, DAQ guardian doesn't work due to compatibility between the modern OS for the guardian server and the legacy server for the DAQ and Front-End servers. DAQ guardian can execute daqd restart and mx_stream restart via remote access to DAQ and Front-End servers.

In this case, remote access was failing because a method supported by the legacy OS had been disabled by default in the new OS. Therefore, we made changes to explicitly specify the old method for the legacy OS.

Several instances have begun to arise where the RCG/DAQ version is hindering upgrades to other servers, and it appears that upgrade plans for other servers will be affected in various ways until the RCG/DAQ upgrade is complete.
DGS (General)
takahiro.yamamoto - 19:18 Monday 16 November 2026 (37853) Print this report
Upgrade of guardian server
Guardian server was upgraded to the Debian13 system.
Because of the large jump in the python version, legacy syntax may makes user code errors.
If you will encounter user code errors, please fix them as necessary.

Related information can be found as follows.
- Upgrade procedure: JGW-T2617316
- Test of the new version of guardian: klog#36860
- Check of legacy code compatibility in the new version: klog#36860

-----
All nodes were able to be moved to the new guardian server, but we found one issue with recovery of the guardian process when guardian server is rebooted. Although Guardian relies on an NFS volume, the Guardian process does not automatically resume after an OS reboot because the NFS mount is not complete when the Guardian process is launched. This issue should normally be controlled using systemd’s `Wants`, `Requires`, `RequiresMountsFor`, and `After` settings, but these did not function as expected.

While it is possible to resume the process by manually starting them after a OS reboot, this problem should be resolved soon from a maintainability perspective.

VAC (IY)
takahiro.yamamoto - 18:50 Monday 16 November 2026 (37852) Print this report
Comment to Online Monitoring of the Pressure Gauge Inside the IYC Booth (37850)
The readout channel of vacuum level at ITMY was added to the DAQ, Guardian alert, and the Web trend monitor.
Related MEDM screens were also updated.
VAC (General)
koji.nakagaki - 17:00 Monday 16 November 2026 (37851) Print this report
Hardware Replacement for the Vacuum IOC Server 'sioc-vac-ix01' (Failure Contingency Test)

[Uchiyama, Nakagaki]

As a test of our hardware failure response procedures, we replaced the IOC server with a different hardware unit onto which the SSD had been cloned.
Just to be safe, we will keep the old server as is for the time being.

Images attached to this report
VAC (IY)
koji.nakagaki - 16:55 Monday 16 November 2026 (37850) Print this report
Online Monitoring of the Pressure Gauge Inside the IYC Booth

[Uchiyama, Nakagaki]

We have connected the pressure gauge of the IYC cryostat to the network.
The readings are provided via the following PV:

K1:VAC-PRESSURE_Y_ITMY

Images attached to this report
Comments to this report:
takahiro.yamamoto - 18:50 Monday 16 November 2026 (37852) Print this report
The readout channel of vacuum level at ITMY was added to the DAQ, Guardian alert, and the Web trend monitor.
Related MEDM screens were also updated.
DGS (General)
takahiro.yamamoto - 9:42 Monday 16 November 2026 (37849) Print this report
Comment to k1mon9 was dead (37844)
k1mon9 was recovered.
It was constructed as the new Debian13 system.
ISC (General)
Hiroki Fujimoto - 9:10 Monday 16 November 2026 (37846) Print this report
DRMI 3f lock trial using REFL135-Q

[Sugioka, Fujimoto]

Abstract

We decoupled the DRMI 3f signals using REFL51-I/Q and REFL135-Q and attempted to lock the DRMI with the 3f signals.
The decoupling was generally successful, except for the PRCL-to-MICH coupling, which remained at approximately +6 dB.
We succeeded in handing over both PRCL and SRCL to the 3f signals and maintained the lock for approximately 1 minute.
Also, we succeeded in handing over MICH alone to the 3f signal, but the lock lasted only about 10 seconds...

Background

Previous investigations (klog #37842, klog #37840, klog #37833) suggested that the MICH signal in REFL51-Q is weaker than before and that REFL135-Q could potentially be used as the MICH signal for the DRMI 3f lock.
Therefore, we performed the decoupling of the 3f signals using REFL135-I/Q and REFL51-I.
The decoupling was performed while the DRMI was locked with the 1f signals. When exciting a specific DOF, we applied notch filters to prevent the other DOFs from being excited through sensor coupling.

Decoupling of the 3f Signals

Phasing of REFL135

We adjusted the demodulation phase of REFL135 to minimize the peak in REFL135-Q when exciting PRCL.
Fig. 1 shows the spectra before and after the adjustment.
The demodulation phase was changed as follows:

  • K1:LSC-REFL_PDA2_RF135_PHASE_R: -119.80 → -119.40

Phasing of REFL51

We attempted to adjust the demodulation phase of REFL51 to minimize the peak in REFL51-Q when exciting SRCL.
However, since the decoupling was already sufficient with the current setting, we did not change the demodulation phase.
Fig. 2 shows the REFL51-I/Q spectra when exciting SRCL.
The demodulation phase remained unchanged:

  • K1:LSC-REFL_PDA2_RF51_PHASE_R: 145.00 (unchanged)

Reduction of PRCL-to-SRCL Coupling

We reduced the PRCL-to-SRCL coupling by subtracting REFL135-I from REFL51-I.
Specifically, we adjusted the subtraction coefficient to minimize the peak in REFL51-I when exciting PRCL.
The resulting signal was sent to CARM_IN1 to check the reduction in the spectrum.
Fig. 3 shows the coupling before and after the adjustment. The coupling was reduced to approximately 1/20 of its original level.
The resulting input matrix elements were:

  • REFL51-I to CARM: 1
  • REFL135-I to CARM: -0.192

Reduction of SRCL-to-PRCL Coupling

We reduced the SRCL-to-PRCL coupling by subtracting REFL51-I from REFL135-I.
Specifically, we adjusted the subtraction coefficient to minimize the peak in REFL135-I when exciting SRCL.
The resulting signal was sent to CARM_IN1 to check the reduction in the spectrum.
Fig. 4 shows the coupling before and after the adjustment. The coupling was reduced to approximately 1/9 of its original level.
The resulting input matrix elements were:

  • REFL135-I to CARM: 1
  • REFL51-I to CARM: -1.3

Reduction of SRCL-to-MICH Coupling

We attempted to reduce the SRCL-to-MICH coupling by subtracting the SRCL signal from REFL135-Q.
Specifically, we planned to subtract the SRCL signal obtained in the SRCL-to-PRCL decoupling described above, so that the peak in REFL135-Q when exciting SRCL would be minimized.
The SRCL signal was sent to DARM_IN1, while the signal after subtraction was sent to CARM_IN1.
However, as shown in Fig. 5, there was already no coherence between the SRCL signal and REFL135-Q. Therefore, we did not apply the subtraction.

OLTF Measurements

We adjusted the overall gains of the input matrix elements so that the OLTFs using the newly obtained PRCL, SRCL, and MICH signals matched those before the decoupling adjustment.
For the measurements, the PRCL, SRCL, and MICH signals were sent to the DARM, XARM, and CARM filter banks, respectively.
Figs. 6, 7, and 8 show the measured OLTFs of PRCL, SRCL, and MICH, respectively.
The resulting input matrix elements were as follows:

PRCL

  • REFL135I to DARM: 0.164
  • REFL51I to DARM: -0.213

SRCL

  • REFL51I to XARM: 4.28
  • REFL135I to XARM: -0.821

MICH

  • REFL135Q to CARM: 22.6

Coupling After Decoupling

Fig. 9 summarizes the coupling measured after the decoupling adjustment.
PRCL, SRCL, and MICH correspond to DARM, XARM, and CARM in the figure, respectively.
With the newly decoupled signals, PRCL and SRCL could be sensed with their own signals dominating over the contributions from the other DOFs.
However, for MICH, which was our main concern, the coupling from PRCL remained at approximately +6 dB. Therefore, we could not decouple the MICH signal sufficiently for the MICH contribution to dominate.

3f Lock Trial

PRCL/SRCL 3f Handover

We successfully handed over both PRCL and SRCL to the 3f signals while the DRMI was locked with the 1f signals and ADS was turned off.
The following settings were used:

  • PRCL: PRCL1 gain = 1.5
  • SRCL: SRCL1 gain = 0.7, BST0.1-1 ON

Although no oscillation was observed, the lock lasted only up to approximately 1 minute.

MICH 3f Handover

We also succeeded in handing over MICH alone to the 3f signal while the DRMI was locked with the 1f signals and ADS was turned off (Fig. 10).
The following settings were used:

  • MICH: MICH1 gain = 6, ELP500 → ELP100, offset = 0

However, the lock lasted only about 10 seconds, although neither oscillation nor saturation of the feedback signal was observed.

Plans for Tomorrow

  • Try further tuning of the control filters for MICH to see whether a stable 3f lock can be achieved.
  • Try increasing the input power to REFL PD to improve SNR.
  • Slightly change the modulation frequency and investigate whether the 3f signals change.
  • If possible, try changing the modulation index as discussed with Komori-san and Ushiba-san. The current REFL135-Q has approximately 0.6 times the MICH sensitivity of REFL51-Q, which was previously used for the 3f lock, while their noise floors are at similar levels (klog #37840). Since the 3f signal is proportional to the square of the modulation index, increasing the modulation index by a factor of √2 might allow us to obtain an SNR in REFL135-Q comparable to that previously obtained with REFL51-Q.
Images attached to this report
ISC (General)
satoru.takano - 5:44 Monday 16 November 2026 (37847) Print this report
Finesse simulation of the sensing gain with the latest ISC parameters

Revision of this post.

I modified the parameters in Finesse to reflect the latest updates to the main interferometers, including PRCL/SRCL measurements and changes in modulation frequencies. The entire simulation code can be found here.

Parameters in the simulation:

  • Interferometer length (from klog37505)
    • PRCL: 66.59625 m
    • SRCL: 66.61860 m
    • Schnupp asym.: 3.3384 m
  • The seed frequency of the phase modulation

The attached plots show the sensing gain of each RF signal ([f1, f2], [1f, 3f]) for each DoF in DRMI. The effect of the change in modulation frequency is not significant, except for PRCL coupling to RF51Q (Fig. 6), which was reduced by ~30 times compared to before the change. These results also do not show degradation of the sensing gain for MICH in RF51Q.

Note that the simulation doesn't include any higher-order modes or birefringence effects so that the signal degradation may be due to these effects.

Images attached to this report
Search Help
×

Warning

×