Reports of 34563
ISC (General)
dan.chen - 5:58 Friday 24 July 2026 (37252) Print this report
Initial alignment 260724

With Yokozawa-san

We performed the initial alignment Xarm, Yarm, OMC, and DRMI.

VIS (SRM)
dan.chen - 4:19 Friday 24 July 2026 (37251) Print this report
GAS is close to saturation (F0)

The SRM GRD says "GAS is close to saturation (F0)".

Images attached to this report
MIF (General)
shun.saito - 1:05 Friday 24 July 2026 (37250) Print this report
Comment to Measurement of the PRC/SRC length using the beat signal at OMC REFL (37178)

[Kawakami, Komori, Tanaka, Saito]

The SRY cavity was scanned by directly driving the sub-laser PZT while monitoring the beat signal in the OMC REFL. Using the Max Hold function of the spectrum analyzer, transmission power as a function of beat frequency was obtained around 1.6 GHz, 800 MHz, −800 MHz, and −1.6 GHz. The measurement data are stored in:

Dropbox → All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMC_REFL_beat_signal_PZT_sweep/2026_07_23_SRY

The data were fitted both with and without a linear background, and the maximum and minimum values within the fitting uncertainties were used to estimate the uncertainty. From these results, the SRY cavity length was determined by fitting. The measured length differs from the design value by 1.757(50) cm, which is consistent with the previous result of 1.58(82) cm reported in klog:37209.
 

  • First, a new spectrum analyzer was installed to monitor the beat signal at the OMC REFL. A PLL was established using the down-converted beat signal when the original beat frequency was approximately 450 MHz, and it was confirmed that the SRY cavity could be scanned by frequency-modulating the LO. Next, although the mixer used for down-conversion has a nominal upper frequency limit of 500 MHz, it was expected that PLL operation would still be possible at higher frequencies with only increased conversion loss. Therefore, the beat frequency was increased to approximately 800 MHz, and it was confirmed that the SRY cavity could again be scanned by frequency-modulating the LO while using the down-converted signal for the PLL.
     
  • Furthermore, since the PLL is not required for the OMC REFL beat-signal measurement itself, the PLL was turned off and the sub-laser PZT was driven directly to scan the SRY cavity. This worked successfully when the beat frequency was around 800 MHz. Therefore, the sub-laser PZT was driven directly, and the Max Hold function of the spectrum analyzer was used to obtain transmission-power data as a function of beat frequency around 1.6 GHz, 800 MHz, −800 MHz, and −1.6 GHz (Fig. 1). Here, the negative frequencies correspond to the case in which the sub-laser frequency is lower than the main laser frequency. In addition, while observing the maximum beat-signal level in the OMC REFL during the PZT sweep, the alignment was optimized using a single mirror. As a result, the peak shapes became noticeably cleaner. This suggests that the relatively large uncertainty of the SRY measurement in klog:37209 was likely caused by imperfect alignment. After acquiring the data around 1.6 GHz and 800 MHz, the temperature of the sub-laser was increased to reduce its frequency. The beat signal disappeared at approximately 29.8°C. According to klog:36777, the sub-laser undergoes a mode hop between 29.5°C and 30°C, so the disappearance of the beat signal is attributed to this mode hop. The temperature was then increased further, and at approximately 31.64°C, data around −800 MHz were acquired. Before and after this point, data around 1.6 GHz and −1.6 GHz were also obtained.
     
  • The peaks in the measured data were fitted with and without a linear background, following the same procedure as in klog:37209. The fitting results for the individual peaks are listed below. The measurement data are also stored in:

    Dropbox → All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMC_REFL_beat_signal_PZT_sweep/2026_07_23_SRY

    Fig. 2: Around 1.6 GHz, without a linear background. Using data from 1518.25 MHz to 1519.1 MHz, the fitted peak frequency is 1518.7773(42) MHz.
    Fig. 3: Around 1.6 GHz, with a linear background. Using data from 1518.25 MHz to 1519.1 MHz, the fitted peak frequency is 1518.725(13) MHz.
    Fig. 4: Around 800 MHz, without a linear background. Using data from 872 MHz to 873.6 MHz, the fitted peak frequency is 872.8561(45) MHz.
    Fig. 5: Around 800 MHz, with a linear background. Using data from 872 MHz to 873.6 MHz, the fitted peak frequency is 872.8274(81) MHz.
    Fig. 6: Around −800 MHz, without a linear background. Using data from 823.3 MHz to 824.25 MHz, the fitted peak frequency is 823.7654(15) MHz.
    Fig. 7: Around −800 MHz, with a linear background. Using data from 823.3 MHz to 824.25 MHz, the fitted peak frequency is 823.7819(48) MHz.
    Fig. 8: Around −1.6 GHz, without a linear background. Using data from 1555 MHz to 1556 MHz, the fitted peak frequency is 1555.3774(33) MHz.
    Fig. 9: Around −1.6 GHz, with a linear background. Using data from 1555 MHz to 1556 MHz, the fitted peak frequency is 1555.3867(99) MHz.
     

  • From the fitted peak frequencies and their uncertainties, the maximum and minimum frequencies within the uncertainty range were determined. The overall uncertainty range was taken as the union of the results obtained with and without a linear background. The following values were therefore used to determine the SRY cavity length:

    Minimum (MHz)    Maximum (MHz)
    1518.7120    1518.7815
    872.8193    872.8606
    −823.7866    −823.7639
    −1555.3967    −1555.3768

    The midpoint frequency between the minimum and maximum values was divided by the FSR calculated from the SRY design length of 64.9264 m. The resulting values were rounded to the nearest integers, and the measured frequencies were fitted with the function AN + B, where A and B are fitting parameters and N is an integer. The fitting results are shown in Fig. 10:

    A: 2.308085(18) MHz
    B: 0.2480(98) MHz

    Since A corresponds to the FSR, the SRY cavity length was calculated from this value:

    Fitted length: 64.94397(50) m
    Design value: 64.9264 m
    Difference (fitted − design): 1.757(50) cm

    This result is consistent with the previous result reported in klog:37209, which gave a difference from the design value of 1.58(82) cm.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 20:48 Thursday 23 July 2026 (37249) Print this report
