Reports of 34958
VIS (IY)
ryutaro.takahashi - 17:11 Friday 16 October 2026 (37686) Print this report
Comment to Offload of GAS filters (36614)

I offloaded the BF GAS with the FR.

CAL (YPcal)
Misato Onishi - 14:01 Friday 16 October 2026 (37685) Print this report
Comment to New laser noise check (37371)

Detailed report: link

FCL (General)
shoichi.oshino - 12:42 Friday 16 October 2026 (37684) Print this report
Machine Room Tent Dehumidifiers Turned Back On
[Ikeda, Oshino]

We found that dehumidifiers inside the tent in the machine room were not operating.
It is likely that the unit stopped during the power outage in September.
We turned on all dehumidifiers inside the tent and confirmed that they resumed operation.
ISC (ASC)
takafumi.ushiba - 11:56 Friday 16 October 2026 (37683) Print this report
Comment to Initial alignment OMC (37668)

After recovery of the OMC PZT driver, OMC can be successfuly locked and initial alignment can be done (fig1)

Images attached to this comment
PEM (Center)
takaaki.yokozawa - 10:21 Friday 16 October 2026 (37682) Print this report
Status of the ground motion during DRMI lock trial
I checked the status of the ground motion yesterday and today (during DRMI lock trial)

Red : around the 2026/10/16 8:00(JST)
Blue : around the 2026/10/15 15:00 (JST)

In blue case,
1- 30 Hz had larger ground motion in IXV seismometer, that imply the construction work around atotsugawa river.
Microseismic motion was larger, peak was about 0.25 Hz
Ground motion below 0.05 Hz was larger in EYV seismometer XY direction (tilt motion? that issue appeared regularly )

In red case,
microseismic motion became smaller, the level was close to the silent case.
But the peak at 0.05 Hz appeared, especially in X direction, some interesting wind direction?
Images attached to this report
ISC (General)
Hiroki Fujimoto - 2:52 Friday 16 October 2026 (37681) Print this report
Recovery of DRMI 1f/3f Lock

[Hirose, Yokozawa, Ushiba, Fujimoto]

Abstract

We successfully recovered both the DRMI 1f and 3f locks.
For the DRMI 1f lock, we also recovered the ADS, and the lock duration reached approximately 20 minutes.
For the DRMI 3f lock, the lock duration was recovered to approximately 9 minutes, although the ADS has not yet been tested.

However, I observed strange lock transitions during the 3f lock, in which the AS DC signal suddenly increased and then returned to its original level.
The cause of this behavior is still unknown and requires further investigation.

Details: DRMI 1f Lock

Earlier today, the IFO LO amplitude was increased from 10 dB to 13 dB (klog 37678), which resolved the issue of the low POP90 signal during the PRMI lock (klog 37667).
We then proceeded with the recovery of the DRMI 1f lock.


Recovery of the 1f Lock

The following modifications were made to recover the DRMI 1f lock.

  1. Restoration of filter settings
    There are several filters in MICH, PRCL, and SRCL that must remain enabled during the DRMI lock but are not automatically turned on or off by the VERTEX Guardian.
    We compared the current filter settings with those before the power outage and restored the necessary filters to their previous states.
     
  2. Correction of the ELP filter settings
    We noticed that the MICH ELP100 filter was being enabled by the PREP_FM_FOR_DRMI of the VERTEX Guardian, although ELP300 must have been used for the 1f lock before.
    It is possible that ELP100 was mistakenly implemented in a way that also affected the 1f lock during the last DRMI 3f commissioning before the F2F meeting.
    We therefore modified the Guardian so that ELP300 is enabled in PREP_FM_FOR_DRMI, while ELP100 is enabled only in LOCKING_DRMI_3F.

After these modifications and the additional initial alignment, we successfully recovered the DRMI 1f lock.
The gains and offsets were left unchanged from the values already implemented in the Guardian.
Fig. 1 shows a screenshot of the setup during the DRMI 1f lock.
The maximum lock duration was approximately 20 minutes.

We also noticed that the POP90 and AS34 signals were approximately 1.44 and 1.35, respectively, which were significantly higher than their previous values of approximately 1.
This is likely because the IFO LO amplitude before the power outage was lower than the 13 dB setting used today, although we do not have an exact record of the previous amplitude.


OLTFs

Figs. 2, 3, and 4 show the OLTFs of MICH, PRCL, and SRCL measured during the DRMI 1f lock, respectively.
No significant abnormalities were observed.
A few comments on the comparison with the reference measurements from August 15:

  • MICH: The measured OLTF gain was approximately 10 dB higher than the reference. This is because the MICH1 gain was increased during the implementation of the DRMI ADS after August 15.
  • PRCL: The measured OLTF gain was approximately 4 dB lower than the reference. It is possible that some gain settings have been changed since August 15.
  • SRCL: The measured OLTF was almost identical to the reference.


