Reports of 34100
MIF (General)
takaaki.yokozawa - 9:50 Wednesday 15 April 2026 (36749) Print this report
Comment to Initial alignment and TCam photo session (36748)
Yuzurihara-san commented that https://klog.icrr.u-tokyo.ac.jp/osl/?r=31281.
And I and Ikeda-san fixed it.
Now both IY and EX camera can take photo with color scale
MIF (General)
takaaki.yokozawa - 9:01 Wednesday 15 April 2026 (36748) Print this report
Initial alignment and TCam photo session
I performed the initial alignment Xarm and Yarm.
To find the GRY flash, I moved SR3 a lot
P : -30 -> 15
Y : 60 -> 30

After that, I performed the TCam photo session.
I don't know the reason, but the IY and EX TCam image was gray scale.
Comments to this report:
takaaki.yokozawa - 9:50 Wednesday 15 April 2026 (36749) Print this report
Yuzurihara-san commented that https://klog.icrr.u-tokyo.ac.jp/osl/?r=31281.
And I and Ikeda-san fixed it.
Now both IY and EX camera can take photo with color scale
DGS (General)
takahiro.yamamoto - 2:29 Wednesday 15 April 2026 (36747) Print this report
Comment to Migrating scripts from k1script1 to k1script0. (36519)
Migration of all on-demand scripts were completed to k1script0.
Now, we can stop k1script1 which is old server.
OS upgrade of k1script1 will be done tomorrow.

All systems and services are now summarized on JGW Wiki.

Please keep this page up to date whenever you add a new service or system.
This will reduce the effort required for future server updates.
In fact, with this update, identifying services for which we had no information was more challenging than ensuring compatibility with the new OS.

-----
Traverser script
I had already confirmed that traverser script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/traverser/traverser_start.py) was worked well on the new server. But server connection and environmental variables were hard-coded on shell command block of MEDM screen files. So migration required to modify several MEDM screens. So I prepared a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/traverser/medm_traverser_start.sh) in which necessary information is set. Thanks to this implementation, we won't need to find related MEDM screens and to update them in future OS upgrade.

Rebooter script
In Python3.13, telnetlib which is used in the rebooter script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/picomotor/pico_power_control.py) is completely deprecated. So I rewrote a function derived from telnetlib as one derived from socket package. Due to differences in escape sequences and control codes, it has been modified quite a bit. And also, a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/picomotor/medm_pico_power_control.sh) is also prepared to avoid hard-coding of various parameters on MEDM screens. I needed to modify hundreds of shell command blocks to migrate from k1script1 to k1script0 in this time. Identifying and fixing related MEDMs was the most tough task of the migration work of script server.

HWP script
I had prepared an HWP script to avoid hard-coding in the previous version, but I realized that it was difficult to avoid hard-coding due to bad implementation of the callback function. (And while it probably hasn’t caused any practical problems yet, the sudores configuration on the RaspPi is likely set up incorrectly.) So, I rewrote the hard-coded `k1script1` to `k1script0`. To eliminate hard-coding entirely, HWP script must be redesigned drastically.

Phytron script
Though I couldn't find any information about Phytron script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/phytron/phytron_start.py), I happened to discover that this script was running on k1script1. Implementation of this script is quite similar to traverser script. So I prepared a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/phytron/medm_phytron_start.sh) to avoid hard-coding on the shell command block of MEDM screens.
MIF (General)
shun.saito - 21:36 Tuesday 14 April 2026 (36746) Print this report
Construction of the optical layout for PRCL and SRCL measurements

[Tanaka,Saito]

Based on the optical layout plan in klog:36739, we installed a newly purchased FI, a beam sampler, and mirrors. The transmission of the FI reached approximately 85%.

  • We replaced the contaminated FI reported in klog:36739 with a newly purchased one (Photo 1). This FI has an aperture of 3 mm. Since the laser beam radius at the planned position in the optical layout is about 1.2 mm, we placed the HWP, PBS, and mirrors upstream of the FI as close together as possible, reducing the beam radius at the FI position to approximately 0.8 mm. After alignment, the input power was about 154 mW and the output power was about 131 mW, corresponding to a transmission of approximately 85%. A beam sampler with a reflection-to-transmission ratio of 9:1 was installed after the FI. Six mirrors were placed on the reflection side of the beam sampler.