Preparation of upgrading ca-gateway server
I prepared a new EPICS ca-gateway server (Debian 13) to replace the current ca-gateway server, which has become a legacy system.

Since the EPICS base and EPICS extensions for Debian 13 had been already built as described in klog#35372 and klog#37207, they will be used.
Details on server setup can be found in JGW-T2617453.

The major changes are the OS upgrade (Debian 8 → Debian 13) and the migration of managing ca-gateway process to systemd. This will automate process startup during server reboots and a recovery from some trouble, and ensure that process logs are properly managed. This server is currently in standby mode between the DGS network and the virtual network and is planned to be swapped with the current server on the next maintenance day.
ISC (General)
takafumi.ushiba - 19:26 Thursday 23 July 2026 (37248) Print this report
Calculation of PRC length, SRC length, and Schnupp asymmetry

Abstract:

Followings are the summary of PRC length, SRC length, and Schnupp asymmetry calculated from the PRX/PRY/SRX/SRY length measurements reported in klog37209 and klog37223.

LPRC=66.5984(28)L_\mathrm{PRC}=66.5984(28) m

LSRC=66.6120(47)L_\mathrm{SRC}=66.6120(47) m

LSchnupp=3.3405(48)L_\mathrm{Schnupp}=3.3405(48) m

Detail:

According to  klog37209 and klog37223, the cavity length of PRX/PRY and SRX/SRY can be summarized as follows:

Cavity mean value [m] error [m]
PRX 68.2688 ±0.0046
PRY 64.9280 ±0.0033
SRX 68.2818 ±0.0045
SRY 64.9422 ±0.0082

Based on these results, we can calculate the PRC/SRC length (average length of PRX/SRX and PRY/SRY) and Schnupp asymmetry.

PRC length:

PRC length can be obtained by averaging PRX and PRY length, so the PRC length can be calculated as follows:

LPRC=LPRX+LPRY2=68.2688+64.92802±0.00462+0.003322=66.5984(28)L_\mathrm{PRC}=\frac{L_\mathrm{PRX}+L_\mathrm{PRY}}{2} = \frac{68.2688+64.9280}{2}\pm\frac{\sqrt{0.0046^2+0.0033^2}}{2}=66.5984(28)

SRC length:

SRC length can be calculated as the similar way of PRC.

LSRC=LSRX+LSRY2=68.2818+64.94222±0.00452+0.008222=66.6120(47)L_\mathrm{SRC}=\frac{L_\mathrm{SRX}+L_\mathrm{SRY}}{2} = \frac{68.2818+64.9422}{2}\pm\frac{\sqrt{0.0045^2+0.0082^2}}{2}=66.6120(47)

Schnupp asymmetry:

Schnupp asymmetry can be calculated by subtracting PRY/SRY length from PRX/SRX length as follows.

LSchnuppfromPR=LPRX-LPRY=(68.2688-64.9280)±0.00462+0.00332=3.34080(566)L_\mathrm{Schnupp from PR}=L_\mathrm{PRX}-L_\mathrm{PRY} = (68.2688-64.9280)\pm\sqrt{0.0046^2+0.0033^2}=3.34080(566)
LSchnuppfromSR=LSRX-LSRY=(68.2818-64.9422)±0.00452+0.00822=3.33960(935)L_\mathrm{Schnupp from SR}=L_\mathrm{SRX}-L_\mathrm{SRY} = (68.2818-64.9422)\pm\sqrt{0.0045^2+0.0082^2}=3.33960(935)

Above 2 values are independent results, so we can calculate the weighted average of these values. So, the Schnupp asymmetry can be calculated as follows:

LSchnupp=3.3408/0.005662+3.3396/0.0093521/0.005662+1/0.009352±11/0.005662+1/0.009352=3.3405(48)L_\mathrm{Schnupp}=\frac{3.3408/0.00566^2+3.3396/0.00935^2}{1/0.00566^2+1/0.00935^2}\pm\frac{1}{\sqrt{1/0.00566^2+1/0.00935^2}}=3.3405(48)

ISC (General)
hirose.chiaki - 9:13 Thursday 23 July 2026 (37247) Print this report
Performed the initial alignment for PRMI and SRY

We performed the initial alignment for PRMI and SRY. 

ISC (ASC)
dan.chen - 8:11 Thursday 23 July 2026 (37245) Print this report
Initial Alignment and DRMI ADS Investigation

With Hirose-san and Yokozawa-san

Summary