ADS

We tested the DRMI ADS that was implemented during the last DRMI commissioning before the F2F meeting (klog 37407).
The ADS worked properly for IMMT2, PRM, and BS. However, when the SRM ADS was enabled, the SRM alignment changed rapidly.
Upon investigation, we found that the signal demodulated at the SRM dither frequency contained not only the intended AS34 signal but also the POP DC signal.
The POP DC signal had been used for the SRM initial alignment, but it was not disabled when the ASC_LOCK Guardian went down.
As a result, the POP DC signal was unintentionally included in the DRMI ADS.

We modified the ASC_LOCK Guardian to resolve this issue, after which the SRM ADS also worked properly.
Fig. 5 shows a screenshot of the setup with the ADS enabled.


Details: DRMI 3f Lock

Recovery of the 3f Lock

The following modifications were made to recover the DRMI 3f lock.

  1. Adjustment of the REFL HWP angle
    We noticed that the incident power on the REFL DC PD was approximately 30 mW.
    This was caused by the HWP rotary encoder losing its position information due to the power outage (klog 37518).
    We therefore changed the HWP setting from 146 deg to 166 deg to reduce the incident power on the REFL DC PD to 10 mW.
    We also updated the corresponding setting in the VERTEX Guardian.
     
  2. Adjustment of the MICH1 gain
    The MICH1 gain had been set to 9 to increase the UGF during the 1f lock.
    However, with this gain setting, applying ELP100 to MICH resulted in insufficient phase margin and caused oscillation.
    I therefore modified the VERTEX Guardian so that the MICH1 gain is reduced to 2 for the 3f lock.
     
  3. Adjustment of the MICH1 offset
    The MICH1 offset was originally set to 2 in the Guardian.
    However, I noticed that the AS DC signal exceeded 0.01 during the lock, whereas it should normally remain below 0.01 in the DRMI configuration.
    I therefore adjusted the MICH1 offset to minimize the AS DC signal.
    I found that changing the offset from 2 to 10 minimized the AS DC signal to below 0.01 and allowed the lock to remain stable.

With these adjustments, we successfully recovered the DRMI 3f lock.
Fig. 6 shows a screenshot of the setup during the DRMI 3f lock.
The maximum lock duration was approximately 9 minutes.
The ADS operation has not yet been tested for the 3f lock.
 

*Note: Strange Lock Transition

During the DRMI 3f lock, I repeatedly observed a strange behavior in which the AS DC signal suddenly increased to approximately 0.02–0.03 and returned to its original level a few seconds later.
Fig. 7 shows an example of this behavior.
Since the change occurred almost instantaneously, it appeared as if the interferometer had transitioned to a different lock point.
I also observed that the TEM00 mode image on the AS camera became brighter during this transition.
This behavior was not observed during the 1f lock, and its cause remains unknown.
Further investigation is needed to understand this phenomenon.

Images attached to this report
ISC (General)
hirose.chiaki - 23:50 Thursday 15 October 2026 (37673) Print this report
Cavity scan remeasurement with increased TMSX DCPD gain

[Fujimoto, Yokozawa, Ushiba, Hirose]

Continued from klog37670

Summary

Upon changing the IMC LO from 7.4 dBm to 10 dBm, the IRX successfully locked.(klog37678) In this state, the MIF LO was set to 10 dBm and 13 dBm, and cavity scans were performed for each.

For these measurements, the IMC transmission power was set to 1 W, and the DCPD gain of the TRANS IRX was increased by 40 dB.

The modulation index of SB2, determined from the cavity scan, was 0.0959 when the MIF LO was 10 dBm and 0.1399 when it was 13 dBm. The ratio of the modulation indices was approximately 1.46, which was broadly consistent with the expected value of approximately √2 resulting from a 3 dB increase in RF power.

After the measurement, the DCPD gain on the TRANS IRX was returned to 0 dB.

Details

  • The basic preparation procedure followed klog36322. However, the term ‘IMC-SERVO_COMBOOST’ mentioned in Step 6 of the Notes section of klog36322 is a mistake; it should read ‘CARM-SERVO_COMBOOST’. When carrying out the procedure in Note 6, the GRX unlocked. When measuring the UGF with one stage of the COMBOOST filter engaged, the phase margin was located on the low-frequency side of the Phase Bubble’s peak. In this case, the gain would need to be increased by approximately 8 dB to align the UGF with the peak of the Phase Bubble. However, simply increasing K1:LSC-CARM_SERVO_IN2GAIN from 15 dB to 16 dB caused the control to become unstable, resulting in the system losing lock. As the cause remains unknown at this stage, measurements were carried out this time with only one stage of the COMBOOST filter engaged.

  • A cavity scan was performed under the following conditions.

    IMC LO: 10 dBm (previously: 7.4 dBm)

    MIF LO: 10 dBm, 13 dBm

    IMC transmitted power: 1 W

    TRANS IRX DCPD gain: 40 dB increase compared to the previous setup

    The measurement results are shown in FIG 1 (10 dBm) and FIG 2 (13 dBm).

    In this study, the modulation index was calculated from the TEM00 resonance peaks of the Upper and Lower SB2. Note that the Upper SB1 was excluded from this evaluation because the resonance peak of the first-order transverse mode was very close to the TEM00 peak, making it impossible to accurately identify the TEM00 peak.

  • When the MIF LO was changed from 10 dBm to 13 dBm, the modulation index of SB2 increased by a factor of approximately 1.46. A 3 dB increase in RF power results in an RF voltage approximately √2 times greater. Assuming that the modulation index is proportional to the RF voltage, one would expect the modulation index to increase by a factor of approximately 1.41. The results of these measurements are broadly consistent with this expectation.

  Modulation index=2*sqrt({The average of the TEM00 power in the upper and lower SB2} / carrier TEM00 power)