Unfortunately, since the right-side wall shown in Photo 1 cannot be removed, it is difficult to install an additional mirror and perform alignment.

Images attached to this report
VIS (SRM)
ryutaro.takahashi - 17:28 Tuesday 14 April 2026 (36745) Print this report
Performance of Geophones and FLDACCs

I checked the geophone performance by FLDACC status. Plot 1 shows the spectra of the geophones in the SAFE state, where the FLDACCs were not locked but were free-running under DC actuation to the proof mass. Plot 2 shows the spectra of the geophones in the READY state, where the FLDACCs were locked in ~20Hz UGF. In this case, the geophone spectra have been smeared by the FLDACC's activity.

Images attached to this report
CRY (General)
nobuhiro.kimura - 16:16 Tuesday 14 April 2026 (36744) Print this report
Comment to Maintenance Work on the Duct-Shield Cryo-coolers for IXC and IYC was Completed (36605)

[Kimura, Yasui and M. Takahashi]

 The duct shield cryocoolers (Yea, Yer) and the cooling water circulation system at Y-end were shut down at 9:00 a.m. to perform repairs on the Y-end feedwater pump.
Since the repairs on the feedwater pump were completed, the duct shield cryocoolers (Yea, Yer) and the cooling water circulation system were restarted at 1:30 p.m.

While the cooling water circulation system was shut down, the SLACK alarm was temporarily disabled.

VIS (SRM)
ryutaro.takahashi - 15:20 Tuesday 14 April 2026 (36743) Print this report
Suspension monitoring during evacuation

I monitored the suspension during the evacuation, which started at 13:10. The suspension state was SAFE. The valve opening looks very small until 13:25. About one hour later, the IP drifted by ~1mm (Pic. 1) and the BF GAS drifted by ~0.15mm (Pic. 2). I changed the suspension state to ISOLATED at 14:25. The pressure was 6x10^3 Pa. The DC feedback signals to lock the FLDACCs were almost the same as the previous: 12100 for H1, 11500 for H2, and -5200 for H3. I offloaded the IP H1 and H2 with the FRs.

Images attached to this report
DGS (General)
takahiro.yamamoto - 22:23 Monday 13 April 2026 (36742) Print this report
Taking system backup of k1script0
Though a migration of some on-demand scripts still remained, all resident systems and services were migrated to k1script1 to k1script0 (see klog#36519).
So a current system backup of k1script0 was taken with shutting down it.
For this work, all resident systems and services on k1script0 was stopped during this morning.

-----
Disk related error?
When I tried to stop k1script0, a SATA error appeared on the console and the system wouldn’t respond to keyboard input. However, because I was able to log in via SSH without any issues, I decided to try rebooting it once before shutting it down, and then it could be launched without any issues. So I shut down it to take a system backup as an original plan. A backup process had also no issue and a cold boot after taking backup was also fine.

I haven't been able to reproduce a SATA error yet. It seems better to keep an eye on this matter for a while. If this issue occurs on HDD side, backup disks taken today should help to recover. If it occurs on the motherboard side, replacement of server chassis might be required (it's now running V0 server).

How is a relation to Ondotori DAQ?
I'm not sure this issue is a direct cause of a suspended DAQ in klog#36733, but after rebooting, DAQ record seems to work well again. If it will be reproduced with or without a SATA error, a cause of DAQ issue can be investigated more detailed. (I noticed Yokozawa-san's report after my work in this time, so I couldn't any investigation at all today.)

Appearing "-100.0" is a feature of Ondotori system. It was implemented by Sasaki-kun to inform the communication error between the parent and the child devices. In most cases, it's related to too weak signal on child devices. When a function to record a battery and RSSI information was added on Sasaki-kun's script, this feature hadn't worked well due to a bug injection. Then, this function came back when Ondotori script was rewritten in Python (klog#36668) because I hadn't noticed this bug at that time yet.

If you prefer the previous behavior (where communication errors were not treated as -100), I can modify the Python script. On the other hand, the communication errors occurred on Ondotori@EXA in recent 1 year, but nobody noticed that fact because past values that looked plausible were still being remained on EPICS records. (I wonder Temperature@EXA should be one of important environmental information for the integrating sphere calibration...) So some kind of information to notice an communication errors even if we will revert a behavior of Ondotori script as previous one.
VAC (General)
takahiro.yamamoto - 20:32 Monday 13 April 2026 (36740) Print this report
Comment to Vacuum system migration for SRMGV/OMMTGV (36416)

