Reports of 34389
MIF (General)
dan.chen - 7:48 Thursday 11 June 2026 (37059) Print this report
Initial alignment 260611

With Yokozawa-san

We performed the initial alignment for Xarm, Yarm, OMC and PRMI.

MIF (General)
shun.saito - 21:37 Wednesday 10 June 2026 (37058) Print this report
Alignment of the sub-laser beam incident on the SRC

[Smith, Hirose, Saito]

The optic that was identified as a BS in the previous experiment (klog:37052) was replaced with a mirror. In addition, while attempting to correct beam clipping on the edge of a mirror, it was found that the beam was not passing through the center of the 150 mm focal-length lens. Since the beam was laterally displaced, an attempt was made to move the lens sideways. However, due to the mounting configuration, the lens could not be translated laterally. Modifying the mount to allow lateral adjustment would likely cause interference with a nearby mirror and shift the lens from its original position. Therefore, it will be necessary to move the mirror instead. Furthermore, because two lenses were removed during the alignment procedure, mode matching must be redone. In addition, the short distance between the 150 mm focal-length lens and the nearby mirror, as well as the difficulty of adjusting the mirror near the lens, have led us to consider redesigning the optical layout.
 

  • First, the optic at Spot 1 in the photograph, which had been identified as a BS in the previous experiment (klog:37052), was replaced with a mirror. (Please note that although a mount labeled "NON POL 50:50" was used, the optic itself is a mirror (HYD-10).) The alignment of the main laser was then readjusted, and the alignment of the sub-laser was performed using two irises.
     
  • However, when the sub-laser power was measured at Spot 2 in the photograph, it was found to be approximately 830 mW. Therefore, Spot 3 was inspected, and it was discovered that the beam was clipping on the edge of a mirror. The alignment was then adjusted so that the main laser beam was centered on the mirror. However, under these conditions, when the beam was adjusted to pass through the center of the 200 mm focal-length lens, it clipped on the side edge of the mirror at Spot 4. To correct this, the alignment was adjusted using mirrors located upstream of the two lenses so that the beam would pass through the centers of both the lenses and the mirrors. However, this was not successful. It was suspected that the presence of the lenses was making the alignment process difficult, so the two lenses were temporarily removed. With the lenses removed, the beam was aligned to pass through the centers of the mirrors, and the 150 mm focal-length lens was then reinstalled. However, the beam became laterally displaced. An attempt was made to adjust the lateral position of the lens, but this was not possible because of the way the lens was mounted. Furthermore, modifying the mount to allow lateral adjustment appeared impractical because the lens was located very close to a mirror, making it difficult to reinstall the lens in its original position.
     
  • Therefore, it will be necessary to move the mirror located before the lens. In addition, because the two lenses were removed, mode matching must be performed again. Considering this, together with the short distance between the 150 mm focal-length lens and the nearby mirror and the difficulty of adjusting the mirror in that region, we are considering redesigning the optical layout.
Images attached to this report
MIF (General)
kenta.tanaka - 17:57 Wednesday 10 June 2026 (37057) Print this report
Monitor PD Preparation for Aux. laser alignment check to SRC

To align the Aux. beam axis with SRC axis more precisely, we would like to use the flash transmitted from SRC. We estimated the flash power on AS PD when 1W Aux. input power was injected from the SR2 AR side. The power just after trasmitting SRM seems to be ~65 uW and this beam is transmitted to AS port via OSTM (T = 3%). Then, the estimated power on AS DC PD is ~2 uW. Therefore, it maybe too low to obtain the flash with AS PD.

So we put new DC PD (Thorlabs, PDA100A2) in OMC REFL path for monitoring the flash instead of AS PD. The channel for OMC REFL DC is already existed (maybe it was used previously but now it is not used.). So I connected the new DC PD to the channel (K1:OMC-REFL_DC). I confirmed the PD response with DGS.

However, the alignment work on POS table seems not to be completed (Maybe Saito-kun reported detail later). So I put the beam dumper in front of the PD and blocked the beam by the dumper for now. 

IOO (OMC)
takafumi.ushiba - 16:26 Wednesday 10 June 2026 (37056) Print this report
Comment to OMC DC PD health check: dark noise and single bounce (37055)