LO10dBm 2 * sqrt((0.222209 + 0.228785) / 2 / 98.003189)=
0.095936
LO13dBm 2 * sqrt((0.496847 + 0.513378) / 2 / 103.256147)=0.139883
Images attached to this report
CAL (Gcal general)
takahiro.yamamoto - 21:20 Thursday 15 October 2026 (37680) Print this report
Comment to Whitining filter works not well @ KEK (37675)
Is "0" you said same as the definition of the config board?
“0” by the config board should be “ON” for the universal whitening filters if my memory is correct.

What point in the analog path is the voltage you said referred to?
Voltage that absolute value is larger than 20V is saturated at ADC. So the input voltage of ADC calibrated by using the count at ADC becomes within +/-20V. In addition, a calibrated voltage at other points by using the count at ADC becomes also within +/-20V because a signal path on your setup doesn't have an attenuator like component if your calibration is correct. On the other hand, your plot shows larger voltage than +/-20V and also doesn't show behavior of saturation. So I guess the calibration from the ADC count to the voltage at some point is wrong.
ISC (General)
takafumi.ushiba - 20:05 Thursday 15 October 2026 (37678) Print this report
LO amplitude changes

[Fujimoto, Hirose, Yokozawa, Ushiba]

Abstract:

We changed IMC and IFO local oscillators' amplitude to 10.4 dBm and 13.0 dBm, which were 7.4 dBm and 10.0 dBm, respectively.
After that, we measured the OLTF of IMC and IRX loops, and confirmed that they are almost consistent with those measured before.

Detail:

As reported in klog37656, IMC UGF is lower than before (klog35394), so we investigated the reason.
Though IMC LO amplitude is nominal (7.4 dBm, which is written on the signal generator), LO amplitude was 10.4 dBm after the planned power outage in March according to the photo in notion page.
So, we set LO amplitude to 10.4 dBm and measured the OLTF (fig1).
Then, the UGF becomes 120 kHz, which is almost same as before.

