Reports of 33686
VIS (PR2)
ryutaro.takahashi - 15:15 Friday 06 February 2026 (36310) Print this report
Offload of IM

I offloaded the IM V OSEMs with the picomotors for pitch. It was performed in ALIGNED mode.

PEM (Center)
tatsuki.washimi - 15:08 Friday 06 February 2026 (36309) Print this report
Shakers installation in the PSL room

[Miyakawa, YokozaWashimi]

We installed 4 ahakers installation in the PSL room.

  1. Near the final periscope
  2. Near the ACC3 and the Laser source
  3. & 4. Near the suspect mirrors
Images attached to this report
PEM (Center)
takaaki.yokozawa - 15:00 Friday 06 February 2026 (36308) Print this report
Installation of the mini shakers to the PSL room
[Miyakawa, YokozaWashimi]

After the discussion with Miyakawa-san, we decided the position of the installation of the mini shakers at the PSL room and actually installed.

1. Near the periscope
EXC channel : K1:PEM-EXCITATION_SR3_RACK_9_EXC

2. Near the ACC3 (and master laser)
EXC channel : K1:PEM-EXCITATION_SR3_RACK_10_EXC

3. Near the weak mirror1 (after the PMC)
EXC channel : K1:PEM-EXCITATION_SR3_RACK_11_EXC

4. Near the weak mirror2 (after the PMC)
EXC channel : K1:PEM-EXCITATION_SR3_RACK_12_EXC
MIF (General)
takaaki.yokozawa - 14:54 Friday 06 February 2026 (36307) Print this report
Comment to Lock failed 260206 (36300)
It started the 02:08:24 2026/02/06 JST, and all MN and IM H and V photo sensor can be seen.
(IFO kept locked. LSC_LOCK =9998)
Images attached to this comment
IOO (OMC)
takahiro.yamamoto - 14:05 Friday 06 February 2026 (36306) Print this report
Comment to Proposal of compatibility update of OMC_LSC guardian for the new pylon-camera-server (36226)
DGS (General)
takahiro.yamamoto - 14:02 Friday 06 February 2026 (36305) Print this report
Migration of OMC_TRANS camera
OMC_TRANS camera which was still running as the old camlan camera-server was migrated to the pylon-camera-server.
OMC_LSC guardian was updated for compatibility fixes with the new pylon-camera-server, which was proposed in klog#36226.
With this work, all cameras have been migrated to pylon-camera-server.

