Reports of 34756
DMG (General)
nobuyuki.kanda - 16:48 Tuesday 08 September 2026 (37470) Print this report
DMG router replacement at Hokubu-kaikan
DMG's old router Fujitsu IPCOM at Hokubu-kankan is replaced by new touter YAMAHA RTX1300 today.
According to this replacement, below are changed:

- Traffic capacity is now enlarged. While data transmission under steady-state conditions has always been fine, this new system offers more headroom even when sending large bursts of data after transmission interruptions due to network outages or other issues.

- Maintenance has become easier than before.

- The lifespan of the equipment has been extended.

- VPN connection to DMG network at Kamioka is closed.

- We can access DMG servers, i.e. frontend server in KAGRA tunnel (hyades-#), iKAGRA login server (taurus-#) via new router with ssh via specified port. But the access is limited from inside of ICRR network. Since the access to these servers are very limited users, detail of the access will be shared during DMG subgroup inside.

Nothing is changed for data transfers, i.e. bulk data derived from DGS and low latency from CAL to Kashiwa.
Now (9/8 16:00) all data transfer from Kamioka is resumed.
AOS (Cameras)
takahiro.yamamoto - 12:39 Tuesday 08 September 2026 (37469) Print this report
Comment to POS camera seems dead (37464)
The POS camera resumed operation briefly around 1:30 JST but stopped working again around 11:15 JST.
Even though there was no activity around the POS table, the situation appears to have changed.

Since the camera unit itself has never malfunctioned before, we should first try replacing the LAN cable.

Attached figure and text file shows a down time of POS camera.
Images attached to this comment
Non-image files attached to this comment
DetChar (General)
takahiro.yamamoto - 9:35 Tuesday 08 September 2026 (37468) Print this report
Segment generation failed because cache generation was put on hold
As the title says.

I released the held job and resumed cache generation.
After then, segment generation was also resumed.

$ condor_q
-- Schedd: kmst2-01 : <192.168.120.15:9618?... @ 09/08/26 09:22:45
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
1928928.0 detchar 7/22 19:44 0+00:00:01 H 0 10.0 makeCache.sh -c Kashiwa -t full 0

$ condor_q -hold 1928928.0
-- Schedd: kmst2-01 : <192.168.120.15:9618?... @ 09/08/26 09:23:39
ID OWNER HELD_SINCE HOLD_REASON
1928928.0 detchar 9/8 07:00 Job missed deferred execution time

Total for query: 1 jobs; 0 completed, 0 removed, 0 idle, 0 running, 1 held, 0 suspended
Total for all users: 29 jobs; 0 completed, 4 removed, 1 idle, 21 running, 3 held, 0 suspended

$ condor_q -l 1928928.0 | grep -E 'HoldReason|HoldReasonCode|HoldReasonSubCode'
HoldReason = "Job missed deferred execution time"
HoldReasonCode = 20
LastHoldReason = "Job missed deferred execution time"
LastHoldReasonCode = 20
ISC (General)
shun.saito - 5:40 Tuesday 08 September 2026 (37467) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

The fitting results for SRY in klog:37466 are shown below.

The measurement data are saved in the following Dropbox folder:

All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_07_SRY
 

  • Fig. 1: Around 1.6 GHz, without a linear background. Using data from 1610.59 MHz to 1611.02 MHz, the fitted peak frequency was 1610.8297(27) MHz.
    Fig. 2: Around 1.6 GHz, with a linear background. Using data from 1610.59 MHz to 1611.02 MHz, the fitted peak frequency was 1610.893(13) MHz.

    Fig. 3: Around 800 MHz, without a linear background. Using data from 802.82 MHz to 803.27 MHz, the fitted peak frequency was 803.0799(23) MHz.
    Fig. 4: Around 800 MHz, with a linear background. Using data from 802.82 MHz to 803.27 MHz, the fitted peak frequency was 803.147(27) MHz.

    Fig. 5: Around -800 MHz, without a linear background. Using data from 800.72 MHz to 801.16 MHz, the fitted peak frequency was 800.9089(24) MHz.
    Fig. 6: Around -800 MHz, with a linear background. Using data from 800.72 MHz to 801.16 MHz, the fitted peak frequency was 800.839(13) MHz.

    Fig. 7: Around -1.6 GHz, without a linear background. Using data from 1592.3195 MHz to 1592.7295 MHz, the fitted peak frequency was 1592.4944(25) MHz.
    Fig. 8: Around -1.6 GHz, with a linear background. Using data from 1592.3195 MHz to 1592.7295 MHz, the fitted peak frequency was 1592.4459(93) MHz.

Images attached to this comment
ISC (General)
shun.saito - 4:57 Tuesday 08 September 2026 (37466) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

[Fujimoto, Saito]

We adjusted the HWP and polarizer for SRY to obtain a clean peak and acquired the beat signal data. After fitting the data, the deviation of the SRY length from the design value was found to be 2.332(93) cm. This result is consistent with the previous measurements reported in klog:37455: the deviations from the design value were 2.168(80) cm with the HWP scale at 14 and the polarizer scale at 295, and 2.319(71) cm with the HWP scale at 59 and the polarizer scale at 250. However, it is slightly different from the result obtained before moving the lens to improve the mode-matching ratio (klog:37250), where the deviation of the SRY length from the design value was 1.757(50) cm.

Using the SRX result from klog:37450 and the results from klog:37458, I calculated the SRC length and Schnupp asymmetry as follows:

SRC length: 66.61860(51) m
Schnupp asymmetry calculated from the SRC: 3.33775(102) m
Schnupp asymmetry from the weighted average: 3.33842(49) m

These results are consistent with the previous measurements reported in klog:37455 and klog:37458. With the HWP scale at 14 and the polarizer scale at 295, the SRC length was 66.61778(45) m, the Schnupp asymmetry calculated from the SRC was 3.339390(904) m, and the Schnupp asymmetry from the weighted average was 3.33884(48) m. With the HWP scale at 59 and the polarizer scale at 250, the corresponding values were 66.61853(41) m, 3.337880(825) m, and 3.33839(47) m, respectively. Comparing these results with the measurements before moving the lens to improve the mode-matching ratio (klog:37260), where the SRC length was 66.61409(70) m, the Schnupp asymmetry calculated from the SRC was 3.34023(139) m, and the Schnupp asymmetry from the weighted average was 3.33791(45) m, the SRC length and the Schnupp asymmetry calculated from the SRC are somewhat different. However, the Schnupp asymmetry obtained from the weighted average is consistent with the previous result.
 

  • First, we set the HWP scale at the sub-laser to 82 (S polarization) and set the polarizer in front of the RFPD to S polarization. With the main laser turned off, we adjusted the alignment of the sub-laser to SRY. Next, we locked the main laser to SRY, adjusted the alignment to the RFPD, and checked the beat signal. However, as in the previous measurement (klog:37440), the peak was split. Therefore, we adjusted the alignment of the sub-laser to maximize the beat signal, and rotated the HWP and polarizer to maximize the beat signal as well. The HWP scale was then 124 (P polarization), and the polarizer scale was 2 (P polarization). However, the peak was split into three peaks.

    Next, we turned off the main laser and adjusted the alignment again using the sub-laser. When the polarizer in front of the RFPD was removed, the maximum signal was -16 counts for S-polarized injection and -52 counts for P-polarized injection, giving a difference of about a factor of three. The peak also appeared cleaner as a single peak for S polarization, whereas it was split into about three peaks for P polarization.

    Next, with the HWP scale at 82 (S polarization), we set the polarizer scale to 272 (S polarization). Peaks separated by approximately 1 MHz were observed (Photo 1). we then set the polarizer scale to 317, and one of the two peaks became larger (Photo 2). When I set the polarizer scale to 227, the other peak appeared to become larger (Photo 3). The three cases are plotted together in Fig. 1.
     

  • Next, we acquired beat signal data around 1.6 GHz (Photo 4), 0.8 GHz (Photo 5), -0.8 GHz (Photo 6), and -1.6 GHz (Photo 7) with the HWP scale at 82 and the polarizer scale at 317, where the peak appeared the cleanest. I fitted the obtained SRY data both with and without a linear background. I will post the fitting results for the individual peaks later. From the peak frequencies obtained from the fits and their uncertainties, I calculated the minimum and maximum values within the uncertainty ranges. I then took the overall minimum and maximum values from the two fitting models, with and without a linear background, as the uncertainty range.
    Therefore, I used the following data to determine the SRY length:

    Minimum (MHz)    Maximum (MHz)
    1610.8271    1610.9060
    803.0776    803.1743
    -800.9112    -800.8258
    -1592.4969    -1592.4366

    I set the FSR index of the data around -1.6 GHz to 0. For each pair of nearby peak frequencies, I calculated the frequency difference and divided it by the design value of the FSR. I then rounded the resulting value to the nearest integer to determine the FSR index. I fitted the measured peak frequencies as a function of the FSR index using the linear function AN+B, where A and B are fitting parameters and N is the FSR index.
    The fitting results are shown below (Fig. 2):

    A: 2.307881(33) MHz
    B: -1592.467(27) MHz

    Since A corresponds to the FSR, I calculated the SRY length from the fitted value of A, obtaining:

    Fitted value: 64.94972(93) m
    Design value: 64.9264 m
    Difference from the design value (fitted value − design value): 2.332(93) cm

    This result is consistent with the previous measurements reported in klog:37455: the deviations from the design value were 2.168(80) cm with the HWP scale at 14 and the polarizer scale at 295, and 2.319(71) cm with the HWP scale at 59 and the polarizer scale at 250. However, it is slightly different from the result obtained before moving the lens to improve the mode-matching ratio (klog:37250), where the deviation of the SRY length from the design value was 1.757(50) cm.
     

  • Using the SRX result from klog:37450 and the results from klog:37458, I calculated the SRC length and Schnupp asymmetry as follows:

    SRC
    Calculated value: 66.61860(51) m
    Design value: 66.5913 m
    Difference from the design value (calculated value − design value): 2.730(51) cm

    Schnupp asymmetry calculated from the SRC
    Calculated value: 3.33775(102) m
    Design value: 3.3298 m
    Difference from the design value (calculated value − design value): 0.795(102) cm

    Schnupp asymmetry
    Weighted average: 3.33842(49) m
    Design value: 3.3298 m
    Difference from the design value (weighted average − design value): 0.862(49) cm

    These results are consistent with the previous measurements reported in klog:37455 and klog:37458. With the HWP scale at 14 and the polarizer scale at 295, the SRC length was 66.61778(45) m, the Schnupp asymmetry calculated from the SRC was 3.339390(904) m, and the Schnupp asymmetry from the weighted average was 3.33884(48) m. With the HWP scale at 59 and the polarizer scale at 250, the corresponding values were 66.61853(41) m, 3.337880(825) m, and 3.33839(47) m, respectively. Compared with the measurements before moving the lens to improve the mode-matching ratio (klog:37260), where the SRC length was 66.61409(70) m, the Schnupp asymmetry calculated from the SRC was 3.34023(139) m, and the Schnupp asymmetry from the weighted average was 3.33791(45) m, the SRC length and the Schnupp asymmetry calculated from the SRC are somewhat different. However, the Schnupp asymmetry obtained from the weighted average is consistent with the previous result.

Images attached to this comment
DGS (General)
takahiro.yamamoto - 17:58 Monday 07 September 2026 (37465) Print this report
Package update of workstations
Package update was applied to all workstations.
Now all workstations including k1ctr22 (see also klog#37444) are unified their environment.

gateway server was also updated.
AOS (Cameras)
takahiro.yamamoto - 13:56 Monday 07 September 2026 (37464) Print this report
POS camera seems dead
When the monitor workstations in the control room was rebooted for the maintenance, POS camera didn't came back.
According to camera server's logs, network connection of POS camera is unstable in a recent couple of months.

I'm not sure it's related to the recent activities related to the cavity length measurements.
Anyway, cable connection must be checked once.
And also, it's better to replace LAN cable if the connection becomes unstable just by activities around POS table.
LAN cable might be aging such as one for the PMC camera.
Comments to this report:
takahiro.yamamoto - 12:39 Tuesday 08 September 2026 (37469) Print this report
The POS camera resumed operation briefly around 1:30 JST but stopped working again around 11:15 JST.
Even though there was no activity around the POS table, the situation appears to have changed.

Since the camera unit itself has never malfunctioned before, we should first try replacing the LAN cable.

Attached figure and text file shows a down time of POS camera.
Images attached to this comment
Non-image files attached to this comment
ISC (ASC)
takaaki.yokozawa - 13:29 Monday 07 September 2026 (37463) Print this report
Comment to Evaluation of the SR2 mirror angle (37451)
I removed the camera structure from OMM chamber.
Before that, I took picture with bright image.

Fig.1. showed the image with red circle and yellow lines.
As you can see, the red circle was slightly lower than the hole in front of the black shield, but this camera was placed blow the IR beam height, it was not so strange.
Rather, circle can follow the center of the OSEM lights, I think.
Images attached to this comment
VIS (IY)
ryutaro.takahashi - 9:32 Monday 07 September 2026 (37462) Print this report
Comment to Offload of GAS filters (36614)

I offloaded the BF GAS with the FR.

VIS (IX)
ryutaro.takahashi - 9:31 Monday 07 September 2026 (37461) Print this report
Comment to Offload of GAS filters (33170)

I offloaded the F0 GAS with the FR.

ISC (ASC)
takaaki.yokozawa - 9:03 Monday 07 September 2026 (37460) Print this report
Comment to Evaluation of the SR2 mirror angle (37451)
Additional information.

Red circle is the image of black cover in front of OMMT1, with yellow was the center.
In this figure, we put the TCam mirror below the IR beam, so horizontal would be OK, but we need investigation for vertical direction.

I attached the gif image.
Images attached to this comment
ISC (General)
shun.saito - 10:39 Sunday 06 September 2026 (37459) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

The fitting results for PRX and PRY in klog:37458 are shown below.
The measurement data are saved in the following Dropbox folders:

All files/Dropbox KAGRA/Measurements/IFO/PRCL/PRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_04_PRX
All files/Dropbox KAGRA/Measurements/IFO/PRCL/PRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_04_PRY
 

  • PRX
    Fig. 1: Around 1.6 GHz, without a linear background. Using the data from 1591.51 MHz to 1592.0 MHz, the fitted peak frequency was 1591.7750(12) MHz.
    Fig. 2: Around 1.6 GHz, with a linear background. Using the data from 1591.51 MHz to 1592.0 MHz, the fitted peak frequency was 1591.8014(56) MHz.

    Fig. 3: Around 800 MHz, without a linear background. Using the data from 807.62 MHz to 808.15 MHz, the fitted peak frequency was 807.8942(17) MHz.
    Fig. 4: Around 800 MHz, with a linear background. Using the data from 807.62 MHz to 808.15 MHz, the fitted peak frequency was 807.8842(49) MHz.

    Fig. 5: Around -800 MHz, without a linear background. Using the data from 821.12 MHz to 821.59 MHz, the fitted peak frequency was 821.3504(11) MHz.
    Fig. 6: Around -800 MHz, with a linear background. Using the data from 821.12 MHz to 821.59 MHz, the fitted peak frequency was 821.3352(35) MHz.

    Fig. 7: Around -1.6 GHz, without a linear background. Using the data from 1563.29 MHz to 1563.82 MHz, the fitted peak frequency was 1563.5494(14) MHz.
    Fig. 8: Around -1.6 GHz, with a linear background. Using the data from 1563.29 MHz to 1563.82 MHz, the fitted peak frequency was 1563.5525(32) MHz.
     

  • PRY
    Fig. 9: Around 1.6 GHz, without a linear background. Using the data from 1599.85 MHz to 1600.57 MHz, the fitted peak frequency was 1600.1828(18) MHz.
    Fig. 10: Around 1.6 GHz, with a linear background. Using the data from 1599.85 MHz to 1600.57 MHz, the fitted peak frequency was 1600.1637(33) MHz.

    Fig. 11: Around 800 MHz, without a linear background. Using the data from 810.32 MHz to 810.95 MHz, the fitted peak frequency was 810.6120(14) MHz.
    Fig. 12: Around 800 MHz, with a linear background. Using the data from 810.32 MHz to 810.95 MHz, the fitted peak frequency was 810.5939(29) MHz.

    Fig. 13: Around -800 MHz, without a linear background. Using the data from 816.67 MHz to 817.23 MHz, the fitted peak frequency was 816.9934(28) MHz.
    Fig. 14: Around -800 MHz, with a linear background. Using the data from 816.67 MHz to 817.23 MHz, the fitted peak frequency was 817.0274(72) MHz.

    Fig. 15: Around -1.6 GHz, without a linear background. Using the data from 1596.96 MHz to 1597.66 MHz, the fitted peak frequency was 1597.3557(27) MHz.
    Fig. 16: Around -1.6 GHz, with a linear background. Using the data from 1596.96 MHz to 1597.66 MHz, the fitted peak frequency was 1597.4093(82) MHz.

Images attached to this comment
ISC (General)
shun.saito - 9:56 Sunday 06 September 2026 (37458) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

[Fujimoto, Ye, Saito]

We adjusted the HWP and polarizer to obtain clean peaks and acquired beat signal data for PRX and PRY. After fitting the data, the deviations from the design values were 0.926(22) cm for PRX and 0.043(52) cm for PRY. Compared with the previous measurements before moving the lens to improve the mode-matching ratio (klog:37260), which gave deviations of 0.677(11) cm for PRX and -0.107(46) cm for PRY, both results are slightly different.

We also calculated the PRC length and the Schnupp asymmetry from the PRC. Using the Schnupp asymmetry calculated from the SRC in klog:37455, we then calculated the Schnupp asymmetry by taking a weighted average of the two values. The results were as follows:

PRC length: 66.59625(28) m
Schnupp asymmetry calculated from the PRC: 3.338630(565) m
Schnupp asymmetry from the weighted average:
3.33884(48) m when SRY was measured with the HWP scale at 14 and the polarizer scale at 295
3.33839(47) m when SRY was measured with the HWP scale at 59 and the polarizer scale at 250

Compared with the previous measurements before moving the lens to improve the mode-matching ratio (klog:37260), which gave a PRC length of 66.59425(24) m, a Schnupp asymmetry calculated from the PRC of 3.337640(473) m, and a Schnupp asymmetry from the weighted average of 3.33791(45) m, the PRC length is slightly different. However, there is no inconsistency between the Schnupp asymmetry calculated from the PRC and that calculated from the weighted average.
 

  • To acquire the beat signal data for PRX, we first turned off the main laser and adjusted the alignment of the sub-laser. We then turned on the main laser and adjusted the alignment to the RFPD. When we checked the beat signal with the HWP scale at 82 and the polarizer scale at 50 using a spectrum analyzer, the peak was not clean (Photo 1). We therefore rotated the HWP and polarizer. The peak became clean when the HWP scale was set to 70 and the polarizer scale was set to 254. We then acquired data around 1.6 GHz (Photo 2), 0.8 GHz (Photo 3), -0.8 GHz (Photo 4), and -1.6 GHz (Photo 5).
     
  • Similarly, for PRY, we first turned off the main laser and adjusted the alignment of the sub-laser. We then turned on the main laser and adjusted the alignment to the RFPD. We set the HWP scale to 16 and the polarizer scale to 117 to obtain clean peaks, and acquired data around 1.6 GHz (Photo 6), 0.8 GHz (Photo 7), -0.8 GHz (Photo 8), and -1.6 GHz (Photo 9).
     
  • We then fitted the obtained PRX and PRY data with and without a linear background. I will post the fitting results for the individual peaks later. From the peak frequencies obtained from the fits and their uncertainties, we calculated the minimum and maximum values within the uncertainty ranges. We then took the overall minimum and maximum values from both fitting models, with and without a linear background, as the uncertainty range. The following data were therefore used to determine the PRX and PRY lengths.

    PRX
    Minimum (MHz)    Maximum (MHz)
    1591.7738    1591.8070
    807.8792    807.8958
    -821.3516    -821.3318
    -1563.5557    -1563.5479

    PRY
    Minimum (MHz)    Maximum (MHz)
    1600.1604    1600.1846
    810.5910    810.6133
    -817.0346    -816.9907
    -1597.4175    -1597.3530

    We set the FSR index of the data around -1.6 GHz to 0. For each pair of nearby peak frequencies, we calculated the frequency difference and divided it by the design value of the FSR. We then rounded the resulting value to the nearest integer to determine the FSR index. We fitted the measured peak frequencies as a function of the FSR index using the linear function AN+B, where A and B are fitting parameters and N is the FSR index.

    The fitting results were as follows.

    PRX (Fig. 1)
    A: 2.1957810(72) MHz
    B: -1563.5483(38) MHz

    PRY (Fig. 2)
    A: 2.308691(19) MHz
    B: -1597.363(21) MHz

    Since A corresponds to the FSR, we calculated the PRX and PRY lengths from the fitted values of A. The results were as follows.

    PRX
    Fitted length: 68.26556(22) m
    Design value: 68.2563 m
    Difference from the design value (fitted length − design value): 0.926(22) cm

    PRY
    Fitted length: 64.92693(52) m
    Design value: 64.9265 m
    Difference from the design value (fitted length − design value): 0.043(52) cm

    Compared with the previous measurements before moving the lens to improve the mode-matching ratio (klog:37260), which gave deviations of 0.677(11) cm for PRX and -0.107(46) cm for PRY, both results are slightly different.
     

  • We also calculated the PRC length and the Schnupp asymmetry from the PRC. Using the Schnupp asymmetry calculated from the SRC in klog:37455, we calculated the Schnupp asymmetry from the weighted average as follows.

    PRC
    Calculated value: 66.59625(28) m
    Design value: 66.5914 m
    Difference from the design value (calculated value − design value): 0.485(28) cm

    Schnupp asymmetry calculated from the PRC
    Calculated value: 3.338630(565) m
    Design value: 3.3298 m
    Difference from the design value (calculated value − design value): 0.8830(565) cm

    Schnupp asymmetry
    When SRY was measured with the HWP scale at 14 and the polarizer scale at 295:
    Weighted average: 3.33884(48) m
    Design value: 3.3298 m
    Difference from the design value (weighted average − design value): 0.904(48) cm

    When SRY was measured with the HWP scale at 59 and the polarizer scale at 250:
    Weighted average: 3.33839(47) m
    Design value: 3.3298 m
    Difference from the design value (weighted average − design value): 0.859(47) cm

    Compared with the previous measurements before moving the lens to improve the mode-matching ratio (klog:37260), which gave a PRC length of 66.59425(24) m, a Schnupp asymmetry calculated from the PRC of 3.337640(473) m, and a Schnupp asymmetry from the weighted average of 3.33791(45) m, the PRC length is slightly different. However, there is no inconsistency between the Schnupp asymmetry calculated from the PRC and that calculated from the weighted average.

Images attached to this comment
ISC (ASC)
takaaki.yokozawa - 12:22 Saturday 05 September 2026 (37457) Print this report
Comment to Evaluation of the SR2 mirror angle (37451)
After the initial alignment of Xarm, Yarm and PRMI, I performed the SR2 angle investigation.

I set SR2 suspension to PAY_FLOAT state, requested PRX 1f lock to vertex guardian

By the capture diff script, I can find the beam position on the OMMT1 mirror as shown in pdf1.
Original picture was the 0 -256 gray scale, and just performed the subtraction between two figures, and multiplied to 30 after performing the absolute.
From the circle image and center value of the +500 and 0 case, I found the 321 IM optic align value would be center.
Same measurement performed in pitch with adding 321 count IM optic align Y, I can obtain the 150 count would be center in pdf2.

I took picture with PRX lock and without IR laser (shutter on), and confirmed the SR2 centering as shown in Fig.1.

Now, I didn't perform this change to SR2, It would be better with centering of SR2 oplev next Monday(?).
Images attached to this comment
Non-image files attached to this comment
ISC (General)
shun.saito - 10:39 Saturday 05 September 2026 (37456) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

The fitting results for the SRY measurements in klog:37455, with the HWP scale at 14 and the polarizer scale at 295, and with the HWP scale at 59 and the polarizer scale at 250, are shown below.

The measurement data are saved in the following Dropbox folders:

All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_01_SRY_hwp14_pol295
All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_01_SRY_hwp59_pol250
 

  • HWP scale: 14, Polarizer scale: 295

    Fig. 1: Around 1.6 GHz, without a linear background. Using the data from 1611.21 MHz to 1612.42 MHz, the fitted peak frequency was 1611.809(10) MHz.
    Fig. 2: Around 1.6 GHz, with a linear background. Using the data from 1611.21 MHz to 1612.42 MHz, the fitted peak frequency was 1611.766(45) MHz.

    Fig. 3: Around 800 MHz, without a linear background. Using the data from 810.37 MHz to 811.56 MHz, the fitted peak frequency was 810.962(11) MHz.
    Fig. 4: Around 800 MHz, with a linear background. Using the data from 810.37 MHz to 811.56 MHz, the fitted peak frequency was 810.993(45) MHz.

    Fig. 5: Around -800 MHz, without a linear background. Using the data from 845.47648 MHz to 846.683146 MHz, the fitted peak frequency was 846.1233(96) MHz.
    Fig. 6: Around -800 MHz, with a linear background. Using the data from 845.47648 MHz to 846.683146 MHz, the fitted peak frequency was 846.033(45) MHz.

    Fig. 7: Around -1.6 GHz, without a linear background. Using the data from 1655.6 MHz to 1656.77 MHz, the fitted peak frequency was 1656.233(13) MHz.
    Fig. 8: Around -1.6 GHz, with a linear background. Using the data from 1656.6 MHz to 1656.77 MHz, the fitted peak frequency was 1656.2322(79) MHz.
     

  • HWP scale: 59, Polarizer scale: 250

    Fig. 9: Around 1.6 GHz, without a linear background. Using the data from 1599.24 MHz to 1600.04 MHz, the fitted peak frequency was 1599.5509(77) MHz.
    Fig. 10: Around 1.6 GHz, with a linear background. Using the data from 1599.24 MHz to 1600.04 MHz, the fitted peak frequency was 1599.507(11) MHz.

    Fig. 11: Around 800 MHz, without a linear background. Using the data from 789.2 MHz to 789.96 MHz, the fitted peak frequency was 789.4894(61) MHz.
    Fig. 12: Around 800 MHz, with a linear background. Using the data from 789.2 MHz to 789.96 MHz, the fitted peak frequency was 789.449(11) MHz.

    Fig. 13: Around -800 MHz, without a linear background. Using the data from 814.0 MHz to 814.82 MHz, the fitted peak frequency was 814.4756(78) MHz.
    Fig. 14: Around -800 MHz, with a linear background. Using the data from 814.0 MHz to 814.82 MHz, the fitted peak frequency was 814.541(15) MHz.

    Fig. 15: Around -1.6 GHz, without a linear background. Using the data from 1582.56 MHz to 1583.35 MHz, the fitted peak frequency was 1583.0282(66) MHz.
    Fig. 16: Around -1.6 GHz, with a linear background. Using the data from 1582.56 MHz to 1583.35 MHz, the fitted peak frequency was 1583.0585(99) MHz.

Images attached to this comment
ISC (General)
shun.saito - 9:36 Saturday 05 September 2026 (37455) Print this report
Comment to PRCL/SRCL Measurement with P-Polarization (37436)

We analyzed the SRY data obtained in klog:37440. The deviation from the design value was 2.168(80) cm when the HWP scale was 14 and the polarizer scale was 295, and 2.319(71) cm when the HWP scale was 59 and the polarizer scale was 250. Compared with the previous measurement (klog:37393), which gave a deviation of 2.385(42) cm from the SRY design value, the result with the HWP scale at 59 is consistent, while the result with the HWP scale at 14 appears to be slightly different. Both results differ more significantly from the result before moving the lens to improve the mode-matching ratio (klog:37250), which gave a deviation of 1.757(50) cm from the design value.

Using the SRX result from klog:37450, we also calculated the SRC length and the Schnupp asymmetry. The SRC lengths were 66.61778(45) m for the HWP scale of 14 and polarizer scale of 295, and 66.61853(41) m for the HWP scale of 59 and polarizer scale of 250. The Schnupp asymmetries calculated from the SRC lengths were 3.339390(904) m and 3.337880(825) m, respectively. Compared with the previous measurement (klog:37393), which gave an SRC length of 66.61828(92) m and a Schnupp asymmetry calculated from the SRC of 3.33605(185) m, both SRC lengths are consistent, while the Schnupp asymmetry with the HWP scale at 14 appears to be slightly different. Compared with the results before moving the lens to improve the mode-matching ratio (klog:37260), which gave an SRC length of 66.61409(70) m and a Schnupp asymmetry calculated from the SRC of 3.34023(139) m, both SRC lengths are slightly different, while the Schnupp asymmetry with the HWP scale at 59 appears to be slightly different.
 

  • We fitted the SRY data obtained in klog:37440 with and without a linear background. I will post the fitting results for the individual peaks later. From the peak frequencies obtained from the fits and their uncertainties, we calculated the minimum and maximum values within the uncertainty ranges. We then took the overall minimum and maximum values from both fitting models, with and without a linear background, as the uncertainty range. The following data were therefore used to determine the SRY length.

    HWP scale: 14, Polarizer scale: 295
    Minimum (MHz)    Maximum (MHz)
    1611.7206    1611.8190
    810.9479    811.0371
    -846.1329    -845.9886
    -1656.2458    -1656.2199

    HWP scale: 59, Polarizer scale: 250
    Minimum (MHz)    Maximum (MHz)
    1599.4960    1599.5586
    789.4376    789.4956
    -814.5555    -814.4679
    -1583.0683    -1583.0217

    We set the FSR index of the data around -1.6 GHz to 0. For each pair of nearby peak frequencies, we calculated the frequency difference and divided it by the design value of the FSR. We then rounded the resulting value to the nearest integer to determine the FSR index. We fitted the measured peak frequencies as a function of the FSR index using the linear function AN+B, where A and B are fitting parameters and N is the FSR index.

    The fitting results were as follows.

    HWP scale: 14, Polarizer scale: 295 (Fig. 1)
    A: 2.307939(29) MHz
    B: -1656.230(13) MHz
    HWP scale: 59, Polarizer scale: 250 (Fig. 2)
    A: 2.307886(26) MHz
    B: -1583.043(22) MHz

    Since A corresponds to the FSR, we calculated the SRY length from the fitted value of A. The results were as follows.

    HWP scale: 14, Polarizer scale: 295
    Fitted length: 64.94808(80) m
    Design value: 64.9264 m
    Difference from the design value (fitted length − design value): 2.168(80) cm
    HWP scale: 59, Polarizer scale: 250
    Fitted length: 64.94959(71) m
    Design value: 64.9264 m
    Difference from the design value (fitted length − design value): 2.319(71) cm

    Compared with the previous measurement (klog:37393), which gave a deviation of 2.385(42) cm from the SRY design value, the result with the HWP scale at 59 is consistent, while the result with the HWP scale at 14 appears to be slightly different. Both results differ more significantly from the result before moving the lens to improve the mode-matching ratio (klog:37250), which gave a deviation of 1.757(50) cm from the design value.
     

  • Using the SRX result from klog:37450, we calculated the SRC length and the Schnupp asymmetry as follows.

    HWP scale: 14, Polarizer scale: 295
    SRC
    Calculated value: 66.61778(45) m
    Design value: 66.5913 m
    Difference from the design value (calculated value − design value): 2.648(45) cm

    Schnupp asymmetry calculated from the SRC
    Calculated value: 3.339390(904) m
    Design value: 3.3298 m
    Difference from the design value (calculated value − design value): 0.9590(904) cm

    HWP scale: 59, Polarizer scale: 250
    SRC
    Calculated value: 66.61853(41) m
    Design value: 66.5913 m
    Difference from the design value (calculated value − design value): 2.723(41) cm

    Schnupp asymmetry calculated from the SRC
    Calculated value: 3.337880(825) m
    Design value: 3.3298 m
    Difference from the design value (calculated value − design value): 0.8080(825) cm

    Compared with the previous measurement (klog:37393), which gave an SRC length of 66.61828(92) m and a Schnupp asymmetry calculated from the SRC of 3.33605(185) m, both SRC lengths are consistent, while the Schnupp asymmetry with the HWP scale at 14 appears to be slightly different. Compared with the results before moving the lens to improve the mode-matching ratio (klog:37260), which gave an SRC length of 66.61409(70) m and a Schnupp asymmetry calculated from the SRC of 3.34023(139) m, both SRC lengths are slightly different, while the Schnupp asymmetry with the HWP scale at 59 appears to be slightly different.

Images attached to this comment
ISC (ASC)
takaaki.yokozawa - 14:29 Friday 04 September 2026 (37454) Print this report
Comment to Evaluation of the SR2 mirror angle (37451)
I(actually not I but ChatGPT) generated the program for evaluating the difference of the png files.
With the PRX lock and this program, I will perform the similar measurement in next chance.
Images attached to this comment
VAC (OMMT)
takahiro.yamamoto - 11:56 Friday 04 September 2026 (37453) Print this report
Pausing slack notification about vacuum alert for OMMT
Slack alerts for K1:VAC-PRESSURE_CS_OMMTGV (CC-10 readout) and K1:VAC-GV_OMMT_{OPEN|CLOSE} (GV status) were paused.

These can be manually resumed at any time before the next pumping down.
Even if they are not manually resumed, they will automatically resume when the CC-10 readout falls below the threshold or when the gate valve opens.
ISC (General)
shun.saito - 10:19 Friday 04 September 2026 (37452) Print this report
Comment to Attempt to change the SRX length (37450)

The fitting results for the individual peaks after changing and then restoring the SRX length in klog:37450 are shown below.

The measurement data are saved in the following Dropbox folders:

All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_03_SRX_moved
All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_03_SRX_restored
 

  • After changing the SRX length
    Fig. 1: Around 1.6 GHz, without a linear background. Using the data from 1630.48 MHz to 1631.57 MHz, the fitted peak frequency was 1630.9316(29) MHz.
    Fig. 2: Around 1.6 GHz, with a linear background. Using the data from 1630.48 MHz to 1631.57 MHz, the fitted peak frequency was 1630.9322(38) MHz.

    Fig. 3: Around 800 MHz, without a linear background. Using the data from 789.76 MHz to 790.84 MHz, the fitted peak frequency was 790.2061(23) MHz.
    Fig. 4: Around 800 MHz, with a linear background. Using the data from 789.76 MHz to 790.84 MHz, the fitted peak frequency was 790.2147(25) MHz.

    Fig. 5: Around -800 MHz, without a linear background. Using the data from 798.46 MHz to 799.51 MHz, the fitted peak frequency was 799.0342(30) MHz.
    Fig. 6: Around -800 MHz, with a linear background. Using the data from 798.46 MHz to 799.51 MHz, the fitted peak frequency was 799.0380(41) MHz.

    Fig. 7: Around -1.6 GHz, without a linear background. Using the data from 1588.38 MHz to 1589.78 MHz, the fitted peak frequency was 1589.2838(23) MHz.
    Fig. 8: Around -1.6 GHz, with a linear background. Using the data from 1588.38 MHz to 1589.78 MHz, the fitted peak frequency was 1589.2831(38) MHz.
     

  • After restoring the SRX length
    Fig. 9: Around 1.6 GHz, without a linear background. Using the data from 1608.77 MHz to 1609.66 MHz, the fitted peak frequency was 1609.0959(28) MHz.
    Fig. 10: Around 1.6 GHz, with a linear background. Using the data from 1608.77 MHz to 1609.66 MHz, the fitted peak frequency was 1609.0650(63) MHz.

    Fig. 11: Around 800 MHz, without a linear background. Using the data from 796.61 MHz to 797.44 MHz, the fitted peak frequency was 796.9280(26) MHz.
    Fig. 12: Around 800 MHz, with a linear background. Using the data from 796.61 MHz to 797.44 MHz, the fitted peak frequency was 796.898(10) MHz.

    Fig. 13: Around -800 MHz, without a linear background. Using the data from 835.71 MHz to 836.57 MHz, the fitted peak frequency was 836.2367(26) MHz.
    Fig. 14: Around -800 MHz, with a linear background. Using the data from 835.71 MHz to 836.57 MHz, the fitted peak frequency was 836.2598(71) MHz.

    Fig. 15: Around -1.6 GHz, without a linear background. Using the data from 1577.79 MHz to 1578.53 MHz, the fitted peak frequency was 1578.1716(42) MHz.
    Fig. 16: Around -1.6 GHz, with a linear background. Using the data from 1577.79 MHz to 1578.53 MHz, the fitted peak frequency was 1578.168(10) MHz.

Images attached to this comment
ISC (ASC)
takaaki.yokozawa - 7:30 Friday 04 September 2026 (37451) Print this report
Evaluation of the SR2 mirror angle
After installed the IR sensitive camera, we started the evaluation of the SR2 mirror angle.

Initial alignment for Xarm and Yarm performed.
I set the SR2 suspension to PAY_FLOAT state, ETMX, ETMY MISALIGNED state, ITMX MISALIGNED_BF state.
(single bounce from ITMY)
Close the GRX and GRY shutter.

I moved yaw direction using the IM optic align.
when I put the 10 count, the oplev yaw value moved 8 urad, so I roughly evaluated 10 count -> 8 urad in SR2.
the distance from SR2 to OMMT1 is 21,300 mm and we want to move the beam position on the OMMT1 at 50 mm, we need to move about 2.3 mrad in SR2 ~ 3,000 count to IMY optic align.
I added the +4,000 count, but we cannot see change in camera image, even I increased the IMC output from 1 W to 4 W, the situation was not changed.
and I changed to -4,000 count, but we cannot see change in camera image, I gave up this measurement today.
(OMMT2 trans QPD sum became almost zero even not moved so much)

Put the target inside the OMM chamber or increase the power to OMC (PRMI bright lock?)
Comments to this report:
takaaki.yokozawa - 14:29 Friday 04 September 2026 (37454) Print this report
I(actually not I but ChatGPT) generated the program for evaluating the difference of the png files.
With the PRX lock and this program, I will perform the similar measurement in next chance.
Images attached to this comment
takaaki.yokozawa - 12:22 Saturday 05 September 2026 (37457) Print this report
After the initial alignment of Xarm, Yarm and PRMI, I performed the SR2 angle investigation.

I set SR2 suspension to PAY_FLOAT state, requested PRX 1f lock to vertex guardian

By the capture diff script, I can find the beam position on the OMMT1 mirror as shown in pdf1.
Original picture was the 0 -256 gray scale, and just performed the subtraction between two figures, and multiplied to 30 after performing the absolute.
From the circle image and center value of the +500 and 0 case, I found the 321 IM optic align value would be center.
Same measurement performed in pitch with adding 321 count IM optic align Y, I can obtain the 150 count would be center in pdf2.

I took picture with PRX lock and without IR laser (shutter on), and confirmed the SR2 centering as shown in Fig.1.

Now, I didn't perform this change to SR2, It would be better with centering of SR2 oplev next Monday(?).
Images attached to this comment
Non-image files attached to this comment
takaaki.yokozawa - 9:03 Monday 07 September 2026 (37460) Print this report
Additional information.

Red circle is the image of black cover in front of OMMT1, with yellow was the center.
In this figure, we put the TCam mirror below the IR beam, so horizontal would be OK, but we need investigation for vertical direction.

I attached the gif image.
Images attached to this comment
takaaki.yokozawa - 13:29 Monday 07 September 2026 (37463) Print this report
I removed the camera structure from OMM chamber.
Before that, I took picture with bright image.

Fig.1. showed the image with red circle and yellow lines.
As you can see, the red circle was slightly lower than the hole in front of the black shield, but this camera was placed blow the IR beam height, it was not so strange.
Rather, circle can follow the center of the OSEM lights, I think.
Images attached to this comment
ISC (General)
shun.saito - 6:23 Friday 04 September 2026 (37450) Print this report
Attempt to change the SRX length

[Fujimoto, Ye, Saito]

After Takahashi-san and Ushiba-san changed the length of SRX (klog:37449), and again after they restored the length, we acquired beat signal data around 1.6, 0.8, -0.8, and -1.6 GHz. We then calculated the SRX length. The deviations from the design value were 3.050(11) cm after the length was changed and 3.127(42) cm after the length was restored. Comparing the result after restoring the length with the previous measurement (klog:37393), which gave a deviation of 3.01(18) cm from the design value, we consider the results to be consistent. However, the result differs slightly from the result before moving the lens to improve the mode-matching ratio (klog:37260), which gave a deviation of 2.80(13) cm. According to klog:37449, the SRX length decreased by 1 mm after the length was changed. The two measurements also show that the SRX length decreased by approximately 1 mm after the length was changed. Therefore, we confirmed that this measurement method can detect changes in the cavity length.
 

  • After Takahashi-san and Ushiba-san changed the SRX length (klog:37449), we removed the mirror that had been placed in the optical path to the RFPD at the reflection port of OMMT2 in the previous measurement (klog:37445). We then injected the light into the RFPD and adjusted the alignment to maximize the DC output. Next, we injected the sub-laser with the HWP scale set to 82, corresponding to S-polarization. We observed the beat signal with a spectrum analyzer and rotated the polarizer to maximize the beat signal. The scale reading was then set to 50. We acquired data when the beat signal was around 1.6 GHz (Photo 1), 0.8 GHz (Photo 2), -0.8 GHz (Photo 3), and -1.6 GHz (Photo 4).
     
  • After Takahashi-san and Ushiba-san restored the SRX length, we adjusted the alignment to maximize the DC output of the RFPD. When we checked the beat signal around 1.6 GHz, the peak appeared to be split into two peaks (Photo 5). We therefore turned off the main laser and adjusted the alignment of the sub-laser. However, the alignment already appeared to be sufficiently optimized, and there was almost no change. We then turned the main laser back on and checked the beat signal again. The peak had become clean, so we acquired data when the beat signal was around 1.6 GHz (Photo 6), 0.8 GHz (Photo 7), -0.8 GHz (Photo 8), and -1.6 GHz (Photo 9).
     
  • We fitted the data around each peak with and without a linear background. I will post the fitting results for these peaks later. From the peak frequencies obtained from the fits and their uncertainties, we calculated the minimum and maximum values within the uncertainty ranges. We then took the overall minimum and maximum values from both fitting models, with and without a linear background, as the uncertainty range. The following data were therefore used to determine the SRX length.

    After changing the length
    Minimum (MHz)    Maximum (MHz)
    1630.9283    1630.9360
    790.2038    790.2172
    -799.0422    -799.0312
    -1589.2869    -1589.2793

    After restoring the length
    Minimum (MHz)    Maximum (MHz)
    1609.0587    1609.0987
    796.8883    796.9306
    -836.2669    -836.2342
    -1578.1785    -1578.1583

    We set the FSR index of the data around -1.6 GHz to 0. For each pair of adjacent peak frequencies, we calculated the frequency difference and divided it by the design value of the FSR. We then rounded the resulting value to the nearest integer to determine the FSR index. We fitted the measured peak frequencies as a function of the FSR index using the following linear function AN+B where A and B are fitting parameters and N is the FSR index.

    The fitting results were as follows.

    After changing the length (Fig. 1)
    A: 2.1951014(35) MHz
    B: -1589.2804(34) MHz

    After restoring the length (Fig. 2)
    A: 2.195077(14) MHz
    B: -1578.1721(92) MHz

    Since A corresponds to the FSR, we calculated the SRX length from the fitted value of A. The results were as follows.

    After changing the length
    Fitted length: 68.28670(11) m
    Design value: 68.2562 m
    Difference from the design value (fitted length − design value): 3.050(11) cm

    After restoring the length
    Fitted length: 68.28747(42) m
    Design value: 68.2562 m
    Difference from the design value (fitted length − design value): 3.127(42) cm

    Comparing the result after restoring the length with the previous measurement (klog:37393), which gave a deviation of 3.01(18) cm from the design value, we consider the results to be consistent. However, the result differs slightly from the result before moving the lens to improve the mode-matching ratio (klog:37260), which gave a deviation of 2.80(13) cm.
    According to klog:37449, the SRX length decreased by 1 mm after the length was changed. The two measurements also show that the SRX length decreased by approximately 1 mm after the length was changed. Therefore, we confirmed that this measurement method can detect changes in the cavity length.

Images attached to this report
Comments to this report:
shun.saito - 10:19 Friday 04 September 2026 (37452) Print this report

The fitting results for the individual peaks after changing and then restoring the SRX length in klog:37450 are shown below.

The measurement data are saved in the following Dropbox folders:

All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_03_SRX_moved
All files/Dropbox KAGRA/Measurements/IFO/SRCL/SRCL_OMMT2_REFL_beat_signal_PZT_sweep/2026_09_03_SRX_restored
 

  • After changing the SRX length
    Fig. 1: Around 1.6 GHz, without a linear background. Using the data from 1630.48 MHz to 1631.57 MHz, the fitted peak frequency was 1630.9316(29) MHz.
    Fig. 2: Around 1.6 GHz, with a linear background. Using the data from 1630.48 MHz to 1631.57 MHz, the fitted peak frequency was 1630.9322(38) MHz.

    Fig. 3: Around 800 MHz, without a linear background. Using the data from 789.76 MHz to 790.84 MHz, the fitted peak frequency was 790.2061(23) MHz.
    Fig. 4: Around 800 MHz, with a linear background. Using the data from 789.76 MHz to 790.84 MHz, the fitted peak frequency was 790.2147(25) MHz.

    Fig. 5: Around -800 MHz, without a linear background. Using the data from 798.46 MHz to 799.51 MHz, the fitted peak frequency was 799.0342(30) MHz.
    Fig. 6: Around -800 MHz, with a linear background. Using the data from 798.46 MHz to 799.51 MHz, the fitted peak frequency was 799.0380(41) MHz.

    Fig. 7: Around -1.6 GHz, without a linear background. Using the data from 1588.38 MHz to 1589.78 MHz, the fitted peak frequency was 1589.2838(23) MHz.
    Fig. 8: Around -1.6 GHz, with a linear background. Using the data from 1588.38 MHz to 1589.78 MHz, the fitted peak frequency was 1589.2831(38) MHz.
     

  • After restoring the SRX length
    Fig. 9: Around 1.6 GHz, without a linear background. Using the data from 1608.77 MHz to 1609.66 MHz, the fitted peak frequency was 1609.0959(28) MHz.
    Fig. 10: Around 1.6 GHz, with a linear background. Using the data from 1608.77 MHz to 1609.66 MHz, the fitted peak frequency was 1609.0650(63) MHz.

    Fig. 11: Around 800 MHz, without a linear background. Using the data from 796.61 MHz to 797.44 MHz, the fitted peak frequency was 796.9280(26) MHz.
    Fig. 12: Around 800 MHz, with a linear background. Using the data from 796.61 MHz to 797.44 MHz, the fitted peak frequency was 796.898(10) MHz.

    Fig. 13: Around -800 MHz, without a linear background. Using the data from 835.71 MHz to 836.57 MHz, the fitted peak frequency was 836.2367(26) MHz.
    Fig. 14: Around -800 MHz, with a linear background. Using the data from 835.71 MHz to 836.57 MHz, the fitted peak frequency was 836.2598(71) MHz.

    Fig. 15: Around -1.6 GHz, without a linear background. Using the data from 1577.79 MHz to 1578.53 MHz, the fitted peak frequency was 1578.1716(42) MHz.
    Fig. 16: Around -1.6 GHz, with a linear background. Using the data from 1577.79 MHz to 1578.53 MHz, the fitted peak frequency was 1578.168(10) MHz.

Images attached to this comment
VIS (General)
ryutaro.takahashi - 18:44 Thursday 03 September 2026 (37449) Print this report
Change of SRCL

[Ushiba, Takahashi]

We moved three SR mirrors to change SRCL. Each setpoint for the IP L LVDT was changed by +200 [um]. SRCL was decreased by 1mm in Total. Moving order was SR3, SRM, and SR2. After changing the setpoints, GRY was locked and aligned. The setpoints for the Oplev yaw were changed from 37 to 31 for SR3 and from -49 to -45 for SR2. Changed values are summarized below. Oplev L was different from IP L by a factor of 2. After the length measurements, all setpoints were recovered.

  IP L setpoint [um] IP L OUT [cnt] OL L [um] OL P [urad] OL Y [urad]
SR3 0:200 -3000:3000 +210 (-90:120) -2 (17:15) -6 (37:31)
SRM -550:-350 -6200:-2500 +190 (-60:150) +5 (32:37) -32 (68:36)
SR2 -100:100 6900:9900 +105 (-245:-150) +26 (18:44) +4 (-49:-45)

 

 

Images attached to this report
ISC (General)
tomotada.akutsu - 17:13 Thursday 03 September 2026 (37448) Print this report
Comment to Evaluation toward the beam position measurement at the surface of OMMT1 shield (37432)

Note that: OMMT1 equips LIGO-OSEMs, and the OSEMs are using LEDs, whose wavelength is nearly infrared (but not 1um), and the IR camera (without proper filtering) senses the infrared light clearly. Very brighter than stars which the IR camera can detect.

To distinguish the light source, it might be helpful to turn off the OSEM LEDs, if possible.

ISC (General)
takaaki.yokozawa - 13:07 Thursday 03 September 2026 (37447) Print this report
Comment to Evaluation toward the beam position measurement at the surface of OMMT1 shield (37432)
Images attached to this comment
ISC (General)
takaaki.yokozawa - 11:48 Thursday 03 September 2026 (37446) Print this report
Comment to Evaluation toward the beam position measurement at the surface of OMMT1 shield (37432)
I installed the Camera and structure just below the IR beam (SRM - OMMT1) as shown in Fig.1. (cared both main beam and reflected beam to outside of OMMT chamber in current experiment)
After that, I prepared the PC for remote connection (If you have interested in the IP address, please contact Yokozawa). Now we can connect the remote PC via VNC.

Fig.2. showed the bright case of Camera image and Fig.3. showed the closed OMM chamber by aluminum.
I don't know the bright three image, we can start the remote measurement of SR2 mirror tomorrow morning, I think.
Images attached to this comment
Search Help
×

Warning

×