Some notes on the measurement setup:

1. For the single-bounce configuration, the following suspension states were requested:
PRM: MISALIGNED_BF
ITMX: MISALIGNED_BF
ETMY: MISALIGNED
SRM: MISALIGNED
All others: LOCK_ACQUISITION

2. In the case of locking with 7.8 mW and 16.2 mW on DC PD B, OMMT2 and OSTM were actively controlled to optimize their alignment using the in-vacuum OMC QPDs, whereas no alignment control was applied during locking with 1.6 mW.
This is because the alignment control using the in-vacuum OMC QPDs did not work well due to the very low power on the OMC QPDs; however, this is expected to have little impact on the results.

IOO (OMC)
Joshua Smith - 15:28 Wednesday 10 June 2026 (37055) Print this report
OMC DC PD health check: dark noise and single bounce
[Ushiba, Smith]

We did a (weak) health check of the OMC DC PD B and saw no signs of excess noise in the dark state or in the single bounce configuration.

In klog 36277, excess noise was seen on DC PD B following a lock loss on February 3, 2026. In klog 36569, later in March 2026, DC PD B showed no excess dark noise. So did DC PD B have some intermittent noise that went away? Or could it have some damage that only makes excess noise when there is a DC power? We tried to test this by looking again at the dark noise and comparing with the noise in a single bounce configuration (IMC locked, ITMX misaligned).

Dark noise:
9/6/2026 05:38:30 UTC dark noise: shutter closed, 1 stage whitening transimpedence 400 ohm (to match settings in klog 36569)
The DC PD dark noise agrees with previous measurements made in klog36569. No excess noise in DC PD B.

Single bounce:
OMC locked with single bounce configuration, OMC DCPD settings the same as above.
9/6/2026 05:47:40 UTC Single bounce with 7.8mW on DCPD B.
The noise here of 1.4e-7 mW/rt(Hz) is higher than shot noise (7.8mW should give a shot noise of 5.4e-8 mW/rt(Hz)).

To double check that this is not shot noise, we increased power by a factor of 2 and look at how the noise scales.
9/6/2026 05:56:20 UTC Single bounce with 16.2mW of power on DCPD B.

The noise scales close to linearly. Turning the power up a factor of (both in mW): 16.2/7.8 = 2.08 the high frequency noise went up a factor (both in e-7 mW/rt(Hz)) 2.8/1.4 = 2. So there is some noise on the light hitting the DC PDs that’s scaling close to linearly with power. We’re not sure what the source of that noise is.

So we try to reduce the linear noise by reducing the power on the DC PDs. Locked OMC with IMC output of 0.9W.
10/6/2026 00:21:45 UTC Single bounce with 1.6mW on DC PD B.

Using the photodiode powers for DC PD B, we can make some estimates for the various noise components, comparing the 7.8mW and the 1.65mW single bounce cases.

The power (mW) reduced by factor 7.8/1.65 = 4.7
The unknown linear noise should now be at the level 1.4e-7/4.7=2.98e-8 mW/rt(Hz)
The shot noise for 1.65mW should be 2.48e-8 mW/rt(Hz)
The dark noise was measured to be 1.4e-8 mW/rt(Hz)
So for 1.65mW on DC PD B, the quadrature sum of dark+shot+linear = sqrt(2.48^2+2.98^2+1.4^2) = 4.122 e-8 mW/rt(Hz)
And we measure just a little higher, about 5e-8 mW/rt(Hz). Pretty close to shot+dark+linear noise.

From these tests, there is not any evidence of excess noise in OMC PD B. But the unknown linearly-scaling noise on the light in the single bounce configuration isn’t allowing us to make a shot-noise-limited test.
Images attached to this report
Comments to this report:
takafumi.ushiba - 16:26 Wednesday 10 June 2026 (37056) Print this report

Some notes on the measurement setup:

1. For the single-bounce configuration, the following suspension states were requested:
PRM: MISALIGNED_BF
ITMX: MISALIGNED_BF
ETMY: MISALIGNED
SRM: MISALIGNED
All others: LOCK_ACQUISITION