The initial alignment through the OMC was completed successfully. During the subsequent DRMI ADS investigation, we found that the BS ADS loop was likely destabilizing the DRMI lock. Disabling the BS ADS improved the lock stability. Since the BS injection was more clearly observed in AS DC than in POP 90 and AS RF34, we started investigating AS DC as an alternative sensing signal and began transfer-function measurements for phasing.

Initial alignment

We performed the initial alignment through the OMC. The X arm, Y arm, and OMC alignment were completed without any significant issue. The OMC transmission was approximately 33.

DRMI ADS investigation

We then investigated the instability of the DRMI ADS during ALIGNING_DRMI. The DRMI lock appeared to be disturbed by the BS ADS loop. After disabling the BS ADS, the lock became significantly more stable, indicating that this loop was likely the main source of the instability.

With the BS ADS injection kept on, we checked several possible sensing signals. A small response was visible in AS RF34, while a much clearer response was observed in AS DC. Based on this result, we started investigating whether AS DC could be used as the sensing signal for the BS ADS loop.

We briefly closed the loop with a low gain, but the BS alignment continued to drift and the loop did not appear to control the alignment properly. We therefore started preparing a transfer-function measurement to determine the appropriate demodulation phase using AS DC.

Current status

  • Initial alignment through the OMC was completed successfully.
  • Disabling the BS ADS improved the DRMI lock stability.
  • AS DC showed the clearest response to the BS ADS injection.
  • Transfer-function measurements were started to investigate the BS ADS phasing.
ISC (General)
kenta.tanaka - 3:04 Thursday 23 July 2026 (37244) Print this report
First trial of PRC length estimation by TOF measurement

Ushiba, Komori, Tanaka (original idea by Fujimoto-kun?)

Ushiba-san modified the script of TOF measuremet for schnupp asymmentry in order to be able measure the PRC length. We ran the script and tried to measure the REFL PDA3 RF45 optimal demod. phases for Xarm and PRMI, respectively. This time, we locked PRMI with the 1f signal (VERTEX guardian state is PRMI_1F_LOCKED). The basic procedure is the same as in klog36343

Each optimal demod. phase for PRMI and Xarm is written as follows,

θPRMI=ωmodc(LEOM2PRM+LPRM2PD)\theta_{\mathrm{PRMI}} = \frac{\omega_{\mathrm{mod}}}{c} (L_{\mathrm{EOM2PRM}} + L_{\mathrm{PRM2PD}})

θXarm=ωmodc(LEOM2PRM+2(LPRM2BS+LBS2ITMX)+LPRM2PD)\theta_{\mathrm{Xarm}} = \frac{\omega_{\mathrm{mod}}}{c} (L_{\mathrm{EOM2PRM}} + 2 (L_{\mathrm{PRM2BS}} + L_{\mathrm{BS2ITMX}}) + L_{\mathrm{PRM2PD}})

where, omega_{mod} is a modulation angular frequency, L_{A2B} is a distance from A to B (A,B: EOM, PD, PRM, BS, ITMX), and c is a speed of light. These phase difference is derived as

θXarm-θPRMI=ωmodc×2(LPRM2BS+LBS2ITMX)=ωmodc×2(LPRM2BS+LBS2ITMX+LBS2ITMY2+LBS2ITMX-LBS2ITMY2)=ωmodc×2(LPRCL+Lasym2)\theta_{\mathrm{Xarm}} - \theta_{\mathrm{PRMI}} = \frac{\omega_{\mathrm{mod}}}{c} \times 2(L_{\mathrm{PRM2BS}}+ L_{\mathrm{BS2ITMX}}) = \frac{\omega_{\mathrm{mod}}}{c} \times 2(L_{\mathrm{PRM2BS}}+ \frac{L_{\mathrm{BS2ITMX}} + L_{\mathrm{BS2ITMY}}}{2} + \frac{L_{\mathrm{BS2ITMX}} - L_{\mathrm{BS2ITMY}}}{2}) = \frac{\omega_{\mathrm{mod}}}{c} \times 2(L_{\mathrm{PRCL}} + \frac{L_{\mathrm{asym}}}{2})

we can derive

LPRCL+Lasym2=c2ωmod(θXarm-θPRMI)L_{\mathrm{PRCL}} + \frac{L_{\mathrm{asym}}}{2} = \frac{c}{2\omega_{\mathrm{mod}}} (\theta_{\mathrm{Xarm}} - \theta_{\mathrm{PRMI}})

## Results

Fig.1 and Fig.2 show the results of measurements for Xarm and PRMI, The optimal demod. phases of REFL PDA3 RF45 for Xarm and PRMI were 230.14 degrees and 117.80 degrees, respectively. (I forgot to note the error value...)

If I assumed 20*360 degrees additional rotation because 45 MHz is 20 times FSR of PRMI, L_PRCL + L_asym/2 = 2.9979e8 * (20*360 + 230.14 -117.80) / (2*360 * 8* 5.624365513 MHz) ~ 67.67 m

It seems to be inconsistent with the design value (L_PRCL + L_asym/2 = 66.591 + (26.6649 - 23.3351)/2 = 68.2559 m (ref. JGWwiki)).

We are not sure of the cause of this discrepancy. We suspect that the RF45 sideband is not exactly at the anti-resonance point of the PRMI. As a result, its reflection phase deviates from 180°. This effect is expected to be more noticeable in the low-finesse PRMI than in the high-finesse X arm cavity.

But we did not confirm whether the SNR is enough or not with PRMI configration. We need more investigation.