This is a retry of klog#36416 which hadn't been completed.

For the hardware replacement of CC-10 readout for SRMGV and OMMTGV from RaspPi to MOXA (klog#36737), I stopped vacuum DAQ and resumed it with a new channel list. All migration works on DGS (disabled to access RaspPi@AS which is no longer used, updated MEDM screens, update a watch list by vacuum guardian, and updated a channel list of KAGRA DAQ) was completed. At the end of this work, daqd was restarted.

I heard from Nakagaki-san that some hardware settings still remain. Because of this, new values haven't been written in some channels used for an alert by guardian by the new MOXA system though they exist. So an alert about pressure values at SRMGV and OMMTGV, and status of gate valve at OMMT are still disabled as shown in Fig.1 due to avoid annoying and meaningless alerts. They should be automatically enabled when pressure values will become smaller than threshold and gate valve will be opened.

Images attached to this comment
VIS (SRM)
ryutaro.takahashi - 20:20 Monday 13 April 2026 (36741) Print this report
Comment to Health check (36669)

I checked the TM transfer functions after closing the chamber. They were consistent with the references.

Images attached to this comment
MIF (General)
shun.saito - 19:26 Monday 13 April 2026 (36739) Print this report
Revised optical layout plan for PRCL and SRCL measurements and investigation of the FI

[Tanaka,Saito]

To resolve the issue of an excessively large beam size identified in klog:36731, we recalculated the positions of two lenses for mode matching.
The large loss in the FI reported in klog:36731 was caused by misalignment of the output polarization and contamination inside the FI.
 

  • To resolve the issue of an excessively large beam size identified in klog:36731, we recalculated the positions of two lenses for mode matching (Fig. 1). The origin is defined as the point where the laser is emitted. The orange line represents the beam profile of the laser, the green line represents the beam profile after passing through the first lens, the red line represents the beam profile after passing through the second lens, and the blue line represents the target beam profile of the IR laser on the POS optical table.

    The focal lengths and positions of the two lenses are as follows:

    Lens 1: focal length = 200 mm, position = 2794 mm
    Lens 2: focal length = 150 mm, position = 3190 mm

    The beam size at these lens positions is acceptable when using 2-inch lenses. Based on the calculated lens positions, we redesigned the optical layout for PRCL and SRCL measurements (Fig. 2).
     

  • Although the FI exhibited large losses in klog:36731, aligning the output polarization improved the transmitted power: the input power was approximately 27 mW, while the output power increased to about 20 mW, corresponding to a transmission of 74%. However, since no further improvement was observed, we inspected the interior of the FI by illumination and found contamination (Photo 1). Therefore, we decided to use a newly purchased FI instead.

Images attached to this report
VIS (SRM)
ryutaro.takahashi - 18:15 Monday 13 April 2026 (36738) Print this report
Comment to Health check (36669)
Images attached to this comment
VAC (SRM)
koji.nakagaki - 17:55 Monday 13 April 2026 (36737) Print this report
Comment to Preparation for GV-ommt Interlock Device Installation (35898)

[YamaT, Kimura, Yasui, TakahashiM, SawadaH, Nakagaki]

We switched the remote monitoring system for the two CC-10 vacuum gauges (PV names K1:VAC-PRESSURE-CS-SRMGV and K1:VAC-PRESSURE-CS-OMMTGV) that will be used by the GV auto-closure device from Raspberry Pi to MOXA.

VIS (SRM)
ryutaro.takahashi - 17:41 Monday 13 April 2026 (36736) Print this report
Comment to Health check (36669)

I checked the GAS transfer functions after closing the chamber. They were consistent with the references.

Images attached to this comment
VIS (SRM)
ryutaro.takahashi - 17:29 Monday 13 April 2026 (36735) Print this report
Comment to Health check (36669)

I checked the IP transfer functions after closing the chamber.  The resonant frequencies of the IP were increased from 63 to 66 mHz for L, from 70 to 74 mHz for T, and from 0.32 to 0.33 Hz for Y, respectively. Diagonization should be retuned.

Images attached to this comment
DGS (General)
shoichi.oshino - 14:26 Monday 13 April 2026 (36734) Print this report
Backup server maintenance
I updated the operating system on the backup server. This was a minor version update.
The major version used on k1bck0 is nearing its end-of-life, so a major version upgrade will be necessary soon.
PEM (Center)
takaaki.yokozawa - 9:44 Monday 13 April 2026 (36733) Print this report
All temperature monitor system stopped
I noticed that the temperature monitor system (ondotori) stopped recording since the 3rd Apr. 13:20(JST)
Only once, the value changed in 6th Apr. 14:09(JST).

And BOOTH PSL temperature sometimes -100 deg.
It started 30th Mar. 13:16(JST)
Images attached to this report
CAL (YPcal)
dan.chen - 9:42 Monday 13 April 2026 (36732) Print this report
Turn ON Pcal-Y

I turned ON the laser of Pcal-Y and requested the Pcal-Y guardian to be low power state, which was turned OFF duo to the DGS maintenance last weeks.

MIF (General)
shun.saito - 21:03 Saturday 11 April 2026 (36731) Print this report
Installation of the sub-laser and optical components for PRCL and SRCL measurements

[Tanaka,Hirose,Saito]

In accordance with the optical layout plan in klog:36730, we installed the sub-laser, HWP, PBS, and FI.
We found that the beam size at the position of the second lens was too large, so we decided to reconsider the optical layout.
 

  • Following the optical layout plan in klog:36730, we installed the sub-laser, HWP, PBS, and FI (Photo 1). From right to left in Photo 1, these are the sub-laser, HWP, PBS, HWP, and FI. Using the first HWP and PBS, we constructed the optical layout with reduced laser power. The laser power will be increased during the measurements of PRCL and SRCL. Although the HWP placed in front of the FI was not included in the original optical layout plan, it was installed to match the polarization to the FI. The FI was adjusted to maximize the transmitted power; however, the power decreased significantly from approximately 27 mW before the FI to approximately 1.8 mW after the FI. Since we had not confirmed whether the laser beam was properly aligned before placing the optical components, we plan to check the beam alignment.
     
  • In the calculation of the positions of the two lenses for mode matching in klog:36730, the beam radius at the position of the second lens was found to be 10.7 mm, indicating that the beam size is too large for a 1-inch (25.4 mm) lens. Therefore, we plan to recalculate the positions of the two lenses for mode matching.
Images attached to this report
MIF (General)
shun.saito - 2:23 Friday 10 April 2026 (36730) Print this report
Calculation for mode matching on the POS optical table and optical layout plan for PRCL and SRCL measurements

[Tanaka,Hirose,Saito]

Abstract:

We fitted the beam profile of the IR laser on the POS optical table measured in klog: 36724. The waist position was found to be 259 mm, and the waist size was 0.054 mm. Based on these results and the fitted beam profile of the sub-laser, we calculated the positions of two lenses required for mode matching. Furthermore, we developed an optical layout plan for the measurements of PRCL and SRCL.

Detail:

First, we fitted the beam profile of the IR laser on the POS optical table measured in klog: 36724 (Fig.1). The points represent the measurement results, and the lines represent the fitting results. The green and orange points were used for the fitting, while the blue and red points were excluded because their behavior differed from the other measurement points.

The measurement points around 300 mm deviate significantly from the fitting curve because, as shown in Photo 2 of klog: 36724, the beam split into two, and both spots were simultaneously fitted with a Gaussian. The apparently reasonable behavior around 350 mm is because only one of the split beams was successfully fitted with a Gaussian. However, since the beam was distorted as shown in Photo 3 of klog:36724, it should have been compared with the beam between 100 mm and 250 mm to determine whether to include it in the fitting; unfortunately, no photos were taken in that range. In addition, when the mesurement points around 350 mm are included in the fitting (Fig.2), the mesurement points between 100 mm and 250 mm deviate from the fitting curve compared to Fig.1. Therefore, we decided to use the results from Fig.1 to determine the positions of the two lenses for mode matching. (For the measurements of PRCL and SRCL, it is sufficient to observe the resonance of the TEM00 mode, so a slight mismatch in mode matching is considered acceptable.)

The waist position and waist size obtained from the fitting in Fig.1 are as follows:

Major : waist position = 264.3 ± 5.1 mm, waist size = 0.0526 ± 0.0025 mm
Minor : waist position = 253.6 ± 2.3 mm, waist size = 0.0555 ± 0.0013 mm
→ Average: waist position = 259 mm, waist size = 0.054 mm

The laser to be newly installed on the POS optical table must be mode-matched to this waist position and size. Therefore, its beam profile was measured in advance in Kashiwa and fitted (Fig.3). The origin is defined as the point where the laser is emitted.

The waist position and waist size obtained from the fitting in Fig.3 are as follows:

Major : waist position = −118.8 ± 1.9 mm, waist size = 0.1469 ± 0.0008 mm
Minor : waist position = −127.8 ± 1.8 mm, waist size = 0.1562 ± 0.0008 mm
→ Average: waist position = −123 mm, waist size = 0.1516 mm

Next, based on these waist positions and waist sizes, we determined the positions of two lenses for mode matching (Fig.4). The origin is defined as the point where the laser is emitted. The orange line represents the beam profile of the laser, the green line represents the beam profile after passing through the first lens, the red line represents the beam profile after passing through the second lens, and the blue line represents the target beam profile of the infrared laser on the POS optical table. 

The focal lengths and positions of the two lenses are as follows:

Lens 1: focal length = 200 mm, position = 1426 mm
Lens 2: focal length = 500 mm, position = 2363 mm

Finally, based on the calculated lens positions, we designed an optical layout for a phase-locked loop (PLL) used in the measurements of PRCL and SRCL (Fig.5). The right-hand side of Fig.5 corresponds to the optical system designed in this work.

Images attached to this report
VIS (SRM)
ryutaro.takahashi - 13:40 Thursday 09 April 2026 (36728) Print this report
Comment to Adjustment of suspension (36711)

[Washimi, Takahashi]

We replaced the satellite box for the IM H OSEMs. The previous box is  S1604901 (Pic. 1 and 2). The new box is  S1807635 (Pic. 3 and 4). The OSEM outputs were changed as follows (Pic. 5). The transfer functions for H2 (Pic. 7), H3 (Pic. 8), and Y (Pic. 10) were the same as the previous measurements. The DC gain of the transfer functions for H1 (Pic. 6) and L (Pic. 9) was increased by 5dB. The H1 OFFSET in "K1 SRM IM OSEMINF FILTERS" was returned from -3700 to -6315.5.

  Previous New
H1 2790 3760
H2 5900 5940
H3 8380 8420

 

Images attached to this comment
VIS (SRM)
ryutaro.takahashi - 13:16 Thursday 09 April 2026 (36729) Print this report
Comment to Health check (36669)

I added the F0 transfer function measured with a modified template.

Images attached to this comment
VIS (SRM)
takaaki.yokozawa - 8:31 Thursday 09 April 2026 (36727) Print this report
Incident angle of the SRM oplev
According of the JGWDoc7268, the incident angle of SRM oplev is 37 deg.

Images attached to this report
DGS (General)
takahiro.yamamoto - 3:11 Thursday 09 April 2026 (36726) Print this report
Comment to Migrating scripts from k1script1 to k1script0. (36519)
I started to migrate on-demand scripts.

Pico, Stepper, and temperature control scripts were migrated from k1script1 to k1script0.

Though traverser script was worked also on k1script0, it's launched from MEDM screen with hard-coded server name. So all MEDM screens must be also updated. Because it's so hard to do remotely, I'll do it next week.

Rebooter script doesn't work on k1script0 because it depends on the telnetlib package which was obsoleted from Python3.13 whic h is one of the system packge of Debian13. So I replaced a function defined in the telnetlib package as a function defined by the socket packages. I haven't tested this new code with connecting rebooter devices yet. It will also be done in next week. In addition, MEDM screens for rebooter on which the server information is hard-coded must be also updated.

HWP script also has a server connection settings with hard-coded manner. So it must be rewritten as the new script server information. Rewritten code was already prepared and will be tested next week.

Once these tests are complete, we plan to proceed with the actual deployment. These are remaining tasks of the migration work for k1script.
VIS (SRM)
ryutaro.takahashi - 0:33 Thursday 09 April 2026 (36725) Print this report
Comment to Health check (36669)

I checked the transfer functions of F1, BF, IM, and TM. The states during the measurement were READY for F1 and BF, TWR_FLOAT for IM and TM. The diaggui for F0 did not work. 

Images attached to this comment
Search Help
×

Warning

×