2. In the case of locking with 7.8 mW and 16.2 mW on DC PD B, OMMT2 and OSTM were actively controlled to optimize their alignment using the in-vacuum OMC QPDs, whereas no alignment control was applied during locking with 1.6 mW.
This is because the alignment control using the in-vacuum OMC QPDs did not work well due to the very low power on the OMC QPDs; however, this is expected to have little impact on the results.

MIF (General)
takaaki.yokozawa - 8:58 Wednesday 10 June 2026 (37053) Print this report
Initial alignment 260610
I performed the initial alignment for Xarm, Yarm, OMC, PRMI, and SRY.
CAL (XPcal)
dan.chen - 7:17 Wednesday 10 June 2026 (37051) Print this report
Comment to XPcal calibration (37050)

After the calibration work, we moved the RxPD back to its nominal position and found that its output had changed from the pre-work value. We investigated the cause and found that the alignment between the integrating sphere and the plate underneath it had slightly shifted. We realigned the integrating sphere with the plate, and the RxPD output returned almost to its original value.

MIF (General)
shun.saito - 21:26 Tuesday 09 June 2026 (37052) Print this report
Measurement of the PLL open-loop transfer function and alignment of the sub-laser beam incident on SRY

[Tanaka, Hirose, Saito]

A 10 dB attenuator was added, reducing the beat signal level from 23 dBm to 10 dBm. The open-loop transfer function of the PLL was then measured. The results suggest that the sub-laser PZT responds with a frequency change to the frequency-difference signal from the PFD, rather than responding with a frequency change to a phase-difference signal. In addition, the alignment of the sub-laser beam incident on SRY was performed using two irises. The sub-laser PZT was then driven, but no flashes were observed at the AS port. This is likely because one of the optics expected to be a mirror was actually a BS, the beam was clipping on the edge of a mirror, and the observation was being made at the AS port. In the next experiment, the BS will be replaced with a mirror, the alignment will be redone, and a PD will be installed at the OMC reflection port to observe the flashes.
 

  • First, a 10 dB attenuator was added to reduce the input power to the PFD. As a result, the beat signal level decreased from 23 dBm to 10 dBm. Next, the 1 MHz low-pass filter in the SR560 used for feedback to the sub-laser PZT was replaced with either a 100 kHz or a 10 kHz low-pass filter. Under these conditions, the approximately 260 kHz oscillation previously observed in the error signal (klog:37046) disappeared. The open-loop transfer function was then measured, revealing a flat region. This was unexpected. We had assumed that the feedback loop operated by changing the sub-laser frequency via the PZT to eliminate the phase difference, which should behave as an integrator. However, the observation is consistent with the PFD producing a frequency-difference signal and the sub-laser PZT responding with a frequency change. Therefore, a 10 kHz low-pass filter was applied in the SR560 feedback path to the sub-laser PZT, and the gain and integrator cutoff frequency in Moku:Lab were varied. The measured open-loop transfer function then closely matched the designed filter response (Photo 1).
     
  • Next, the mirrors were adjusted so that the main laser beam followed the optical path intended for the sub-laser beam entering the interferometer. Two irises were then installed along this path and aligned to the main laser beam. The sub-laser alignment was subsequently adjusted so that it also passed through the two irises. The main laser was then blocked, leaving only the sub-laser beam incident on SRY. The sub-laser PZT was driven with a triangular waveform generated by the Moku:Lab function generator, and the AS port was monitored for flashes. However, no flashes were observed. This is likely because the optical power incident on SRY was too low. The laser powers measured at Spots 1~5 in Photo 2 were as follows:

    Spot 1: approximately 130 mW
    Spot 2: approximately 390 mW
    Spot 3: approximately 780 mW
    Spot 4: approximately 1.0 W
    Spot 5: approximately 1.1 W

    From these measurements, the laser power incident on SRY is estimated to be approximately 130 mW, which corresponds to only about 0.25 μW at the AS port. Such a small signal is likely buried in noise. The reduction in laser power between Spot 2 and Spot 1 occurred because the optic between them was a BS rather than a mirror. In addition, the reduction in power between Spot 4 and Spot 3 may be due to the beam clipping on the edge of the mirror.
     

  • Therefore, in the next experiment, the BS between Spot 2 and Spot 1 will be replaced with a mirror, and the alignment will be adjusted so that the beam does not clip on the edge of the mirror between Spot 4 and Spot 3. However, even after these modifications, the power at the AS port is expected to increase only to approximately 0.97 μW. Therefore, a PD will be installed at the OMC reflection port, and flashes will be monitored there instead.

