I added VIS Check Button.

We turned on the OBS INTENT around 19:29 JST after the weekly calibration work.

K1CALCS

Channels in JGW-L2314962

It's related to klog#34597
They were updated based on the latest value of optical gain of DARM and ETMX actuator efficiencies in klog#34601.

Changes were accepted on observation.snap (Fig.1), down.snap (Fig.2), and safe.snap (Fig.3).
Finally, numerical rounding errors were reverted after re-loading observation.snap as shown in Fig.4.

We accepted SDFs related to the cal measurement in observation.snap, and safe.snap and down.snap (k1calcs).
K1:CAL-MEAS_{CURRENT, LATEST}

CAL group
We did the calibration measurements and updated the parameters.

This time we needed to change the fiting limit in parameters_fit.py
Original: m.limits["H_c"] = (self.H_c * 0.95 * 1e-12, self.H_c * 1.05 * 1e-12)
New: m.limits["H_c"] = (self.H_c * 0.90 * 1e-12, self.H_c * 1.10 * 1e-12)

Estimated parameters in the Pre-maintenance measurements are as follows.
 H_etmxtm = 3.831118314e-14 @10Hz ( -0.67% from previous measurements)
 H_etmxim = 1.549324464e-14 @10Hz  ( -3.40% from previous measurements)
 Optical_gain = 2.057370638e+12   ( -0.86% from previous measurements)
 Cavity_pole = 18.205397988 Hz  ( 0.44% from previous measurements)

Previous values are listed in klog#34533.

Estimated parameters in the Post-maintenance measurements are as follows.
 H_etmxtm = 3.845556852e-14 @10Hz ( 0.38% from pre-maintenance measurements)
 H_etmxim = 1.502986128e-14 @10Hz  ( -2.99% from pre-maintenance measurements)
 Optical_gain = 2.043225053e+12   ( -0.69% from pre-maintenance measurements)
 Cavity_pole = 18.072043623 Hz  ( -0.73% from pre-maintenance measurements)

Fig.1 and Fig.2 show the fitting results.
Fig.3 and Fig.4 show the ratio of the sensing functions

[Hido, Yuzurihara]

Hido-san reported that there was a duplication in the recent cache files at the kmst-2 (Kashiwa cluster). The time of the duplication are summarized in the attached txt file. I checked several thing, but I'm not sure the critical cause. It's better to perform the countermeasure.

Details

• As I checked the history of condor submission, the job to produce the cache file finished without errors.
• I found many job were running around the time of the duplication.
  • To separate the cause of the duplication, I tried to run many jobs to occupy the cpu resources and to run the job in the detchar account. The last submitted job run at the dedicated cpu. So, the many jobs are not direct cause.
  • Note that the job to produce the cache file is running at the dedicated cpu since 2025/05/07 (see klog33698).
• I reproduced the cache files for 14359, 14360, 14366 directories. The cache files including the duplication are stored in /home/detchar/work/20250718_HTcondor 
• We will need to reproduce the segment files for these time, after several checks.
• As a countermeasure, it's better to update the script to remove the duplications in the cache file (such as using uniq). Before running the script regularly, I will test the script.

We accepted Pcal beam position related SDF diffs as reported klog34593.

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

Operator: Nagisa Sembo, Shingo Hido, Dan Chen

Update Time: 2025/07/18 15:22:18

Update Time: 2025/07/18 15:22:54

Update Time: 2025/07/18 15:23:28

Update Time: 2025/07/18 15:23:59

We accepted Pcal beam position related SDF diffs as reported klog34588.

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

Operator: Shingo Hido, Nagisa Sembo, Dan Chen

Update Time: 2025/07/18 09:57:04

Update Time: 2025/07/18 09:58:03

Update Time: 2025/07/18 09:58:50

Update Time: 2025/07/18 09:59:14

[1]+ Done emacs pcal_update_report.html

I took the TCam photos for four mirrors at 9:37 ~ 9:42 this morning. The previous work is klog34514.

• ETMY
  • original
  • fitting result
  • previous reference
• For these mirrors, I updated the reference positions. I also re-draw the yellow line shown at the k1mon4. For the other mirrors, we don't need to update the reference positions.

We turned off the OBS INTENT around 08:00 JST for CAL work.

EY_4K_REF3_50K temp continues decreasing, but it was slow.

Both IX_REF1_50K/4K_HEAD temperatures recovered as in Fig.1.

[Ushiba, Komori]

Abstract:

We measured the transfer functions from the BF GAS, BF damper, and F3 GAS to DARM and performed a noise budget analysis for the corresponding coil driver noises.
All were found to be negligible.

Detail:

In a previous study, we observed a significant improvement in DARM sensitivity upon enabling the dewhitening filters for the type-A tower suspensions (klog:33197).
This raised the possibility that coil driver noise from these suspensions might be limiting the current DARM sensitivity.
To assess this, we measured the transfer functions from selected type-A suspensions to DARM and evaluated the associated noise contributions.

We selected three suspensions—BF GAS, BF damper, and F3 GAS—since they are located closest to the cryopayload, and thus expected to have the largest potential impact.

First, we estimated the coil driver noises of the BF damper and F3 GAS to be negligible.
The nominal coil driver noise levels are 3.3e-5 cnt/√Hz at each SUMOUT port (klog:33428).
Even when injecting white noise of 1e-2 cnt/√Hz at 5-100 Hz, no significant coherence with DARM was observed.
An example is shown in Fig. 1, where the left bottom panel shows no coherence between DARM and IY BF_V3, despite the noise injection of 1e-2 cnt/√Hz (right middle panel).

