Reports 1-1 of 1 Clear search Modify search
ISC (General)
takaaki.yokozawa - 14:48 Wednesday 14 October 2026 (37667) Print this report
Trial of the PRMI lock
[Hirose, Yokozawa]

After the recovery of the GRY, we performed the initial alignment again for Xarm and Yarm.
Next, we tired to lock the PRMI by tweaking the PRM.

PRMI actually can be locked, but the POP 90 I value was about 0.4 and MICH control seemed very loose.

1. Compared with previous Initial alignment PRMI
Previous one was
GPS 1471274941
2026/08/20 15:28;43 UTC

- IMC output was almost same, 0.94 -> 0.99
- Refl DC PD1 value larger 10 -> 14, we need to turn the IFO_HWP more, but when we rotated, PRMI locked loss, so we will tune the HWP after investigate the MICH LSC.
- POP DC PD1 value lower 0.01 -> 0.006
- POP 90 I offset value changed.
- Check the filter bank MICH1, MICH2, PRCL1, PRCL2, but I cannot find any difference

2. Measured the transfer function
Fig.1. and Fig.2. showed the MICH and PRCL OLTF, MICH 20 dB lower than previous, PRCL shape different about -5 dB.
We need to check why the MICH OLG so small.

3. Performed the Yuzurihara-san offset code

/opt/rtcds/userapps/release/asc/k1/scripts $ python3 subtract_dark_offset.py -p notQPD
K1:LSC-REFL_PDA1_RF45_Q_OFFSET => -2.8782957593599954
K1:LSC-REFL_PDA1_RF45_I_OFFSET => -0.7863214095433553
K1:LSC-REFL_PDA2_RF51_Q_OFFSET => -58.14948800404866
K1:LSC-REFL_PDA2_RF51_I_OFFSET => -94.92184766133626
K1:LSC-REFL_PDA2_RF135_I_OFFSET => 15.199504470825195
K1:LSC-REFL_PDA2_RF135_Q_OFFSET => 206.31389261881512
K1:LSC-AS_PDA1_RF17_Q_OFFSET => 1.4356917520364125
K1:LSC-AS_PDA1_RF17_I_OFFSET => 4.0745154341061935
K1:LSC-POP_PDA1_RF17_Q_OFFSET => -35.377245712280256
K1:LSC-POP_PDA1_RF17_I_OFFSET => -1.565380189816157
K1:LSC-POP_PDA1_RF45_Q_OFFSET => 2.929738660653432
K1:LSC-POP_PDA1_RF45_I_OFFSET => -1.1762522975603742
K1:LSC-POP_PDA2_RF90_Q_OFFSET => 317.74421335856124
K1:LSC-POP_PDA2_RF90_I_OFFSET => -315.9900405883789

raceback (most recent call last):
File "/opt/rtcds/userapps/trunk/asc/k1/scripts/subtract_dark_offset.py", line 171, in
zeroOffs(channels_omc, fout)
File "/opt/rtcds/userapps/trunk/asc/k1/scripts/subtract_dark_offset.py", line 48, in zeroOffs
d = z.avg(t_ave, list_of_chans)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/cdsutils/avg.py", line 69, in avg
for buf in conn.iterate(*args):
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/cdsutils/nds.py", line 104, in iterate
return super(connection, self).iterate(*nargs, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/nds2.py", line 1340, in iterate

So (maybe) only 14 PD offset can be changed.

But still we couldn't find the critical reason
- why the POP 90 I during PRMI lock lower (1.0 -> 0.4)
- why the MICH OLTF so small (-20 dB)

We also tried to lock the SRY and SRMI.
SRY locked without any problem, SRMI also.
We measured the OLTF for SRMI (MICH Fig.3. and SRCL Fig.4. )

Images attached to this report
Comments to this report:
takahiro.yamamoto - 18:35 Wednesday 14 October 2026 (37669) Print this report
Since the error message is missing from the traceback (only the stack trace is attached), this is merely a guess, but I suspect an NDS 'overloaded' error occurred.

I have heard that this script has been successfully tested in the past, so it should run correctly when the NDS server is under low load. But, NDS overload can occur depending on the situation, such as when other users are applying high loads to the NDS or when many test points remain un-released after use.

In such cases, waiting and re-executing the script, or releasing unnecessary test points, should resolve the issue.
Search Help
×

Warning

×