Images attached to this report
CAL (XPcal)
Misato Onishi - 14:21 Tuesday 09 June 2026 (37050) Print this report
XPcal calibration

KAGRA Pcal-X updates (2026/06/09)

Workers: Dan Chen, Jiahui Xiong, Misato Onishi

We performed monthly Pcal-X calibration on 2026/06/09.

After the calibration, we updated EPICS parameters related to the Pcal-X system. No issues were found.

EPICS Key Before After Δ (After − Before)
K1:CAL-PCAL_EX_1_OE_R_SET 0.98353 0.98379 0.00027
K1:CAL-PCAL_EX_1_OE_T_SET 0.98353 0.98379 0.00027
K1:CAL-PCAL_EX_1_PD_BG_RX_V_SET -0.00390 -0.00384 0.00006
K1:CAL-PCAL_EX_1_PD_BG_TX_V_SET 0.00483 0.00477 -0.00006
K1:CAL-PCAL_EX_1_RX_V_R_SET 0.50217 0.50205 -0.00012
K1:CAL-PCAL_EX_2_INJ_V_GAIN 0.95152 0.95265 0.00113
K1:CAL-PCAL_EX_2_OE_R_SET 0.97404 0.97473 0.00069
K1:CAL-PCAL_EX_2_OE_T_SET 0.97404 0.97473 0.00069
K1:CAL-PCAL_EX_2_PD_BG_TX_V_SET 0.00389 0.00389 0.00000
K1:CAL-PCAL_EX_2_RX_V_R_SET 0.49783 0.49795 0.00012
K1:CAL-PCAL_EX_WSK_PER_RX_SET 1.49025 1.49085 0.00060
K1:CAL-PCAL_EX_WSK_PER_TX1_SET 0.52750 0.52749 -0.00001
K1:CAL-PCAL_EX_WSK_PER_TX2_SET 0.38816 0.38837 0.00021

 

Images attached to this report
Comments to this report:
dan.chen - 7:17 Wednesday 10 June 2026 (37051) Print this report

After the calibration work, we moved the RxPD back to its nominal position and found that its output had changed from the pre-work value. We investigated the cause and found that the alignment between the integrating sphere and the plate underneath it had slightly shifted. We realigned the integrating sphere with the plate, and the RxPD output returned almost to its original value.

MIF (General)
takaaki.yokozawa - 8:38 Tuesday 09 June 2026 (37049) Print this report
Initial alignment 260609
I performed the initial alignment Xarm Yarm and PRMI
CAL (Pcal general)
dan.chen - 6:00 Tuesday 09 June 2026 (37048) Print this report
Pcal Parameter Update Report

A CAL Tcam session was performed to obtain beam position information necessary for Pcal. The parameters have already been updated, and SDF has been accepted.

Operator: Dan Chen

Update Time: 2026/06/09 05:54:18

EPICS Key Before [mm] After [mm] Δ (After - Before) [mm]
K1:CAL-PCAL_EX_TCAM_PATH1_X -0.87474 mm -2.41683 mm -1.54209 mm
K1:CAL-PCAL_EX_TCAM_PATH1_Y 66.37439 mm 65.57365 mm -0.80074 mm
K1:CAL-PCAL_EX_TCAM_PATH2_X -0.37755 mm 1.41852 mm +1.79607 mm
K1:CAL-PCAL_EX_TCAM_PATH2_Y -67.02710 mm -66.64088 mm +0.38622 mm

Update Time: 2026/06/09 05:54:58

EPICS Key Before [mm] After [mm] Δ (After - Before) [mm]
K1:CAL-PCAL_EY_TCAM_PATH1_X 0.76950 mm -0.69068 mm -1.46018 mm
K1:CAL-PCAL_EY_TCAM_PATH1_Y 65.80570 mm 62.58426 mm -3.22144 mm
K1:CAL-PCAL_EY_TCAM_PATH2_X 1.39102 mm 0.14883 mm -1.24219 mm
K1:CAL-PCAL_EY_TCAM_PATH2_Y -69.21742 mm -69.03655 mm +0.18087 mm

 