Images attached to this report
MIF (General)
shun.saito - 21:56 Wednesday 22 July 2026 (37243) Print this report
Comment to Measurement of the PRC/SRC length using the beat signal at OMC REFL (37178)

[Kawakami, Komori, Tanaka, Saito]

A mixer and a 140 MHz low-pass filter were inserted between the 20 dB RF amplifier and the 45 dB RF amplifier. By setting the mixer's LO frequency to 350 MHz, the beat signal at approximately 450 MHz was successfully down-converted to approximately 100 MHz. PLL operation was successfully achieved using this down-converted signal. In the next experiment, a spectrum analyzer will be installed at the OMC REFL port, and since the mixer supports input frequencies up to 500 MHz, beat signals up to approximately ±500 MHz will be analyzed. The cavity lengths of SRX, SRY, PRX, and PRY will then be measured by applying the same fitting procedure used in klog:37209.
 

  • First, the signal after the 20 dB RF amplifier was monitored with a spectrum analyzer, and the sub-laser temperature was adjusted so that the beat frequency became approximately 450 MHz. A mixer and a 140 MHz low-pass filter were then inserted between the 20 dB RF amplifier and the 45 dB RF amplifier. In addition, the 10 dB attenuator located before the PFD was removed. The current control chain from the RFPD to the sub-laser PZT is as follows:

    RFPD → 12 MHz high-pass filter → 20 dB RF amplifier → mixer → 140 MHz low-pass filter → 45 dB RF amplifier → power splitter → PFD → 100 kHz low-pass filter → Moku:Lab (100 Hz integrator, 10 kHz low-pass filter) → SR560 (gain = 200, 1 Hz low-pass filter) → 20 dB high-voltage amplifier → sub-laser PZT
     

  • With the mixer's LO frequency set to 350 MHz, the signal taken from the power splitter before the PFD was monitored using the Moku:Lab spectrum analyzer, and the beat signal was observed at approximately 100 MHz. When the mixer's LO frequency was decreased, the beat frequency increased, confirming that the original beat signal was at approximately 450 MHz. Since the PFD locks with an offset when the input frequency is too low, the sub-laser temperature was adjusted so that the down-converted signal became approximately 160 MHz. The mixer's LO frequency was then changed to 340 MHz, resulting in a down-converted beat frequency of approximately 135 MHz. Finally, by setting the PFD LO frequency to 135 MHz, stable PLL lock was successfully achieved.

  • In the next experiment, a spectrum analyzer will be installed at the OMC REFL port. Since the mixer can process signals up to 500 MHz, beat signals up to approximately ±500 MHz will be measured. The same fitting procedure as in klog:37209 will then be applied to determine the lengths of the SRX, SRY, PRX, and PRY cavities.