Past related works
- k1cam2 as pylon-camera-server was newly installed (klog#36182).
- Cameras on k1cam0 as camlan camera-server were moved to k1cam2 (klog#36212).
- k1cam0 was upgraded to pylon-camera-server and cameras on k1cam1 except OMC_TRANS were moved to k1cam0 (klog#36284).

Remaining tasks
- Uninstall of old k1cam1
- Rename of k1cam2 as k1cam1
- Hardware replacement of k1cam0
PEM (Center)
tatsuki.washimi - 12:51 Friday 06 February 2026 (36304) Print this report
Comment to PEM injection test 260206 (36301)

Spectrograms for the  large shaker tests.

Images attached to this comment
PEM (Center)
tatsuki.washimi - 12:36 Friday 06 February 2026 (36303) Print this report
Comment to PEM injection test 260206 (36301)

Spectrograms for the  small shaker tests.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 11:30 Friday 06 February 2026 (36302) Print this report
Minute trend rotation
Until now, the minute frames had not been deleted from the Kamioka storage for k1nds0, but since the retention period for the second frames becames too short, the minute frames were deleted.
Deleted time segments is [1023500000, 1260000000), which is until just before O3GK.

Because NDS serves minute trend data via minute_raw files instead of minute frames and a direct access to frame files is restricted for end users, site activities aren't affected by this work.
(In this meaning, minute frames can be removed from the Kamioka storage except recent several days for SummaryPages and so on.)

-----
Minute frames before 1300000000 were already moved from KAGRA System-B to the ICRR computer system (see also [kagra07982]). So I compared the files between on the Kamioka storage and on the ICRR computer system and removed files on the Kamioka storage which can be found on the ICRR computer system. Some files and directories cannot be found on ICRR computer system. These files are still kept on the Kamioka storage. Removed and kept directories can be found in the attached files.

Missing files on ICRR computer system might be caused by the DAQ trouble on the k1fw1-hyades1 stream. I checked and removed files in this time on the k1fw0-hyades0 stream. On the other hand, the primary stream was (is?) k1fw1-hyades1 stream for a long time. So files existing only on the k1fw0 might not be sent to Kashiwa. I don't think these files has important information. (It's hard to know what kind of data for the too old and not in the observing period data. And also, trend data can be reproduced from raw frames with tough works if they are really needed.) But I will keep them for a while just in case.
Non-image files attached to this report
PEM (Center)
takaaki.yokozawa - 9:36 Friday 06 February 2026 (36301) Print this report
PEM injection test 260206
I performed the PEM injection test (continuously OMC bellows leg injection for evaluating the noise projection below 400 Hz)

07:07:00 - 07:20:00 silent run

07:20:00 - 08:03:40

Swept sine injection, 20 cnt, 400 - 180 Hz, 1 Hz resolution, 10 s in each frequency
K1:PEM-EXCITATION_SR3_RACK_7_EXC
Locked loss happened

08:30:00 - 08:56:00
K1:PEM-EXCITATION_SR3_RACK_7_EXC
Swept sine injection, 20 cnt, 180 - 50 Hz, 1 Hz resolution, 10 s in each frequency

9:00:00 - 9:35:00
K1:PEM-EXCITATION_SR3_RACK_8_EXC
Swept sine injection, 800 cnt, 50 - 10 Hz, 1 Hz resolution, 50 s in each frequency, 1 s setting time, 1 s ramp down
REF : K1:PEM-SEIS_OMC_GND_Z_OUT_DQ or K1:PEM-ACC_OMC_CHAMBER_OMCLEG_Z_OUT_DQ
Locked loss happened during the injection (maybe 12 or 13 Hz)
Comments to this report:
tatsuki.washimi - 12:36 Friday 06 February 2026 (36303) Print this report

Spectrograms for the  small shaker tests.

Images attached to this comment
tatsuki.washimi - 12:51 Friday 06 February 2026 (36304) Print this report

Spectrograms for the  large shaker tests.

Images attached to this comment
MIF (General)
takaaki.yokozawa - 6:02 Friday 06 February 2026 (36300) Print this report
Lock failed 260206
In this morning, the lock trial was failed after the ALS_DARM engaged, I tried to search the reason, about the2 Hz oscillation was quite large in ETMX.
During checking the ETMX control signals, I noticed that the glitch of about 2 Hz detected in MN photo sensor L.
But when I checked start time of this glitch, the 2 Hz glitch suddenly disappeared.
After then, locked loss succeeded without any problem.
What this??
Images attached to this report
Comments to this report:
takaaki.yokozawa - 14:54 Friday 06 February 2026 (36307) Print this report
It started the 02:08:24 2026/02/06 JST, and all MN and IM H and V photo sensor can be seen.
(IFO kept locked. LSC_LOCK =9998)
Images attached to this comment
MIF (ASC)
kentaro.komori - 1:50 Friday 06 February 2026 (36299) Print this report
First trial of high bandwidth control of DHARD Yaw

[Tanaka, Dan, Ushiba, Komori]

Abstract:

We attempted to implement a new filter to achieve high-bandwidth control of DHARD yaw, but have not succeeded yet.
As the next step, we will pursue a more moderate-bandwidth control scheme.

Details:

We began implementing a new filter to control DHARD yaw with a higher unity gain frequency (UGF).
This approach is expected to significantly reduce fluctuations in the arm transmission, which currently seem to be limited by TM yaw motion.

Based on the measured transfer function from DHARD yaw to the TM oplev signal (klog:36289), we designed a new filter consisting of ten zero–pole phase compensation stages.
The figure shows the estimated open-loop transfer function, with the UGF set to 4 Hz.

When we enabled DHARD yaw control using this new filter, an oscillation around 20 Hz occurred immediately, leading to lock loss.
To suppress this oscillation, we had to reduce the gain by a factor of approximately 3e3.
However, with such a low gain, the control was insufficient to drive the error signal to zero, even for a long period.
In addition, another oscillation appeared at approximately 80 mHz at this reduced gain, which also resulted in lock loss.

One possible cause of the high-frequency oscillation is coupling from other degrees of freedom.
The ten zero–pole phase compensation stages significantly amplify signals at high frequencies, which likely enhances such couplings.
Therefore, our next plan is to implement a moderate-bandwidth control scheme.
The target UGF will be between the second and third yaw resonances, approximately 2.5 Hz.

Images attached to this report
VIS (General)
takafumi.ushiba - 22:32 Thursday 05 February 2026 (36298) Print this report
Comment to TF measurements for Type-Bp noise budget (36287)

I restarted the automeasurement scripts on the remote desktop session of k1ctr5.
I hope the script will finish by tomorrow morning but ​​​​​if someone would like to stop the script, please send the command Ctrl+C on the terminal opened on the remote session of k1ctr5.

MIF (General)
shoichi.oshino - 22:07 Thursday 05 February 2026 (36297) Print this report
Finesse reanalysis
I reanalyzed the finesse of the X-arm and Y-arm.
Measurements from June 2022 to 2024 were only reanalyzed if the log contained 10 measurements.
Since recent finesse measurements are performed with 5 measurements, measurements from 2025 onwards were only reanalyzed if the log contained 5 or more measurements.
The fitting function includes an offset.
The GPS time recorded in the file is the time converted from the directory name. This corresponds to the start time of the measurement.
On the other hand, the GPS time recorded in previous files is the last measurement time. Therefore, there may be a difference of several tens of minutes between the GPS times.
Non-image files attached to this report
CRY (General)
nobuhiro.kimura - 19:50 Thursday 05 February 2026 (36296) Print this report
Comment to Maintenance Notes for Duct Shield Cryo-cooler Units (36285)

[Kimura and Yasui]
 On February 5, the helium gas inside the cold heads of the duct shield cryo-cooler unit were replaced.
The cold heads whose helium gas was replaced were and Yfa (arm side of the IYC) and Xfa (arm side of the IXC)
Yfa worked from 10:30 AM to 11:40 AM, and Xfa worked from 1:30 PM to 3:30 PM.
The pressure of the helium gas in the cold heads is 15 bar. 
The grade of helium gas used was G1.

MIF (ASC)
dan.chen - 15:50 Thursday 05 February 2026 (36295) Print this report
Continuation of high-bandwidth ASC work: CHARD_P / DHARD_P

[Tanaka, Komori, Dan]

1. CHARD_P

At first, We worked with only the CHARD_P loop mainly engaged, while the other P DoFs were kept weakly locked.

  • The CHARD_P filter was created by copying from the DHARD_P filter and modified a little.
  • The OLTF was measured and compared with previous results.

OLTF file: /users/Commissioning/data/ASC/2026/0205/OLTF_CHARD_P_20260205.xml

  • Brown: updated (measured in the morning)
  • Blue: yesterday’s result
  • Green: before notch tuning
  • Purple: remeasured CHARD_P OLTF

The purple measurement was performed in the RF_LOCKED state, where all other DoF loops were also closed. A large response was observed in DHARD_P signals, suggesting that residual coupling remains from CHARD_P to DHARD_P.

Result: See OLTF_CHARD_P.png (fig001).

2. DHARD_P

Previously, the DHARD_P gain was set to −3 externally. In this work, the gain was incorporated into the filter bank FM6 = HBtest.
After this change, an oscillation appeared around 2 Hz. Therefore, the gain was temporarily reduced from gain(3) to gain(2).

Compared with yesterday’s results, a larger bump around 10 Hz was observed. After repeating the measurements several times, this bump seemed to occur when the alignment was poor. In particular, the bump around 10 Hz was prominent in measurements taken when the transmitted power was low. 

OLTF measurements were performed with and without the DHARD_P FM2 (notch filter). After that, the IFO was brought to the RF_LOCKED state, and the same measurements were repeated.

Measurement file: OLTF_DHARD_P_20260205.xml

Result: See OLTF_DHARD_P.png(fig002).

3. ASC GRD update

Based on the above results, the ASC GRD was updated.

  • The appropriate filters for DHARD_P and CHARD_P are now automatically engaged.

Filters to be engaged for DHARD_P and CHARD_P:

  • ASC_filter_after_GRD_change.png (fig003)
  • DC_HARD_P_FB.png (fig004)

VIS MN LOCK filter configuration:

The FM4 = HBtest filter (marked by blue circles in the figure) is now turned ON via GRD instead of the conventional FM9 and FM10.

See VIS_MN_LOCK_FB.png (fig005).

Images attached to this report
MIF (General)
yuta.michimura - 13:56 Thursday 05 February 2026 (36294) Print this report
Comment to PRX and PRY power recycling measurements (36242)

To derive power recycling cavity length in klog #36249, I used the finesse of PRX/PRY to be 2.00(3), which is a theoretical value with measured BS T and R, without losses.
In reality, from carrier PRG measurements PRX had ~10% loss and PRX had ~15% loss.
Also, sideband PRG for PRFPMI sugested ~13% loss in PRC.
If we add optical loss of 13(5)% loss, PRX/PRY finesse will be 1.89(4).
This slightly changes the linewidth I used to calibrate the PRC length (the effect is negligible compared with other uncertainties).
Updated values will be

Estimated f2 detuning of PRC    0.071+/-0.004 MHz
Sideband PRG for PRX    0.0797+/-0.0031
Sideband PRG for PRY    0.0654+/-0.0026
Average PRC length      66.523+/-0.006 m

So the measured PRCL is shorter from the design (66.591 m) by 6.8(6) cm.
If we are to keep the current f2 modulation frequency (44.9946924104 MHz), PRCL needs to be shortened by 10.5(6) cm.

Using these values, the calibration factor for POP90 sqrt(I^2+Q^2)/Pin will be 6.16(18).
This gives the following (see attached).

Sideband PRG for PRFPMI 7.97+/-0.23
Sideband losses in PRC for PRFPMI 12.43+/-0.33 %

Note that this loss includes the effect from f2 detuning.
Carrier losses in PRC for PRFPMI should be estimated independently from carrier PRG (to be done next).

Images attached to this comment
VIS (BS)
takaaki.yokozawa - 11:24 Thursday 05 February 2026 (36292) Print this report
Comment to TF measurement result for BS local control noise budget (36291)
I performed the noise projection manually (10 - 100 Hz).
Images attached to this comment
VIS (BS)
takafumi.ushiba - 10:43 Thursday 05 February 2026 (36291) Print this report
TF measurement result for BS local control noise budget

I checked the measured TF of BS for the noise budget.
Following local controls have a large coherence to DARM, so precise projection should be performed.
The other TF have low coherence, so the noise contribution to the current DARM should be small.

TM_OLDAMP_P: fig1
TM_OLDAMP_Y: fig2

Images attached to this report
Comments to this report:
takaaki.yokozawa - 11:24 Thursday 05 February 2026 (36292) Print this report
I performed the noise projection manually (10 - 100 Hz).
Images attached to this comment
MIF (General)
takaaki.yokozawa - 9:25 Thursday 05 February 2026 (36290) Print this report
PEM injection test 260205
I performed the PEM injection test

- 7:19 silent run

1. Large vibration injection
To evaluate how large vibration can be performed in OMC area, I turned off the BPC controls and inject the signal
Excitation : K1:PEM-EXCITATION_SR3_RACK_7_EXC
Reference PEM : K1:PEM-ACC_OMC_CHAMBER_OMCLEG_Z_OUT_DQ
02/05 07:27 - 07:47
Sweep the 900 - 1 Hz, 600 s, 100 cnt, 2 times injection
Fig.1. showed the whitened spectrogram.
During this measurement, no locked loss detected. so it would be the large vibration for each frequency.

2. For the evaluation of the noise projection from OMC bellows leg
02/05 08:26 - 09:23(?) Locked loss happened around 09:23 due to the earthquake, stopped the injection around 130 Hz
Swept sine 400 - 50 Hz, 1 Hz resolution, 10 s in each frequency, 10 cnt
Before this injection, I performed the 100 cnt injection, but it seemed too large vibration, the DARM sensitivity always bad, so I reduced the injection amplitude (100->10 cnt)
Even the 10 count injection, the amplitude is more than 10 times larger than background (8 s FFT)
(10 cnt would be something small below 200 Hz, so we will perform to apply the envelope with checking the amplitude tomorrow)
Images attached to this report
MIF (ASC)
kentaro.komori - 3:34 Thursday 05 February 2026 (36289) Print this report
Transfer function measurement from MN to TM in Yaw

[Tanaka, Komori]

We measured the transfer function from the MN to the TM in the yaw degree of freedom as the first step toward achieving higher-UGF yaw control.

We paid careful attention to reproducing conditions as close as possible to the interferometer locked state; for example, the OLDAMP yaw control on the MNs was turned off.
In addition, we turned off the TM lock filters, since our initial approach is to control yaw using feedback applied only to the MNs.

The measured transfer functions for each suspension are shown in the figure.
The results are consistent with expectations for a triple-pendulum system.

Images attached to this report
MIF (ASC)
kentaro.komori - 3:23 Thursday 05 February 2026 (36288) Print this report
Decoupling {D, C}SOFT from HARD in Pitch

[Tanaka, Komori]

Abstract:

We successfully decoupled the pitch {D, C}SOFT modes from the HARD mode by adjusting the sensing matrix of the arm transmission QPDs.

Details:

After tuning the output matrix of the arm WFS signals based on the calibrated TM oplev signals, the next step was to decouple the {D, C}SOFT and CHARD modes from DHARD.
To measure the couplings, we injected a 50-mHz sine wave into the DHARD output while keeping the arm WFS control engaged with the conventional filter.
The excitation frequency was chosen to be 50 mHz in order to avoid feedback to the TMs, which is enabled in the conventional filter, and to isolate the response of the MNs.

The initial result is shown in Fig. 1.
From the beginning, we did not observe a clear 50-mHz peak in the CHARD signal.
This suggests that the TM oplev calibration is still accurate and that DHARD and CHARD are already decoupled at the level of an order of magnitude.
In contrast, clear peaks were observed in the DSOFT and CSOFT signals.
We therefore decoupled these modes from the DHARD excitation by tuning the sensing matrix of the arm transmission QPDs, which serve as the sensors for the SOFT modes.

Figures 2-4 show a comparison of the four arm signals during excitations of DHARD, CSOFT, and DSOFT, using the previous (labeled as “REF” in the figures) and the updated sensing matrix.
After the adjustment, the peak amplitudes in the DSOFT and CSOFT signals during DHARD excitation were significantly reduced, while sufficient responses remained in each degree of freedom when the corresponding excitation was added.
The updated sensing matrix is shown in Fig. 5.

Images attached to this report
MIF (ASC)
kenta.tanaka - 0:10 Thursday 05 February 2026 (36286) Print this report
{D, C}{HARD, SOFT} P OLTF measurements

Komori, Tanaka (remote)

As reported by Komori-san in klog, we decoupled HARD/SOFT modes in terms of SOFT sensors. After decoupling, we measured OLTFs of {D, C}SOFT modes. This time, we set the {D,C}SOFT_P_GAIN to -3. And, BPCs were engaged to controll their modes in their DC regions. Also, other ASCs were used not new filters but previous filters.

Fig. 1 and Fig. 2 show the results. The UGF of the CSOFT_P control seems to be 30 mHz and the gain shape becomes flat below 30 mHz. This time, the UGF of the DSOFT_P seems to be not measured with enough coherence but it seems to be similar with the one of CSOFT mode.

After then, we engaged DHARD_P controls with new filters. Then we measured the OLTF of the DHARD_P control. fig. 3 shows the results. The green line shows the OLTF before decoupling and the brown lines is after the decoupling. As you can see, the peak height around 10 Hz become smaller.  

However, we reminded that CHARD_P control with new filter was engaged when the green lines was measured. On the other hands, in this time, CHARD_P control was engaged with previous filters. So we suspected that the peak around 10 Hz came from the new CHARD_P control. In order to confirm this, we engaged the new CHARD_P controls and remeasured the OLTF of  DHARD_P. Red lines in fig. 3 shows the results. the peak height around 10 Hz is still smaller even though the new CHARD_P control was engaged. That is, the decoupling b.t.w SOFT and HARD makes the peak height become smaller.

Then, we measured the OLTF of CHARD_P. The UGF seems to be around 2 Hz but the phase margin at UGF seems to lower than 20 degrees! So it is necessary to improve the margin by modifying the filter design.

Images attached to this report
VIS (General)
takafumi.ushiba - 23:55 Wednesday 04 February 2026 (36287) Print this report
TF measurements for Type-Bp noise budget

I tuned the template files and ran the automeasurement script on the remote desktop session of k1ctr5.
If someone would like to stop the script, please send the command Ctrl+C on the terminal opened on the remote session of k1ctr5.

Comments to this report:
takafumi.ushiba - 22:32 Thursday 05 February 2026 (36298) Print this report

I restarted the automeasurement scripts on the remote desktop session of k1ctr5.
I hope the script will finish by tomorrow morning but ​​​​​if someone would like to stop the script, please send the command Ctrl+C on the terminal opened on the remote session of k1ctr5.

DGS (General)
takahiro.yamamoto - 21:59 Wednesday 04 February 2026 (36284) Print this report
upgrade of k1cam0
After all cameras on k1cam0 had been moved to k1cam2 (klog#36217), k1cam0 was no longer used.
So I applied a same upgrade to k1cam0 as k1cam2 though the hardware is still an old V0 server.
After then, all cameras on k1cam1 except OMC_TRANS were moved to k1cam0.
Remaining OMC_TRANS will be migrated to the new pylon-camera-server with the update of OMC_LSC guardian (see also klog#36226).

-----
At first, I tried to make a new boot disk of k1cam0 as the copy of the master disk. But the old V0 server doesn't support UEFI though the master disk was generated as the UEFI boot. So I newly installed OS as the legacy BIOS mode. After purchasing new server hardware, it may be better to re-install as UEFI mode. (Default mode of recent hardware is UEFI mode and installing as BIOS mode to such hardware is sometimes troublesome.) Installation procedure can be found as JGW-T2516613 and it takes ~40min. So re-installation can be done within the half day in the weekly maintenance.

After the OS installation, I moved cameras on k1cam1 which is still running as the old camera-server to k1cam0. Then I noticed that POP and POP_P images were swapped. So I checked information on Wiki, S-number on JGWDoc and old/new camera configurations carefully, and then I found a mistake in the management of the serial number of camera devices. The old camera-server accesses each camera by using IP address. On the other hand, the new pylon-camera-server accesses by using an inquiry of serial number with the broadcast packets. So it wasn't a serious problem on the old camera-server in the past. Anyway, the serial number of camera devices for POP and POP_P had been swapped on Wiki and JGWDoc and these wrong information were revised in this time.

Now only OMC_TRANS camera is still running on the old k1cam1 because of the compatibility issue with the OMC_LSC guardian. So I planned to migrate it with the modification of OMC_LSC guardian in the next maintenance day. After then, we can remove k1cam1 (and rename k1cam2 as k1cam1 if necessary). We also need to replace the computer hardware for k1cam0, but it's a task containing a purchase in the next fiscal year.
Search Help
×

Warning

×