DGS (General)
takahiro.yamamoto - 21:45 Monday 08 June 2026 (37047) Print this report
Deployment of V2 IO-chassis and the front-end computer for EY1
[Ikeda, Nakagaki, YamaT]

Similar work: klog#36572 (IX1), klog#36625 (IY1), klog#36654 (EX0), klog#36692 (EY0), klog#36909 (EX1)
Preparation for this work: klog#36986

IO chassis for K1EX1 was replaced from V1 (S1706995) to V2 (S2416122) chassis.
All PCIe boards were just moved from V1 to V2 chassis with keeping their card numbers on the real time models.
There was no PCIe problem on this work.
Because IRIG-B issue was occurred, IRIG-B card was also replaced as one without any issue on the test bench.
After replacement work, We confirmed VIS_ETMY can reach ALIGNED and MISALIGNED states.

ADC/DAC noise measurement will be done in the next week.
MIF (General)
shun.saito - 21:25 Monday 08 June 2026 (37046) Print this report
PLL using a PFD

[Tanaka, Hirose, Saito]

Using the 20 dB RF amplifier and the 40 dB RF amplifier, the beat signal amplitude was increased to 23 dBm. After replacing the phase detector with a Phase Frequency Discriminator (PFD), it was confirmed that the beat signal frequency followed changes in the LO frequency. However, the error signal appeared to oscillate at approximately 260 kHz. This oscillation may be caused by a resonance of the sub-laser PZT.
 

  • First, the alignment was adjusted to maximize the beat signal. The signal level under various RF amplifier configurations was as follows:

    No RF amplifier: -51 dBm
    40 dB RF amplifier only: -5 dBm
    20 dB RF amplifier only: -20 dBm
    40 dB RF amplifier followed by the 20 dB RF amplifier: 8 dBm
    20 dB RF amplifier followed by the 40 dB RF amplifier: 23 dBm
     

  • Therefore, lock acquisition was attempted using the phase detector with the 20 dB RF amplifier followed by the 40 dB RF amplifier. A 1 MHz low-pass filter was applied in the SR560 used for feedback to the sub-laser PZT, while a flat filter was implemented in Moku:Lab. Various gains and integrator settings were tested. However, no behavior indicating that the beat frequency was being pulled toward the LO frequency was observed.
     

  • Next, the phase detector was replaced with a PFD. With a filter consisting of an overall gain of -6 dB and an integrator providing 6 dB of gain at 1 Hz (Photo 1), it was observed that the beat signal frequency followed changes in the LO frequency. In the lower plot of Photo 1, the red trace represents the error signal and the blue trace represents the feedback signal. Since the feedback signal changed when the LO frequency was varied, the LO frequency and beat signal frequency were measured for feedback signal levels of approximately 0 V and ±1 V. The beat signal spectrum exhibited a shape with a dip at the center and peaks on both sides (Photo 2). Therefore, the frequencies of the two peaks were measured, and their average was taken as the beat signal frequency. In Photo 2, the light red trace corresponds to a feedback signal of approximately +1 V, while the red trace corresponds to a feedback signal of approximately -1 V.

    The results are summarized below:

    Feedback Signal           LO Frequency    Beat Signal Frequency
    Approximately -1 V      85.066 MHz         85.16 MHz
    Approximately  0 V      88.066 MHz         87.99 MHz
    Approximately +1 V    89.666 MHz         89.74 MHz
     

  • In addition, when using a flat filter and gradually increasing the gain, the error signal began oscillating at approximately 260 kHz, and the width of the beat signal increased. This oscillation may have been caused by a resonance of the sub-laser PZT. The corresponding error signals and beat signals are shown below:

    Flat filter with a gain of -6 dB (Photo 3), corresponding beat signal (Photo 4)
    Flat filter with a gain of 0 dB (Photo 5), corresponding beat signal (Photo 6)
    Flat filter with a gain of +6 dB (Photo 7), corresponding beat signal (Photo 8)

Images attached to this report
DGS (General)
takahiro.yamamoto - 20:00 Monday 08 June 2026 (37045) Print this report
Minute trend rotation
Old minute frames were removed on the storage for k1fw0.
Removed time segment is [1350000000, 1400000000)