DetChar (General)
takahiro.yamamoto - 21:53 Wednesday 22 July 2026 (37242) Print this report
Update of cache script on Kashiwa cluster
The cache making script had a bug which sometimes made failure and a fixed version of script had been prepared (klog#36476). It was already deployed in Kamioka but not yet done in Kashiwa because of Git conflict issue due to a so bad manner of git operation. I requested to fix this Git issue several times, but there was no sign that they intended to address it in recent several months, so I decided to force a resolution.

I committed all tracked but uncommitted changes on Kashiwa cluster to the "Kashiwa_O4c_local_fix" branch and cleaned up the master branch. (Note that due to the unbelievable operation that personal `user.name` and `user.mail` had been added to the gitconfig of a shared account, this commit was not signed by my account.) After then, I updated the master branch to match origin/master, which had already contained an update of the cache script.

Finally, a process to make cache files on Kashiwa cluster was migrated to the new script (/home/detchar/git/kagra-detchar/tools/Cache/Script/makeCache.sh in master branch). Condor submission was also migrated from condor_submit via crontab to cron parameters in the submission file. A new submission style is served via /home/detchar/git/kagra-detchar/tools/Cache/Script/condor-makeCache.sh.

Committed changes to the "Kashiwa_O4c_local_fix" branch can be seen by using git diff O4c Kashiwa_O4c_local_fix. If these changes are necessary, please merge, commit and push them.
CAL (YPcal)
Misato Onishi - 17:42 Wednesday 22 July 2026 (37241) Print this report
YPcal new laser beam profile
With Dan Chen, Seiya Matsuo

As part of the installation work for the new YPcal laser, we measured the beam profile of the new laser.
The beam profile was measured at both the Tx module and the Rx module.
The measured beam profiles were similar to those previously measured for the current laser.

We also attempted to measure the beam profile outside the Tx module.
However, we found that part of the beam was clipped by the mirrors in the periscope.
To resolve this issue, we adjusted the position of the periscope used to extract the beam from the Tx module.

Next, we will measure the beam profile of the beam extracted from the Tx module and characterize the OFS loop.
Images attached to this report
ISC (General)
hirose.chiaki - 12:57 Wednesday 22 July 2026 (37239) Print this report
Performed the initial alignment for Xarm, Yarm, PRMI, and SRY

[Kawakami, Tanaka, Hirose]

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

  • We attempted DRMI initial alignment partway through, but since the BS ADS isn’t working correctly, adjustments are needed to separate the signal degrees of freedom.
  • During the SRY initial alignment, the amplitude of the SRCL control feedback signal was saturating, so following Ushiba-san's advice, we turned on FM7 (Elptrick Filter 500 Hz). We also modified the settings so that it turns on every time in the “LOCKING_SRC_3F” state of the VERTEX Guardian.
CAL (General)
takahiro.yamamoto - 9:31 Wednesday 22 July 2026 (37238) Print this report
Comment to Installation of the new LL CAL server (36896)
The DMT network is now available in the Mozumi server room (klog#37175), so this new LL server was connected to the DMT network as cal-gst3 (see also Wiki).
Environment for the LL reconstruction hasn't been set up yet.
MIF (General)
shun.saito - 19:21 Tuesday 21 July 2026 (37237) Print this report
Comment to Measurement of the PRC/SRC length using the beat signal at OMC REFL (37178)

[Tanaka, Saito]

The sub-laser was injected into the SRY cavity, and the PLL was locked. The LO frequency was then frequency-modulated by ±10 kHz at a modulation frequency of 1 kHz. As a result, a signal appeared at 1 kHz in the power spectrum of the OMC REFL DC PD. By adjusting the LO frequency to minimize this signal, its amplitude was reduced to approximately the noise floor. To further improve the frequency resolution, the frequency modulation amplitude was increased to ±30 kHz. However, the amplitude of the 1 kHz signal changed in response to spontaneous fluctuations in both the frequency and amplitude of the beat signal observed at the OMC REFL RF PD, making it difficult to determine the beat frequency with 1 kHz-level precision. Therefore, it is considered that the beat frequency can be determined with a precision on the order of 10 kHz.
 

  • First, the SRY cavity was locked, and the main-laser intensity noise measured by the OMC REFL DC PD was reduced to a level comparable to that reported in klog:37144. The sub-laser was then injected into SRY, and the PLL was locked. A Moku:Lab was used as the LO source. Using its frequency modulation function, the LO frequency was swept by ±2 MHz at 10 mHz, and the LO frequency was adjusted to approximately maximize the beat signal observed at the OMC REFL RF PD.
     
  • Next, the LO frequency was modulated by ±10 kHz at 1 kHz. A spectral peak approximately five times higher than the noise floor appeared at 1 kHz in the power spectrum of the OMC REFL DC PD. The LO frequency was then adjusted so as to minimize this peak, and at a certain frequency the peak became comparable to the noise floor. To improve the frequency accuracy further, the modulation amplitude was increased to ±30 kHz. This again produced a peak at 1 kHz, and the LO frequency was adjusted in 1 kHz increments to minimize it. However, the amplitude of the 1 kHz peak varied together with spontaneous changes in the frequency and amplitude of the beat signal observed at the OMC REFL RF PD. As a result, determining the beat frequency with 1 kHz-level precision proved difficult. It is therefore concluded that the beat frequency can be determined with a precision on the order of 10 kHz.
     
  • The final power spectra of the OMC REFL DC PD are shown in Figures 1 and 2. In Figure 1, the red trace corresponds to the present measurement. Its higher noise level at high frequencies compared with the other traces is attributed to the additional intensity noise from the sub-laser. In Figure 2, the green trace was measured with the sub-laser injected but without LO frequency modulation; the blue trace was measured after initially adjusting the LO frequency to approximately maximize the OMC REFL beat signal; and the red trace was measured after increasing the modulation amplitude to ±30 kHz and fine-tuning the LO frequency with approximately 1 kHz resolution.
Images attached to this comment
VAC (Valves & Pumps)
koji.nakagaki - 11:38 Tuesday 21 July 2026 (37235) Print this report
Comment to Acquiring the Open/Closed Status of the Gate Valve Between PRM and PR3 (37198)

[ Kimura, Nakagaki ]

We tested the device for acquiring the open/closed status of the PRM-PR3 gate valve and confirmed that it operates correctly.

DGS (General)
takahiro.yamamoto - 20:20 Monday 20 July 2026 (37234) Print this report
Minute trend rotation
Old minute frames were removed on the storage for k1fw0.
Removed time segment is [1400000000, 1450000000)

These data is available on Kashiwa.
Undelivered files can be found in the attached files and are still kept on k1fw0.
Non-image files attached to this report
ISC (General)
takafumi.ushiba - 17:50 Saturday 18 July 2026 (37233) Print this report
Precise measurement of the schnupp asymmetry

Abstract:

I measured the schnupp asymmetry in the same manner as written in klog36343.
Since REFL PDA3 is the best sensor to use according to the previous measurement, I only used REFL PDA3 in this time.
Obtained result is  3.3443(16) m, which is really consistent with the values calculated from the results of the individual length measurement of PRX/PRY and SRX/SRY reported in klog37209 and klog37223.

Detail:

To verify the PRCL/SRCL measurement by checking the consistency of the Schnupp asymmetry between the values calculated from the length of PRX/PRY and SRX/SRY reported in  klog37209 and klog37223 and from the time of flight measurement, I repeated the Schnupp asymmetry measurement reported in klog36343 with greater precision.

What I changed from the previous measurement are followings:
1. Increase the laser power from 1.2 W to 11.5 W.
2. Increase the averaging time for each measurement data from 10 second to 60 second.
3. Increase the amplitude of frequency modulation (excitation to MCE suspension) from 100 cnts to 200 cnts.

Thanks to the above modification, errors of the estimation of the optimal phase difference between X arm and Y arm were improved, resulting in the accurate result.
Figure 1 to 4 shows the measured data and fitting results.
Measurement data and fitting results are stored in //users/Commissioning/scripts/schnupp/260718/.

I summarized the optimal phase and its errors in the following table.

  optimal phase [deg] errors [deg]
PDA3 REFL 45 I with XARM 230.031196 0.071549
PDA3 REFL 45 Q with XARM -40.019504 0.059909
PDA3 REFL 45 I with YARM 230.725665 0.048606
PDA3 REFL 45 Q with YARM -39.320663 0.047302

During the measurement, seed frequency for the f2 sideband was 5.624365513 MHz.

By using above results, schnupp asymmetry can be estimated as follows:
dL = 3.3443(16) m from PDA3 REFL 45 I with XARM and PDA3 REFL 45 I with YARM.
dL = 3.3443(14) m from PDA3 REFL 45 Q with XARM and PDA3 REFL 45 Q with YARM.

Schnupp asymmetry calculated from the PRX/PRY and SRX/SRY length in klog37209 and klog37223 are 3.3405(48), both results are very consistent.

Note:

For the measurement, I deleted the sensing matrix values putting at XARM and YARM, which is implemented in the work reported in klog37228.
Figure 5 shows the values before deleting the input matrix.

Images attached to this report
ISC (General)
kenta.tanaka - 17:35 Friday 17 July 2026 (37232) Print this report
DRMI INITIAL ALIGNMENT Implementation

We confirmed that INITIAL_ALIGNMENT seems to work well. We made a medm screen for DRMI alignment. You can align PRM, SRM, BS, IMMT1 and IMMT2 by following this procedure.

## What we did

  • We implemented the states, "PREP_FOR_DRMI_ALIGN", "LOCKING_DRMI", "ENGAGE_ADS_DRMI", "ALIGNING_DRMI", and "RECORD_GOOD_VALUES_DRMI".
  • We made a medm screen in INITIAL_ALIGNMENT2407.adl (fig.1) to operate the DRMI initial alignment
  • We tested the state one by one from this medm screen. First, The guardian reaches the RECORD_GOOD_VALUES_DRMI state smoothly. The good alignment values of PRM, SRM, BS, and IMMT2 are recorded in each DRFPMI_GOOD_OPLEV_{PIT, YAW} channel (fig.2). However, offloading was not worked at that time. We found that an offload script, reset_ASC_feedback.py was not worked if the values were recorded in DRFPMI_GOOD_OPLEV channels. Yamamoto-san modified the script.
  • After the modification, offloading works well.
Images attached to this report
PEM (General)
Chia-Jui Chou - 15:55 Friday 17 July 2026 (37231) Print this report
Coherence Analysis of the PSL Shaker Injection Test

[Min Chen, Yuchen Liu, Chia-Jui Chou, Takaaki Yokozawa]

We investigated the coherence of 24 auxiliary channels with the online strain channel during the shaker injection test conducted in February 2026. The summary of the shaker injection test can be found here:

https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=17238

We calculated the coherence between 24 auxiliary channels and online strain channel and ranked the channels according to the coherence values. Then we pick the channels with top 4 ranks with coherence value larger than 0.2 into the important channel list between 280 Hz to 420 Hz. Here are the important channels:

– K1:IMC-REFL QPDA1 DC PIT OUT DQ
– K1:IMC-REFL QPDA1 DC YAW OUT DQ
– K1:IMC-REFL QPDA1 RF14 I PIT OUT DQ
– K1:IMC-REFL QPDA1 RF14 I YAW OUT DQ
– K1:IMC-REFL QPDA1 RF14 Q PIT OUT DQ
– K1:IMC-REFL QPDA2 DC PIT OUT DQ
– K1:IMC-REFL QPDA2 DC YAW OUT DQ
– K1:IMC-REFL QPDA2 RF14 I PIT OUT DQ
– K1:IMC-REFL QPDA2 RF14 I YAW OUT DQ
– K1:IMC-REFL QPDA2 RF14 Q PIT OUT DQ
– K1:IMC-REFL QPDA2 RF14 Q YAW OUT DQ
– K1:PSL-IP QPD1 DC PIT OUT DQ
– K1:PSL-IP QPD2 DC PIT OUT DQ
– K1:PSL-IP QPD2 DC YAW OUT DQ

The detailed report can be found here:

https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=17451

The coherence plots can be found here:

https://ldas-jobs.ligo.caltech.edu/~chiajui.chou/K1-o4c-coherence/

Images attached to this report
VIS (SRM)
ryutaro.takahashi - 9:30 Friday 17 July 2026 (37230) Print this report
Offload of F0 GAS

I offloaded the F0 GAS with the FR a little. The FR closes a movable limit.

CAL (Pcal general)
dan.chen - 5:18 Friday 17 July 2026 (37229) Print this report
Comment to Pcal guardian update (37219)

I had tested the Pcal GRD code.

It works as we expect.

ISC (General)
kenta.tanaka - 2:57 Friday 17 July 2026 (37228) Print this report
Trial the transition from 1f to 3f of DRMI lock

Aritomi, Tanaka

We performed some trials, mainly transition from 1f to 3f. But the trial was not work. We need more investigation.

### DRMI lock modification

This morning, DRMI lock got unstable for some reasons. One reason is that MICH loop is oscillated at SRM ADS frequency: ~6 Hz. At that moment, we were not sure of the cause of the oscillation. At once, we turned off only SRM ADS. Also, we changed the setpoints. Then, DRMI lock became stable a little. Another reason is that sometimes PRCL began the oscillation at ~100 Hz. After DRMI lock becoming stable a little, we measued the OLTFs. PRCL UGF increased to 100 Hz though the phase margin was less than 10 deg. So we lowered the gain. Similarly, SRCL OLTF seems to get better. We adjusted the gain. Current SRCL UGF is ~60 Hz (fig.1), PRCL UGF is ~40 Hz (fig.2).

Finally, the gains of the loop summerized the FM4 filter.

### Trial of the transition from 1f to 3f

To transit to 3f signal, we performed the phasing of 3f signals. we followed the procedure in klog32604.  As for PRCL, we performed the phasing for REFL135 PD to maximize the I signal when PRCL was excited(fig.3). As for SRCL, we performed the phasing for REFL51 PD to maximize the I signal when SRCL was excited (fig.4). After that, we checked the RF51 signal when MICH was excited. Although the demod. phase is optimized for the SRCL signal, I signal was larger than Q signal when MICH was excited because BS motion is mixture with common and differential length change (fig.5). So we may need to decouple each motion. However, this time, we proceeded our work with this state.

We measued each relative gain and phase between 1f and 3f signals. the figures in the right lower 2 panes of fig. 3, 4, and 5 show each gain and phase of PRCL, SRCL, and MICH. As you can see, the relative phase of SRCL and PRCL seems to be 180 deg. But, the phase of MICH is 40 deg since there are some couplings. Anyway, we input these values in matrix (fig.6) and tried the transition. Then we succeeded PRCL and SRCL transition but failed MICH transition. So we moved the decoupling.

To decouple the DoFs, we excited the one DoFs, PRCL (left panel in fig.1) or SRCL (left panel in fig.2) and measued the relative gain and phase of between excited DoF error signal and others' error signal. From the results, I chosed CARM_IN1 as decoupled sensor for MICH 3F for the test, XARM_IN1 as decoupled SRCL 3F, and YARM_IN1 as decoupled PRCL 3F. After the decoupling, I measured the coupling but the ratio seems not to changed. 

### DRMI ADS modification

This morning, we also found that DRMI began the oscillation at ~6 Hz just after engaging ADS. 6.3 Hz is the dither frequency of SRM YAW. The resG for SRM ADS in the MICH loop caused the oscillation. After decoupling the 1f error signals, MICH OLTF seems to got better than before. According to the MICH loop, current MICH UGF is around 10 Hz (fig.6). So I turned off the resG filter in engaging ADS. Then, ADSs seem to become stable.

### DRMI alignment Implementation to the INITIAL_ALIGNMENT guardian

After the modification of DRMI ADS, I implemented the DRMI alignment state with DRMI_1F_LOCKED into the INITIAL_ALIGNMENT guardian. I have not checked INITIAL_ALIGNMENT guardian behavior due to the earthquake.

Images attached to this report
CAL (YPcal)
Misato Onishi - 16:45 Thursday 16 July 2026 (37227) Print this report
YPcal new laser alignment

With Dan Chen


We continued the work from the previous day. (klog_37206)

By adjusting the two mirrors newly installed inside the Pcal-Y Tx module (Fig. 1), we successfully aligned the new laser beam and propagated it to the RxPD.

On the RxPD, the beam position of the new laser appeared to be nearly identical to that of the current laser. The beam positions of the current laser and the new laser are shown in Fig. 2 and Fig. 3.

We also closed the OFS loop, and it appeared to operate normally.

 

Images attached to this report
CAL (Pcal general)
Jinshui Tian - 16:29 Thursday 16 July 2026 (37226) Print this report
Comment to Pcal guardian update (37219)

Due to some remaining issues with the previous Pcal Guardian system, we have now updated the Pcal Guardian code to address these issues. The specific details are as follows:

Issue 1: Swap the order of HIGH_POWER and HIGH_POWER_RX_MON.

Before: INCREASE_OFFSET → HIGH_POWER_RX_MON → HIGH_POWER ⇄ WAITING_IFO    HIGH_POWER_RX_MON →  DECREASE_OFFSET   HIGH_POWER →  DECREASE_OFFSET

class HIGH_POWER(GuardState): 
    index = 100 
    request = False 
 
class HIGH_POWER_RX_MON(GuardState): 
     index = 95 
 
       ('INCREASE_OFFSET', 'HIGH_POWER_RX_MON'), 
       ('HIGH_POWER_RX_MON', 'HIGH_POWER'), 
       ('HIGH_POWER_RX_MON', 'DECREASE_OFFSET'), 
       ('HIGH_POWER', 'DECREASE_OFFSET'), 
       ('HIGH_POWER','WAITING_IFO'), 
       ('WAITING_IFO', 'HIGH_POWER'), 

Update: INCREASE_OFFSET → HIGH_POWER ⇄ HIGH_POWER_RX_MON ⇄ WAITING_IFO   HIGH_POWER →  DECREASE_OFFSET   HIGH_POWER_RX_MON →  DECREASE_OFFSET

 

class HIGH_POWER(GuardState): 
    index = 95 
    request = False 
 
class HIGH_POWER_RX_MON(GuardState): 
     index = 100 
 
       ('INCREASE_OFFSET', 'HIGH_POWER'), 
       ('HIGH_POWER', 'HIGH_POWER_RX_MON'), 
       ('HIGH_POWER_RX_MON', 'DECREASE_OFFSET'), 
       ('HIGH_POWER_RX_MON', 'HIGH_POWER'), 
       ('HIGH_POWER', 'DECREASE_OFFSET'), 
       ('HIGH_POWER_RX_MON','WAITING_IFO'), 
       ('WAITING_IFO', 'HIGH_POWER_RX_MON'),

 

2.Issue: Turn on the injection switches in HIGH_POWER, and turn them off automatically when leaving the state.

Update: Added code to automatically turn on the injection switches in the HIGH_POWER state and automatically turn them off when leaving that state (entering HIGH_POWER_RX_MON or DECREASE_OFFSET).

class HIGH_POWER(GuardState):
    def main(self):
        self.ARM='E'+SYSTEM[10]
        ezca['CAL-PCAL_{0}_0_INJ_V_SW'.format(self.ARM)] = 1

 

class HIGH_POWER_RX_MON(GuardState):
    def main(self):
        self.ARM='E'+SYSTEM[10]
        ezca['CAL-PCAL_{0}_0_INJ_V_SW'.format(self.ARM)] = 0

 

class DECREASE_OFFSET(GuardState):
    def main(self):
        ARM='E'+SYSTEM[10]
        ezca['CAL-PCAL_{0}_0_INJ_V_SW'.format(ARM)] = 0

 

3.Issue: Send a Slack notification if Guardian remains in HIGH_POWER for an extended period.

Update: Added the code to send a Slack notification.

class HIGH_POWER(GuardState):
    def main(self):
        self.slack_time_1h = params[self.ARM]['wait_time_slack_1h']
        self.timer['slack'] = self.slack_time_1h
    def run(self):
        notify('Pcal-{0} is in HIGH_POWER state.'.format(self.ARM))
        if self.timer['slack']:
                message = f'{self.ARM} PCAL HIGH_POWER state for too long (>{self.slack_time_1h}s)'
                kagralib.slackpost("pcal", message, ["U015912SQ5T"])
                self.timer['slack'] = self.slack_time_1h

 

4.Issue: Allow the real-time model to be stopped in the SAFE state.

Update: changed @lpd_check to a comment in the SAFE state.

class SAFE(GuardState):
    index = 1
    #@lpd_check # -> FAULT
    @shutter_check # -> TOSAFE
    @loop_check # -> TOSAFE
    @injection_check # -> TOSAFE
    def main(self):
        ### safe should be loaded independent on gSDF
        if ezca['GRD-CAL_PCAL_{0}_REQUEST_S'.format(gARM)] == self.name:
            sdf.restore(gFEC, self.name.lower())
    #@lpd_check # -> FAULT
    @shutter_check # -> TOSAFE
    @loop_check # -> TOSAFE
    @injection_check # -> TOSAFE
    def run(self):
        return True
MIF (General)
shun.saito - 13:57 Thursday 16 July 2026 (37225) Print this report
Comment to Measurement of the PRC/SRC length using the beat signal at OMC REFL (37178)

The fitting results for the individual SRX resonance peaks presented in klog:37223 are summarized below. The measurement data are stored in Dropbox → All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMC_REFL_beat_signal_LO_sweep/2026_07_14_SRX.
 

  • Figure 1: Around 190 MHz, without a linear background. Using data from 194.7 MHz to 195.5 MHz, the fitted peak frequency is 195.1834 ± 0.0034 MHz.
    Figure 2: Around 190 MHz, with a linear background. Using data from 194.7 MHz to 195.5 MHz, the fitted peak frequency is 195.293 ± 0.018 MHz.
     
  • Figure 3: Around 160 MHz, without a linear background. Using data from 161.8 MHz to 162.6 MHz, the fitted peak frequency is 162.3010 ± 0.0040 MHz.
    Figure 4: Around 160 MHz, with a linear background. Using data from 161.8 MHz to 162.6 MHz, the fitted peak frequency is 162.415 ± 0.019 MHz.

  • Figure 5: Around 140 MHz, without a linear background. Using data from 126.9 MHz to 127.48 MHz, the fitted peak frequency is 127.1931 ± 0.0026 MHz.
    Figure 6: Around 140 MHz, with a linear background. Using data from 126.9 MHz to 127.48 MHz, the fitted peak frequency is 127.2057 ± 0.0026 MHz.
     

  • Figure 7: Around −140 MHz, without a linear background. Using data from 125.0 MHz to 125.8 MHz, the fitted peak frequency is 125.3625 ± 0.0061 MHz.
    Figure 8: Around −140 MHz, with a linear background. Using data from 125.0 MHz to 125.8 MHz, the fitted peak frequency is 125.235 ± 0.031 MHz.
     

  • Figure 9: Around −160 MHz, without a linear background. Using data from 157.9 MHz to 158.7 MHz, the fitted peak frequency is 158.2421 ± 0.0048 MHz.
    Figure 10: Around −160 MHz, with a linear background. Using data from 157.9 MHz to 158.7 MHz, the fitted peak frequency is 158.1853 ± 0.0091 MHz.
     

  • Figure 11: Around −190 MHz, without a linear background. Using data from 193.0 MHz to 193.8 MHz, the fitted peak frequency is 193.3150 ± 0.0033 MHz.
    Figure 12: Around −190 MHz, with a linear background. Using data from 193.0 MHz to 193.8 MHz, the fitted peak frequency is 193.2798 ± 0.0058 MHz.

Images attached to this comment
Search Help
×

Warning

×