Next, we injected white noise at the SUMOUT ports of the BF GAS actuators with amplitudes of 1e-2 cnt/√Hz for EX, EY, and IX, and 3e-2 cnt/√Hz for IY.
This resulted in observable coherence in the 15-45 Hz range (Figs. 2-5).
The projected noise contributions can be roughly estimated by scaling the excited spectra by the ratio of the nominal noise to the injection level: 3.3e-5/1e-2 = 3.3e-3 for EX, EY, IX and 3.3e-5/3e-2 = 1.1e-3 for IY.
These projections are shown in Fig. 7 and confirm that even the coil driver noise from the BF GAS is negligible.

Discussion:

Figure 6 compares the nominal DARM spectrum with those obtained during noise injection into the BF GAS actuators.
While we observed an increase in DARM noise by a factor of a few or an order of magnitude in the 15-45 Hz range, we also saw a clear degradation of sensitivity in the 60-100 Hz band.
This suggests that a nonlinear noise source—possibly related to the observed coherence—is close to the current sensitivity limit, as also suggested by klog:34571.

In Fig.8, we compare the SUMOUT noise spectra of the BF GAS actuators during nominal interferometer operation.
The noise in IY GAS is consistently below the coil driver noise level of 3e-5 cnt/√Hz, whereas other suspensions exceed this threshold at certain frequencies.
The broad 2e-4 cnt/√Hz noise observed at IX may be explained by numerical errors in diaggui due to large DC offsets.
The excess noise below 20 Hz at EX and EY might be reduced by implementing more aggressive low-pass filter at the control stage.

Finally, this result can be inconsistent with the prior observation that enabling the dewhitening filters improved the DARM sensitivity.
The DAC noise without dewhitening is at most 4e-4 cnt/√Hz, which still seems too small to explain the observed sensitivity limitation.
Further investigation is needed—such as turning off the dewhitening filters one by one and monitoring the impact on sensitivity—to resolve this discrepancy.

Abstract:

We injected sine excitation at 6.125Hz to increase the RMS of OMC transmission.
Though RMS was increased by a factor of 5.7, no significant excess can be seen around 60-100Hz, so low frequency RMS doesn't seem problematic.
I also estimated the siderobe due to the low frequency spectrum and it seems negligible as well.

Detail:

We measured the spectrum of calibrated DARM displacement and OMC trans power by injecting the sine signals from DARM error point.
Excitation frequency was 6.125 and amplitudes are 10e-6, 20e-6, 30e-6, 40e-6, and 50e-6 cnts.
Figure 1 shows the measured spectra (excitation amplitude is written in the legend and blue lines are the spectrum without excitation for the reference).
Even though the RMS was increased by a factor of 5.7, no significant excess can be seen around 60-100Hz.
So, DARM non-linear coupling due to low-frequency RMS doesn't seem to contaminate the sensitivity around 60-100Hz.

In addition, we evaluated the siderobe of low frequency spectrum.
When we injected the line at 6.125Hz, 50.875Hz peak was appeared in OMC trans spectrum, which generated due to non-linear coupling between 44.75Hz peak and 6.125Hz peak (see fig2).
According to the peak height at 50.875Hz, sideband peak height was propotional to the peak height at 6.125Hz, so we can evaluate the siderobe of 44.75Hz peak from the OMC trans spectrum.
Figure 3 shows the estimated siderobe generated due to 44.75Hz.

Though the noise floor is low enough, some peaks are very close to the current sensitivity.
So, damping/supressing the peaks aroun 20Hz and 40Hz seems effective to mitigate the sensitivity degradation when suspension resonances are kicked.
In addition, each peak should have a similar effect, so the summation of siderobe would be contaminate the sensitivity even during steady state.

So, it would be worth trying to damp/supress the resonant peaks.

To prevent unfortunate accidents such as klog#34539, I added some indicators on the MEDM screens.

1) Calibration measurements must be in CALIB_NOT_READY or READY because measured TFs are not ensured to be same as ones in OBSERVING if measurements are done in LOCKED state. So I added an indicator to notify that IFO guardian is LOCKED or below at a side of a "start meas." button as shown in Fig.1. Start measurement after confirming that IFO guardian is in CALIB_NOT_READY or READY. (BTW, we request OBSERVATION_WITHOUT_LINES to IFO guardian for our measurements. So IFO guardian falls down LOCKED state soon after starting measurement. This behavior is no problem.)

2) OBSERVING is always requested to IFO guardian in a normal case. But someone may request another state by mistakes. Though only OBSERVING was set as a requestable state, it was actually occurred. So it's difficult to avoid this issue completely. So I added information about STATE_S and REQUEST_S of IFO guardian on the OBS_INTENT interface as a plan-B (see also Fig.2). PM, RC, or CL can probably notice it on this interface even if someone accidentally requests other states to IFO guardian.

When we will raise OBS_INTENT bit,
- a requested state to IFO guardian must be OBSERVING.
- a current state of IFO guardian should be READY (Basically it must be READY. But when we confirmed that IFO can reach READY and we couldn't wait IFO came back to READY such as EQs occurring just before 22:00, it might be allowed to raise OBS_INTENT without IFO in READY?).

We turned on the OBS INTENT around 15:35 JST after the commissioning work today.