These data is available on Kashiwa.
There was no undelivered data to Kashiwa in that time segment.
DGS (General)
takahiro.yamamoto - 19:47 Monday 08 June 2026 (37044) Print this report
Comment to Applying a new live patch for Debian workstations (36973)
Vendor's patch was applied for the Debian13 system.
Debian12 system is still running with the temporal mitigation measure for this issue.
DGS (General)
takahiro.yamamoto - 19:44 Monday 08 June 2026 (37043) Print this report
Comment to Live patching for a new vulnerability (36878)
Vendor's patch was released and applied.
After then, the temporal mitigation measure was removed.

As the result, a remediation for these two issues was completed.
CAL (Pcal general)
Misato Onishi - 14:17 Monday 08 June 2026 (37042) Print this report
WSK calibration at UToyama

Date: 2026/06/08

Member: Dan Chen, Misato Onishi, Seiya Matsuo

We performed our usual WSK calibration at UToyama.

The results look no problem.

Results

Case Alpha (Main Value) Alpha (Uncertainty)
Front WSK, Back GSK -0.911724 0.000357
Front GSK, Back WSK -0.909858 0.000275

Comparison with Previous Results

Comparing with previous results, no significant issues were found.
Attached graph is the result summary including the latest measured data.

Images attached to this report
VIS (IX)
takaaki.yokozawa - 11:19 Monday 08 June 2026 (37041) Print this report
Recovered the ITMX from TRIPPED state
After the large earthquake in Philippines, I fixed the tripped state ITMX.
Images attached to this report
VIS (IY)
ryutaro.takahashi - 9:41 Monday 08 June 2026 (37040) Print this report
Comment to Offload of GAS filters (36614)

I offloaded the BF GAS with the FR.

MIF (General)
takaaki.yokozawa - 8:10 Monday 08 June 2026 (37039) Print this report
TCam photo session 260608
After the initial alignment Xarm and Yarm, I performed the TCam photo session.
MIF (General)
shun.saito - 13:44 Saturday 06 June 2026 (37038) Print this report
Replacement of the mixer used for PLL

[Tanaka, Fujimoto, Saito]

The alignment was adjusted to maximize the beat signal, resulting in a beat signal level of approximately -55 dBm, which was the same as in the previous measurement (klog:37031). It was also confirmed that the sub-laser PZT was operating properly. The mixer currently in use (ZX05-1-S+) was then replaced with a phase detector (ZRPD-1+) purchased by Dan-san, and lock acquisition was attempted. However, no lock was achieved. Furthermore, when an RF amplifier was inserted after the high-pass filter while using the phase detector, the signal was amplified without waveform distortion, unlike the behavior observed in the previous experiment (klog:37031).
 

  • First, the alignment was adjusted to maximize the beat signal. The resulting beat signal level was approximately -55 dBm. Next, a signal from the Moku:Lab function generator was applied directly to the sub-laser PZT, and the corresponding movement of the beat signal was confirmed. Therefore, the PZT was verified to be functioning properly.
     
  • Next, the 1.9 MHz low-pass filter located between the mixer and the SR560 was moved from immediately before the SR560 to immediately after the mixer. PLL lock acquisition was then attempted using Moku:Lab with a 10 kHz low-pass filter while varying the gain and adding an integrator. However, no behavior indicating that the beat frequency was being pulled toward the LO frequency was observed. Lock acquisition was also attempted without using Moku:Lab by varying the gain of the SR560 low-pass filter, but no lock was achieved. In addition, a 10 kHz low-pass filter was applied to the SR560 used in the feedback path to the sub-laser PZT, while a flat filter was implemented in Moku:Lab. However, lock acquisition was still unsuccessful. The mixer currently in use (ZX05-1-S+) was then replaced with the phase detector (ZRPD-1+) purchased by Dan-san. Various Moku:Lab filter configurations were tested in the same manner as before, but lock acquisition was again unsuccessful.

  • Next, while continuing to use the phase detector, an RF amplifier was inserted after the high-pass filter. Unlike the result obtained in the previous experiment (klog:37031), the signal amplitude increased while maintaining a clean waveform (Photo 1). The error signal also increased in amplitude and became saturated. Therefore, the gain of the SR560 was reduced from 200 to 5. Under these conditions, the error signal amplitude was approximately 384 mVpp (Photo 2).

