Displaying report 1-1 of 1.
Reports until 15:28, Tuesday 28 May 2024
H1 SQZ (ISC)
camilla.compton@LIGO.ORG - posted 15:28, Tuesday 28 May 2024 (78088)
SQZ alignment change for new OFI spot

Sheila, Camilla, Jenne, Naoki

To compensate for 78096  SR3/SR2 alignment change we adjusted the SQZ alignment.
 
Started by reverting SQZ alignment to 2024/04/22 11:21:06 UTC (1397820084) which is before the big alignment shift, when we had 160MPc range and the PSAMs were the same as current values (9.0V, -0.7V). SDFs. This should have brought the YAW alignment closer to new spot.
 
Then as the IFO was locking I moved ZM4,6 in P to increase the SQZ-OMC_TRANS_RF3_DEMOD_RFMON.We cotinine to optimize these while in ASQZ.
Naoki adjusted FC1/2 and Sheila turned on FC ASC. IFO ASC wasn't working well but maybe SQZ angle was not best at the time.
In total I moved ZM4 and ZM5 ~500urad each. This is a lot more than the ~300urad previous yaw move.
 
We stayed in our okay alignment, range 145MPc, from 21:50:10 to 21:57:10UTC. See DARM and BLRMs attached. SQZ is good 100-500Hz but we seem to be injecting noise <100Hz (not confirmed), and SQZ is only at 3.5dB at high frequencies. Alignment SDFs accepted.
 
We had planned to take NO SQZ time and SCAN SQZ alignment before going to observing but lost lock instead.
 
When we relock we'll plan to run scan_alignment_fds and scan_sqzang as in wiki. As long as we have range 145MPc+ we'll go to observing for the night. Tagging OpsInfo.
Images attached to this report
Displaying report 1-1 of 1.