Displaying report 1-1 of 1.
Reports until 16:57, Wednesday 26 June 2024
H1 General (ISC, OpsInfo)
oli.patane@LIGO.ORG - posted 16:57, Wednesday 26 June 2024 - last comment - 19:01, Wednesday 26 June 2024(78691)
Ops Day Shift End

TITLE: 06/26 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently relocking and at ENGAGE_SOFT_LOOPS. Two locklosses during my shift, and we had a good amount of trouble messing with ALSX during relocking this second time.

After thislast lockloss, I went to Initial alignment, and while trying to lock green arms I had the same issues with the beatnote frequency and so Sheila and I went to adjust the fiber polarization to get it back to the values that it seems are ideal for ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT and ALS-X_FIBR_LOCK_FIBER_TRANSRIGHTPOL, the closer we got to the correct values for those two channels, the worse the beatnote would get. It seems like the ideal max splot for the ALSX beatnote is 8.8dB and we started with it around -20dB, but as we adjusted the fiber polarization, the beatnote went down to -30dB. Trying to then adjust the fiber polarization to maximize the beat note sent the two fiber polarizatoin channels the complete opposite direction that we wanted, so we went back and based our movements on those two channels to slightly improve those values, and changed the minimum beatnote value to be -20dB (tagging ops, needs to be accepted in sdf) instead of -10dB as a temporary fix for now to make sure that we don't get stuck in fault again like last night.


LOG:

14:30 Detector unlocked and at FIND_IR
    - Initial alignment had been done by H1 Manager, but it had become stuck at the end at 10:46UTC and hadn't tried relocking again until 13:54UTC, and by that time it seems like the alignment had drifted because it couldn't lock
14:37 We started going through CHECK_MICH_FRINGES so I took us to DOWN and ran another initial alignment
14:52 Initial alignment done, relocking
15:41 NOMINAL_LOW_NOISE
15:47 Observing

16:04  Lockloss
16:29 Initial alignment complete, relocking
17:11 NOMINAL_LOW_NOISE
17:14 Observing

22:04 Lockloss
- Went to Initial alignment, had the same issues with the beatnote frequency and so Sheila and I went to adjust the fiber polarization to get it back to the values that it seems are ideal for ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT and ALS-X_FIBR_LOCK_FIBER_TRANSRIGHTPOL, the closer we got to the correct values for those two channels, the worse the beatnote would get. It seems like the ideal max spot for the beatnote is 8.8dB and we started with it around -20dB, but as we adjusted the fiber polarization, the beatnote went down to -30dB. Trying to then adjust the fiber polarization to maximize the beat note sent the two fiber polarizatoin channels the complete opposite direction that we wanted, so we went back and based our movements on those two channels to slightly improve those values, and changed the minimum beatnote value to be -20dB instead of -10dB as a temporary fix for now to make sure that we don't get stuck in fault again like last night.

 

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 19:01, Wednesday 26 June 2024 (78694)

We are not directly measuring the amount of power in the correct polarization. Instead, we measure the power in the wrong polarization as well as the power exiting the fiber using a beam sampler. Unfortuately, the reflection of this beam sampler is stronlgy polarization dependent, so that the calculated percentage and power in the correct polarization is only valid when the polarization is adjusted correctly!

Instead of looking at these values, one should just maximize the beat note, or minimize the power in the wrong polarization.

Displaying report 1-1 of 1.