Images attached to this report
VIS (SRM)
satoru.takano - 15:23 Friday 05 June 2026 (37037) Print this report
SRM oplev diagonalisation

[Fujimoto, Tanaka, Takano]

Summary

We diagonalised the SRM oplev. Now, the coupling from other DoFs is below 1% at the resonance frequencies.

Detail

We noticed that when we shake SRM TM in Pitch we observed motion in Yaw as well. At first, we suspected the actuator couplings, but the health check results obviously told us the coupling of the sensor (the tilt oplev), see Fig. 1 (Pitch) and Fig. 2 (Yaw) (blue: measurement in 2022, green: before the diagonalisation, red: after the diagonalisation). The 2x2 matrix about the coupling between pitch and yaw is as follows:

OUT \ IN Pitch Yaw
Pitch 1 0.19
Yaw -0.32 1

After normalisation:

OUT \ IN Pitch Yaw
Pitch 0.952 0.187
Yaw -0.305 0.982

Using this matrix, we calculated its inverse and multiplied it by the current SENSALIGN matrix from the left. The health check results using the new SENSALIGN matrix are shown in the figure: in both Pitch and Yaw, the coupling is below 1% at the resonance peak frequencies. 

Images attached to this report
MIF (ITF Control)
satoru.takano - 15:04 Friday 05 June 2026 (37036) Print this report
DRMI locking trial with POP17 signals

[Fujimoto, Tanaka, Takano]

Summary

We continued the DRMI optimisation. We could stably lock DRMI with POP17Q for MICH, instead of REFL51Q. REFL51 signals looked strange, probably due to a bad demodulation phase. ADS implementation was tried, but not succeeded yet.

Detail

We continued the DRMI locking trial. This time, we investigated the REFL51 signals and discussed whether they could be used for locking. As reported here, there is an offset on both REFL51I and REFL51Q, but we don't understand its mechanism. In addition, the locking with REFL51Q for MICH looked unstable, so we decided to change the MICH control signal from REFL51Q to POP17Q for better stability. With POP17Q,  stability seemed to be improved so much. The lock can now be kept for more than 10 minutes.

The measured open loop transfer function for each loop are shown in Fig. 1 - 3. They looked stable enough, but sometimes we observed that MICH control got unstable and started oscillation at apparently a random frequency in 20 - 40 Hz. It may be that because of the alignment, MICH sensing gain increased, and the phase margin got smaller, or another control loop sucked the phase margin in the MICH loop via unknown couplings. Anyway, MICH control seems the key to better stability of DRMI control.

Once DRMI got stable, we injected the dithering signal in SRM and tried the phasing of SRM ADS with AS34I signal. The phase of the transfer function from the dithering LO to the signal (AS34I) is shown in Fig. 4. The measured phase was put in ADS, and tried to engage the control for SRM. It was not obvious how it worked, because the buidup level of AS34I looked almost the same due to its large fluctuation. Then, ADS of other mirrors, PRM, BS and IMMT2 were engaged using POP90I signal, but it seemed that the feedback signal made the alignment worse. We should tune the phases of the other mirrors as well for full ADS in DRMI.

With DRMI locked with POP17I&Q and REFL135I, the REFL51 signals were quickly examined. Obviously, both REFL51I and REFL51Q had a large offset. When the demodulation phase was rotated, the offset value also changed in sine curve for I phase and in cosine curve for Q phase (Fig.5). We don't know the source of these offsets, probably either MICH or SRCL has this offset.

Now that we can lock DRMI without REFL51 signals, the investigation is easier than before. I hope these issues will be solved soon and DRMI will be locked using fully 3f signals.

Images attached to this report
VAC (Valves & Pumps)
takashi.uchiyama - 13:19 Friday 05 June 2026 (37035) Print this report
Comment to Water dropped near the Ion pump controller at IXC (37033)
2026/06/05

Hayakawa, Yamaguchi, mTakahashi, Yasui, Uchiyama

The Hayakawa team repaired the ceiling to stop the water.