After that, we increased IFO LO amplitude from 10 dBm to 13 dBm, which should be nominal according to the spec of the harmonic generator (JGW-D1808028-v5).
Though IRX could not be locked with 13 dBm amplitude the day before yesterday, it can be locked without any problems this time.
Figure 2 shows the OLTF of IRX loop with 13 dBm LO amplitude, whose UGF is 11 kHz that is same or slightly high compared with the previous measurement (though we didn't measure IRX OLTF for a long time, it should be -20dB around 100kHz according to klog35455).

After increasing LO amplitude, we locked PRMI and confirmed that POP90 value is slightly higher than before (fig3: Y cursor in the top left pannel shows the POP90 when PRMI was locked with 3F before the blackout).
We are not so sure the reason but it might be due to the LO amplitude is slightly higher than before the unexpected blackout (which was 12.3 dBm after the planned power outage on March 2026).

Anyway, the strange points in IMC, IRX, and PRMI seemed to be resolved by increasing LO amplitude.

Note:

For the future references, I summarized current ISC related signal generator setting in the nortion page.

Images attached to this report
DGS (General)
takahiro.yamamoto - 18:13 Thursday 15 October 2026 (37677) Print this report
Comment to Hang-up of models on K1MCF0 (37672)
Upon visual inspection of the MCF0 rack, the following findings were confirmed:
  • The speaker amplifier is OFF.
  • The 18 V and 24 V voltages measured at the power strips are within the normal ranges.
  • All circuits appear to be operating normally, and no abnormalities were observed in the indicators.
  • No abnormalities were observed in the indicators inside the I/O chassis.
  • The 3 V, 5 V, and 12 V voltages measured on the boards are all within the normal ranges.
  • The Timing Slave indicator indicates that synchronization is in progress.

Additionally, since the Real-Time Front-End (RTFE) is accessible via login, it was confirmed that the kernel is still responsive. Furthermore, the lspci command showed that the PCIe devices in the I/O chassis are not detected. This suggests that the issue is not simply an ADC timeout caused by a timing glitch. Therefore, a disconnection or failure in the PCIe link between the I/O chassis and the RTFE is suspected.

At this stage, we have not yet determined whether the issue is related to the 24 V power supply, including the power supplied to the boards inside the I/O chassis, or to the PCIe connection itself. If the issue is power-related, it may be necessary to shut down the IMC0 rack, which shares the same power supply unit (PSU) as the I/O chassis.

For this reason, we have decided to defer recovery operations until the scheduled maintenance window on Monday.
CAL (Gcal general)
Kohei Mitsuhashi - 17:32 Thursday 15 October 2026 (37675) Print this report
Whitining filter works not well @ KEK
[Mitsuhashi, Yokozawa, Washimi, Dan]

Whitening Filter Test and Abnormal Output


Today, we tested the whitening filter (D1302087) used in the magnetic field measurement system.

1. Increase in Noise with Analog Signal In Disconnected


The configuration card was inserted into the whitening filter, with all switches set to 0 (OFF).
The Analog Out was connected to the AA system, while the Analog Signal In (D-sub 15-pin) was left disconnected.
When the whitening filter was powered on, the RMS noise increased from approximately 0.0003 V to 0.0006 V.
This increase was observed on both Board 1 and Board 2.


2. Abnormal Output with the D-sub 15-pin Connected


On Board 2, the Analog Signal In (D-sub 15-pin) was connected to a conversion box that adapts the pin configuration for the magnetometer.
The magnetometer itself was not connected to the conversion box.
All switches on the configuration card were set to 0 (OFF).
When the whitening filter was powered on, an abnormal output reaching approximately 20 V was observed at Analog Out.
The waveform appeared to be oscillating, but the cause has not yet been identified. The Picture was attached.

To prevent possible damage to the circuit, we decided to stop further testing today after consulting with Yokozawa-san.
At present, the problem may be related to the internal wiring or grounding of the conversion box, but the cause remains unclear.
We plan to check the pin assignments and continuity of the wiring in the conversion box.
Images attached to this report
Comments to this report:
takahiro.yamamoto - 21:20 Thursday 15 October 2026 (37680) Print this report
Is "0" you said same as the definition of the config board?
“0” by the config board should be “ON” for the universal whitening filters if my memory is correct.

What point in the analog path is the voltage you said referred to?
Voltage that absolute value is larger than 20V is saturated at ADC. So the input voltage of ADC calibrated by using the count at ADC becomes within +/-20V. In addition, a calibrated voltage at other points by using the count at ADC becomes also within +/-20V because a signal path on your setup doesn't have an attenuator like component if your calibration is correct. On the other hand, your plot shows larger voltage than +/-20V and also doesn't show behavior of saturation. So I guess the calibration from the ADC count to the voltage at some point is wrong.
ISC (ASC)
takafumi.ushiba - 13:57 Thursday 15 October 2026 (37674) Print this report
Comment to Initial alignment OMC (37668)

[Hirose, Ushiba]

We turned on OMC PZT driver and confirmed OMC length can be scaned by PZT offsets (fig1).
Since +/- 18 V for the circuit is provided by the external power supply, we set the voltage of +/- 18 V and the current limit of +/- 0.5 A.

Note:

During the recovery work of OMC PZT driver, we found that DC 100V power supply is ON (fig2) though the main power is turned off.
I don't know te detail of the power supply but it is likely that DC 100V was automatically recovered after the unexpected blackout.
If this situation is not good for PZT driver, we need to consider how to avoid it.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 10:07 Thursday 15 October 2026 (37672) Print this report
Hang-up of models on K1MCF0
Real-time models on K1MCF0 hung-up at 01:01:28 JST.
Affected models are k1iopmcf0, k1pemmcf0, and k1pemmanage.

Because K1IMC0 is alive, it's not related to the problem on the power supply unit reported as klog#37524.
Though I'm not sure the large speaker was enabled as the recovery work from the unexpected blackout on Sep. 21st.
it may be a same issue as klog#25343, klog#29433, and klog#33565.
Comments to this report:
takahiro.yamamoto - 18:13 Thursday 15 October 2026 (37677) Print this report
Upon visual inspection of the MCF0 rack, the following findings were confirmed:
  • The speaker amplifier is OFF.
  • The 18 V and 24 V voltages measured at the power strips are within the normal ranges.
  • All circuits appear to be operating normally, and no abnormalities were observed in the indicators.
  • No abnormalities were observed in the indicators inside the I/O chassis.
  • The 3 V, 5 V, and 12 V voltages measured on the boards are all within the normal ranges.
  • The Timing Slave indicator indicates that synchronization is in progress.

Additionally, since the Real-Time Front-End (RTFE) is accessible via login, it was confirmed that the kernel is still responsive. Furthermore, the lspci command showed that the PCIe devices in the I/O chassis are not detected. This suggests that the issue is not simply an ADC timeout caused by a timing glitch. Therefore, a disconnection or failure in the PCIe link between the I/O chassis and the RTFE is suspected.

At this stage, we have not yet determined whether the issue is related to the 24 V power supply, including the power supplied to the boards inside the I/O chassis, or to the PCIe connection itself. If the issue is power-related, it may be necessary to shut down the IMC0 rack, which shares the same power supply unit (PSU) as the I/O chassis.

For this reason, we have decided to defer recovery operations until the scheduled maintenance window on Monday.
CRY (Cryostat EX)
nobuhiro.kimura - 8:58 Thursday 15 October 2026 (37671) Print this report
Comment to Opened a side flange of EXC (37587)

[Kimura]

 I am attaching a trend graph.
The partial pressure of H₂O shows a downward trend.

Images attached to this comment
ISC (General)
hirose.chiaki - 23:01 Wednesday 14 October 2026 (37670) Print this report
Cavity scan to investigate the reduction in modulation index

[Fujimoto, Ushiba, Hirose]

Summary

It was confirmed that the POP RF90 signal was reduced at PRMI(klog37667). Currently, as the IRX failed to lock, the LO output is being operated at 10 dBm instead of 13 dBm (klog #37656). It has been suggested that the input-output characteristics of the harmonic generator may be non-linear, and we considered the possibility that the modulation index had decreased in line with the reduction in LO output. We therefore set the LO output to 10 dBm and 13 dBm and compared the sideband modulation index using a cavity scan. As a result, although the measurement result increased from 0.0038 to 0.006, It decreased from the previous reading of 0.01 (klog33306). At present, the cause of this reduction has not been identified. After measurement, the LO output was returned to 10 dBm(Fig1). We plan to continue investigating the cause from tomorrow onwards.

Details

  • The measurement results of cavity scan are as follows. (Although we had initially planned to use IRX_NORM for the evaluation, the sideband signals were buried in noise; therefore, we used the p-pol DCPD signal from TMSX.)
      sideband/TEM00
    LO output 10 dBm 0.18/47=About 0.0038(TEM00:Fig2, sideband:Fig3)
    LO output 13 dBm 0.3/48=About 0.006(TEM00:Fig4, sideband:Fig5)

    ** However, we have not yet been able to identify the peaks at each angular frequency.
    The measurement at 13 dBm is only about 60 per cent of the previous measurement of 0.01, and remains low. At present, we have been unable to identify the cause of the reduction in the modulation index to approximately 60 per cent of previous measurement values, occurring along the signal path from the LO through the various circuits to the EOM crystal. Furthermore, if this were due to variations in the interferometer’s alignment, one would expect to observe changes in the peak intensity of TEM00. However, no significant changes were observed in the TEM00 peak during these measurements. Accordingly, it is considered difficult to explain the current decrease in the modulation index solely by alignment variations. At present, the cause of the decrease in the modulation index compared to previous measurements remains unknown.

  • Once the measurements were complete, the LO output was reset to the current operating value of 10 dBm. From tomorrow onwards, we plan to continue investigating the cause of the reduction in the modulation index. In particular, with regard to the TMSX’s DCPD signal, we are considering whether adjusting the gain might reduce the impact of noise, thereby improving the measurement accuracy of the sideband signals.

Note

  • We followed the procedure for the cavity scan as described in klog36322.
  • If you request ALS_LOCKED whilst the IMC is locked, the low-frequency fluctuations in the MCL are fed back to the IR laser’s frequency. As these frequency fluctuations are also passed to the GR laser via the PLL, the GR laser’s frequency fluctuates. In order to maintain the GRX in a resonant state under these conditions, the feedback to the AOM increases, which exceed the control range of the AOM’s VCO. Consequently, the GRX lock becomes unstable.  To prevent this, the GRX’s RFPD signal must be fed back to the IMC’s MCL (MCE) on the low-frequency side(in the ‘Note’ section of klog36322). In particular, the steps outlined in the ‘Note’ section must be carried out immediately after requesting ‘ALS_LOCKED’ in Step 2 of the ‘Detail’ section of klog36322. Please note that any delay in taking this action will cause the GRX lock to become unstable for the reasons stated above.

  • In this cavity scan, measurements were taken under the following conditions:
    IMC output laser power: 10 W or more
    PRM state: MISALIGNED_FOR_LOCKAQ

  • The OFFSET application channel and ramp time for the cavity scan were based on klog33306. For this measurement, ‘-1’ was set for FM1 in the filter bank, and the OFFSET was applied by specifying the ramp time in diaggui. The filter bank settings can be checked by clicking on the relevant channel in diaggui. Whilst the sweep time should ideally be determined by taking cavity poles into account, in this instance I referred to the settings in klog33306. As the peak of TEM00 in IRX_NORM remained at a nearly constant value across each scan, I concluded that the sweep time set for this experiment was appropriate.

Images attached to this report
ISC (General)
takahiro.yamamoto - 18:35 Wednesday 14 October 2026 (37669) Print this report
Comment to Trial of the PRMI lock (37667)
Since the error message is missing from the traceback (only the stack trace is attached), this is merely a guess, but I suspect an NDS 'overloaded' error occurred.

I have heard that this script has been successfully tested in the past, so it should run correctly when the NDS server is under low load. But, NDS overload can occur depending on the situation, such as when other users are applying high loads to the NDS or when many test points remain un-released after use.

In such cases, waiting and re-executing the script, or releasing unnecessary test points, should resolve the issue.
ISC (ASC)
takaaki.yokozawa - 14:54 Wednesday 14 October 2026 (37668) Print this report
Initial alignment OMC
[Ushiba, Yokozawa]

We tried to perform the initial alignment OMC.
By changing the initial REFL HWP 125 to 140, we completed the increasing the laser power, but OMC cannot be locked.
Ushiba-san commented that maybe the power of pzt OMC was off, so we cannot change the OMC length.
We will check it when we enter the mine next time.
Comments to this report:
takafumi.ushiba - 13:57 Thursday 15 October 2026 (37674) Print this report

[Hirose, Ushiba]

We turned on OMC PZT driver and confirmed OMC length can be scaned by PZT offsets (fig1).
Since +/- 18 V for the circuit is provided by the external power supply, we set the voltage of +/- 18 V and the current limit of +/- 0.5 A.

Note:

During the recovery work of OMC PZT driver, we found that DC 100V power supply is ON (fig2) though the main power is turned off.
I don't know te detail of the power supply but it is likely that DC 100V was automatically recovered after the unexpected blackout.
If this situation is not good for PZT driver, we need to consider how to avoid it.

Images attached to this comment
takafumi.ushiba - 11:56 Friday 16 October 2026 (37683) Print this report

After recovery of the OMC PZT driver, OMC can be successfuly locked and initial alignment can be done (fig1)

Images attached to this comment
ISC (General)
takaaki.yokozawa - 14:48 Wednesday 14 October 2026 (37667) Print this report
Trial of the PRMI lock
[Hirose, Yokozawa]

After the recovery of the GRY, we performed the initial alignment again for Xarm and Yarm.
Next, we tired to lock the PRMI by tweaking the PRM.

PRMI actually can be locked, but the POP 90 I value was about 0.4 and MICH control seemed very loose.

1. Compared with previous Initial alignment PRMI
Previous one was
GPS 1471274941
2026/08/20 15:28;43 UTC

- IMC output was almost same, 0.94 -> 0.99
- Refl DC PD1 value larger 10 -> 14, we need to turn the IFO_HWP more, but when we rotated, PRMI locked loss, so we will tune the HWP after investigate the MICH LSC.
- POP DC PD1 value lower 0.01 -> 0.006
- POP 90 I offset value changed.
- Check the filter bank MICH1, MICH2, PRCL1, PRCL2, but I cannot find any difference

2. Measured the transfer function
Fig.1. and Fig.2. showed the MICH and PRCL OLTF, MICH 20 dB lower than previous, PRCL shape different about -5 dB.
We need to check why the MICH OLG so small.

3. Performed the Yuzurihara-san offset code

/opt/rtcds/userapps/release/asc/k1/scripts $ python3 subtract_dark_offset.py -p notQPD
K1:LSC-REFL_PDA1_RF45_Q_OFFSET => -2.8782957593599954
K1:LSC-REFL_PDA1_RF45_I_OFFSET => -0.7863214095433553
K1:LSC-REFL_PDA2_RF51_Q_OFFSET => -58.14948800404866
K1:LSC-REFL_PDA2_RF51_I_OFFSET => -94.92184766133626
K1:LSC-REFL_PDA2_RF135_I_OFFSET => 15.199504470825195
K1:LSC-REFL_PDA2_RF135_Q_OFFSET => 206.31389261881512
K1:LSC-AS_PDA1_RF17_Q_OFFSET => 1.4356917520364125
K1:LSC-AS_PDA1_RF17_I_OFFSET => 4.0745154341061935
K1:LSC-POP_PDA1_RF17_Q_OFFSET => -35.377245712280256
K1:LSC-POP_PDA1_RF17_I_OFFSET => -1.565380189816157
K1:LSC-POP_PDA1_RF45_Q_OFFSET => 2.929738660653432
K1:LSC-POP_PDA1_RF45_I_OFFSET => -1.1762522975603742
K1:LSC-POP_PDA2_RF90_Q_OFFSET => 317.74421335856124
K1:LSC-POP_PDA2_RF90_I_OFFSET => -315.9900405883789

raceback (most recent call last):
File "/opt/rtcds/userapps/trunk/asc/k1/scripts/subtract_dark_offset.py", line 171, in
zeroOffs(channels_omc, fout)
File "/opt/rtcds/userapps/trunk/asc/k1/scripts/subtract_dark_offset.py", line 48, in zeroOffs
d = z.avg(t_ave, list_of_chans)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/cdsutils/avg.py", line 69, in avg
for buf in conn.iterate(*args):
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/cdsutils/nds.py", line 104, in iterate
return super(connection, self).iterate(*nargs, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/nds2.py", line 1340, in iterate

So (maybe) only 14 PD offset can be changed.

But still we couldn't find the critical reason
- why the POP 90 I during PRMI lock lower (1.0 -> 0.4)
- why the MICH OLTF so small (-20 dB)

We also tried to lock the SRY and SRMI.
SRY locked without any problem, SRMI also.
We measured the OLTF for SRMI (MICH Fig.3. and SRCL Fig.4. )

Images attached to this report
Comments to this report:
takahiro.yamamoto - 18:35 Wednesday 14 October 2026 (37669) Print this report
Since the error message is missing from the traceback (only the stack trace is attached), this is merely a guess, but I suspect an NDS 'overloaded' error occurred.

I have heard that this script has been successfully tested in the past, so it should run correctly when the NDS server is under low load. But, NDS overload can occur depending on the situation, such as when other users are applying high loads to the NDS or when many test points remain un-released after use.

In such cases, waiting and re-executing the script, or releasing unnecessary test points, should resolve the issue.
ISC (General)
Hiroki Fujimoto - 12:34 Wednesday 14 October 2026 (37666) Print this report
Comment to Lock recovery for XARM and YARM (37659)

[Hirose, Yokozawa, Fujimoto]

Abstract

We investigated the GRY locking issue observed yesterday and found that both the phase modulation and demodulation LO outputs for Gr PDHY were turned off.
After turning on both LO outputs, we successfully recovered the PDH error signal and locked GRY.
We also found that the OLTF gain was more than 10 dB lower than previously measured due to an incorrect LO phase.
By optimizing the LO phase, we almos recovered the OLTF gain and achieved a UGF of approximately 5 kHz.

Details

Since we had confirmed this morning that the GRY error signal was missing, we investigated the analog electronics in the mine and resolved the issue as described below.

Turning on the LO outputs

We found that both the phase modulation and demodulation LO outputs for Gr PDHY were turned off (Figs. 1 and 2).
After turning on both outputs, we successfully recovered the Gr PDHY error signal and locked GRY using this signal.

LO phase adjustment

We first set the LO phase to −135 deg, which was the value recorded just before the planned power outage in March 2026 (Notion page).
However, the measured GRY OLTF gain was approximately 10 dB lower than that measured in September 2025 (klog 35124).

We therefore optimized the LO phase and found that −70 deg gave the best result.
As shown in Fig. 3, after performing ADS, the OLTF gain almost recovered to within approximately 1 dB of the previous measurement, with a UGF of approximately 5 kHz.

Images attached to this comment
CRY (Cryostat EX)
nobuhiro.kimura - 9:14 Wednesday 14 October 2026 (37663) Print this report
Comment to Opened a side flange of EXC (37587)

{Kimura}

 I am attaching a trend graph with the upper limit of the left vertical axis corrected to 1×10⁻⁴ Pa.
The partial pressure of H₂O shows a downward trend.

Images attached to this comment
DetChar (General)
hirotaka.yuzurihara - 8:42 Wednesday 14 October 2026 (37661) Print this report
Comment to DetChar cluster: computing environment, automatic segment production (37374)

I tested the automatic Segment production and GauCh analysis as part of the validation of the KAGRA DetChar tools with the latest conda environment.
Overall, both jobs worked well under HTCondor.

The Segment job took 15.5 s on average and up to 25 s to treat 15 minutes data. The memory usage was about 200 MB.

The GauCh job took 116 s on average and up to 136 s to treat one hour data. Its memory usage was about 0.8 GB on average and up to about 1.0 GB.
However, the current test data were taken while the interferometer was not locked, so these resource requirements may be underestimated.
I plan to check the memory usage again after the interferometer is locked and update the requested resources in the HTCondor submit files if necessary.

ISC (General)
takaaki.yokozawa - 6:35 Wednesday 14 October 2026 (37660) Print this report
Comment to Lock recovery for XARM and YARM (37659)
I changed the target IFO_REFL from 125 to 140 for PREP_FOR_YARM_ALIGN in initial alignment guardian.
Same situation happened in this morning, GRY cannot be locked, even
K1:ALS-Y_PDH_COMCOMP
K1:ALS-Y_PDH_SLOWBOOST
were turned on (In case, GRX can be locked), so some trouble in PDH Y circuit?

I performed the initial alignment only for the IRY (ITMY and ETMY and BS), after then, manual alignment for SR3 to be large GRY flash.
ISC (IMC)
kentaro.komori - 0:25 Wednesday 14 October 2026 (37657) Print this report
Measurement of IMC length and length tuning plan

[Fujimoto, Komori]

Abstract:

We measured the IMC FSR to be 5.6243653(1) MHz, corresponding to an IMC round-trip length of 53.302451(1) m.
To reach the target RF sideband frequency, we will move the MCE by 10.26 mm toward the MCI/MCO.

Details:

We tuned the frequency of the seed RF sideband used for the IFO LSC so as to minimize the peak produced by laser-frequency excitation, using the same method as described in klog:23115.
The optimal frequency was found to be 5.6243653(1) MHz, corresponding to an IMC round-trip length of 53.302451(1) m.
This value differs by 13 µm from the previous measurement performed in 2024 (klog:29385).

The target sideband frequency is 5.6265328 MHz.
Therefore, the IMC round-trip length should be shortened by 20.53 mm.
Since the MCE displacement changes the round-trip length by twice the mirror displacement, we will move the MCE by 10.26 mm toward the MCI/MCO.

ISC (General)
Hiroki Fujimoto - 23:05 Tuesday 13 October 2026 (37659) Print this report
Lock recovery for XARM and YARM

[Yokozawa, Ushiba, Fujimoto]

Abstract

We worked on lock recovery and initial alignment for XARM and YARM.
For XARM, we completed the initial alignment, including ADS, after recovering the error signal (klog 37656).
For YARM, I recovered the IR and GR resonances and successfully locked IRY. However, GRY was locked at a point away from resonance, and I could not lock it to the TEM00 mode.

Details

XARM
As described in klog 37656, we successfully recovered the IRX error signal by correcting the LO settings.
Thanks to the XARM alignment performed by Yokozawa-san in the morning, we were able to lock XARM with only minor alignment adjustments and complete the initial alignment procedure, including ADS.
However, as pointed out in klog 37656, some issues still need to be investigated, such as the change in the OLTF gain.

YARM
When I started the initial alignment of YARM, no flashes were observed for either IR or GR.
By adjusting the alignment of SR3, BS, IY, and EY while monitoring the camera images and PD signals, I improved the transmission to approximately 0.8 for both IR and GR and successfully locked IRY.
Fig. 1 shows a screenshot of the setup at that time.

However, when I attempted to lock GRY, it locked at a point away from resonance, as shown in Fig. 2.
As a result, the lock check repeatedly failed, causing the system to attempt to relock GRY.

If anyone has any ideas about what might be causing this issue, I would appreciate your comments at the next morning briefing.

Images attached to this report
Comments to this report:
takaaki.yokozawa - 6:35 Wednesday 14 October 2026 (37660) Print this report
I changed the target IFO_REFL from 125 to 140 for PREP_FOR_YARM_ALIGN in initial alignment guardian.
Same situation happened in this morning, GRY cannot be locked, even
K1:ALS-Y_PDH_COMCOMP
K1:ALS-Y_PDH_SLOWBOOST
were turned on (In case, GRX can be locked), so some trouble in PDH Y circuit?

I performed the initial alignment only for the IRY (ITMY and ETMY and BS), after then, manual alignment for SR3 to be large GRY flash.
Hiroki Fujimoto - 12:34 Wednesday 14 October 2026 (37666) Print this report

[Hirose, Yokozawa, Fujimoto]

Abstract

We investigated the GRY locking issue observed yesterday and found that both the phase modulation and demodulation LO outputs for Gr PDHY were turned off.
After turning on both LO outputs, we successfully recovered the PDH error signal and locked GRY.
We also found that the OLTF gain was more than 10 dB lower than previously measured due to an incorrect LO phase.
By optimizing the LO phase, we almos recovered the OLTF gain and achieved a UGF of approximately 5 kHz.

Details

Since we had confirmed this morning that the GRY error signal was missing, we investigated the analog electronics in the mine and resolved the issue as described below.

Turning on the LO outputs

We found that both the phase modulation and demodulation LO outputs for Gr PDHY were turned off (Figs. 1 and 2).
After turning on both outputs, we successfully recovered the Gr PDHY error signal and locked GRY using this signal.

LO phase adjustment

We first set the LO phase to −135 deg, which was the value recorded just before the planned power outage in March 2026 (Notion page).
However, the measured GRY OLTF gain was approximately 10 dB lower than that measured in September 2025 (klog 35124).

We therefore optimized the LO phase and found that −70 deg gave the best result.
As shown in Fig. 3, after performing ADS, the OLTF gain almost recovered to within approximately 1 dB of the previous measurement, with a UGF of approximately 5 kHz.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 21:36 Tuesday 13 October 2026 (37658) Print this report
trend frame rotation
Old trend frames were removed on the storage for k1fw0.
Removed time segment is [1455000000, 1460000000) for second and minute trend.

These data is available on Kashiwa.
There was no undelivered data to Kashiwa in that time segment.
Search Help
×

Warning

×