Uchiyama looked for ion pump controllers that should be taken care of, and there are 4 units on the 1st floor of the center area.
Images attached to this comment
DetChar (General)
takaaki.yokozawa - 9:28 Friday 05 June 2026 (37032) Print this report
Lock loss study during the O4c (up to middle August. 2025)
[Tanaka, Ide, Hamayasu, Yanagi (Aogaku), Yokozawa]

We tried to perform to make the summary of the lock loss study during the O4c run, up to the middle of Aug. 2025.
Total number of lock loss was 215, we checked them and we succeeded to apply tags to all lock loss during O4c August.

You can find the previous studies : klog34736, klog34684, klog34685, klog34686, klog34687, klog34688.

From the previous studies, we focused to distinguish following groups.

0. Request
When the locked loss happened by the "request" (ex. maintenance, calibration, commissioning, trouble ) we checked this group.
We didn't care which control became unstable in case of this group, of course.

1. Earthquake
If the lock loss guardian tagged [EQ], we treat the lock loss caused by the large (including the low frequency ground motion) earthquake.
We didn't care which control became unstable in case of this group.

2. 1 Hz ground motion
It turned out the "nearby" earthquake which have the ground motion above 1 Hz.
We checked the BLRMS IXV Z 1HZ3 and 3HZ10, and if there are relatively larger ground motion in 10s, we defined the 1 Hz lock loss. (Threshold is about 0.1 in 1HZ3 BLRMS)
We didn't care which control became unstable in case of this group.

3. ETMY MN oplev glitch
As you know, the sudden jump detected in ETMY MN TILT oplev, we saw several glitches in ETMY suspension.
Some locked loss occurred by this glitch, by checking the control signals of ETMY suspensions, we tagged to this group.

4. IR trans and POP 90 I drop before the lock loss (tagged alignment)
By checking the IR trans power and POP 90 I power, we tagged to this group.
After the Yokozawa's investigation, the most case caused by the large motion of the 0.08 Hz in Type-A suspension.
As you know, there are 0.08 Hz resonant frequency in Type-A suspension, if this motion excess the control range of the ASC, we loose the good alignment,
IR trans and POP 90 I became lower and finally lock loss happened.
We can see 0.08 Hz oscillation in ASC error signals in case this locked loss happened.

5. Quick saturation OMC DCPD (tagged quick)
We defined the OMC DCPD suddenly saturated (order of a few miliseconds), we tagged to this group.
After the Yokozawa's investigation, we may distinguish two groups;
- Excitation of the violin mode
As shown in Fig.1. , the similar glitch happened 2 sec before, the resonant frequency was about 180 Hz.
So I guess some of quick saturation may be caused by the excitation of the violin mode resonant frequency.
ID 16, 34, 37, 112, 115, 144, 147 would be the candidate of the this group
- Unknown behavior
This is quite interesting behavior that when quick saturation happened(Fig.2.),
- the value of the OMMT2 TRANS DC decreased (60 -> 40 cnt)
- the value of the AS PDA1 DC decreased (0.17 -> 0.09 )
- the value of the AS PDA1 RF17 Q ERR decreased (0.014 -> -0.001) AS0CROSS???
- the value of the REFL PDA1 DC increased (4 -> 14)
I discussed with Ushiba-san, Tanaka-san, Takano-san and Fujimoto-san, but we cannot conclude it.
If you notice something, please contact to me.
ID 38, 114, 118, 185, 204 would be the candidate.

6. Slowly saturation OMC DCPD (tagged slow)
If the behavior of the 0. - 5. didn't detect and we can see the several oscillation detected in OMC DC PD and saturation detected here, we tagged to this group.
They would be come from the excitation of the resonant frequency of the cryo-payload (see detail in Ishikawa-san's master thesis JGWDoc17063)

Fig.3. showed the percentage of the lock loss during O4c up to the August.
Fig.4. showed the resonant frequency for the slowly saturation OMC DCPD, by our eye and ndscope cousors
We also generated several summary plots, they will appear soon.

We didn't care much for the EQ and 1Hz ground motion. This would be the next step.

Finally, I uploaded the txt file for lock loss tag.

Thank you very much for great work, Yuzurihara-san and many Aogaku members!
Images attached to this report
Non-image files attached to this report
Search Help
×

Warning

×