I replaced the viewport cover I had removed in case someone needs the laser safe state in the morning.
Lockloss @ 02/18 00:06 UTC after almost 5.5 hours locked
TITLE: 02/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.59 μm/s
QUICK SUMMARY:
Currently Observing at 151Mpc and have been Locked for 4:20 now. Wind is very low and ssecondary microseism is very high, but not too bad and turning slightly back downward.
TITLE: 02/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Only one lockloss this shift, but spent time this morning out of observing to troubleshoot SQZ issues, details of which can be found in alog82853. Fortunately, it seems to have helped and H1's range is higher than it's been in a few days.
LOG:
FAMIS 31073
Only event of note I can see is PMC REFL suddenly had a rise of about 0.5W starting 4 days ago that has almost leveled out.
Forgot to add this comment last week, my apologies. The PMC Refl rise appears to coincide with a temperature change in the enclosure and LVEA. Seen on the Weekly Environment plots, there is a clear downward change in all 4 temperature sensors in the PSL enclosure Laser Room (TBLN, TBLS, ACN, ACS), and a clear drop and levelling out of the temperature in the enclosure Anteroom and the PSL LVEA sensor (sits on the exterior PSL enclosure wall between the enclosure and HAM1). This is also seen on a couple of items exposed to ambient temperatures, namely the NPRO laser pump diodes (in the NPRO laser head in the enclosure Laser Room) and the LVEA Control Box (in the PSL rack outside of the enclosure). On the Weekly Cooling set of plots, a clear change in these 3 channels (*_NPRO_LD[1/2]TEMP, *_CB1_TEMP) is seen coincident with the temperature change witnessed by the various PSL temperature sensors.
Seeing this, we attempted a brief alignment tweak of the PMC beam from the Control Room (theory being that since the change in PMC Refl coincides with a temperature change, maybe an temperature-induced alignment shift caused the increase in PMC Refl). Unfortunately we saw no change in PMC Trans with an alignment tweak.
Lockloss @ 17:04 UTC - link to lockloss tool (late entry for the lockloss this morning)
Happened while Camilla and I had H1 out of observing to troubleshoot SQZ (see alog82853), but very unlikely anything we were doing contributed to the lockloss. This looks like another of the newer ~11Hz oscillation locklosses that Oli discusses in alog82847.
H1 returned to observing at 18:53 UTC (but later dropped again for more SQZ troubleshooting, see above).
Ryan S, Camilla
Corey 82849, Ryan and I have had some issues with SQZ this morning. Corey adjusted the SHG temp to get enough green power to lock the OPO but after that the SQZ and range was bad. FR3 signal and FC WFS were very noisy.
Ryan tried to take SQZ out, checked OPO temp (fine), reset the SQZ angle from 220deg back to a more sensible 190deg and then put SQZ back in again but he couldn't get the FC to lock. Followed steps in the SQZ wiki to touch up FC1/2 alignment and got H1:SQZ-FC_TRANS_C_LF_OUTPUT to >120, plot. but we still were loosing the FC at TRANSION_TO_IR_LOCKING. THE FC also seemed unstable when locked on green. While we were troubleshooting, the IFO lost lost. Unsure if this is an ASC issue, FC_ASC trends attached (POS for Y and P were moving much more than usual), SQZ ASC trends (ZM4 PIT changes alot).
After the lock loss, the SQZ_FC seemed to lock stably in green with H1:SQZ-FC_TRANS_C_LF_OUTPUT = 160. Plot. This is higher than usual and it's not clear what changed!
Ryan mentioned that something happened to Oli at the weekend where the range was bad but SQZ unlocked and re-locked and it came back good, plot, but this seemed to the the OPO PZT changing to a better place (we know it likes ot be ~90 rather than 50s).
After relocking, everything was fine but the FC ASC wasn't turning on as the threshold was too low, 2.5. Ryan decreased H1:SQZ-FC_ASC_TRIGGER_THRESH_ON from 3.0 to 2.0, this has been slowly decreasing, maybe as we decreased the OPO trans from 80uW to 60uW last week. Plot. Ryan accepted in sdf and then checked SQZ_MANAGER, SQZ_FC, sqzparams to check this isn't set in GRD.
FC ASC lower trigger threshold accepted in SDF. It is not set anywhere by Guardian nor is this model's SAFE.snap table pushed during SDF_REVERT.
After a while, Camilla and I again dropped H1 out of observing as even after thermalization, BNS range and squeezing weren't looking good. We decided to reset the SQZ ASC and angle in case they were set at a bad reference point. I took SQZ_MANAGER to 'RESET_SQZ_ASC_FDS' and adjusted the SQZ angle to optimize DARM and SQZ BLRMS. To reset the angle servo here, I adjusted SQZ-ADF_OMC_TRANS_PHASE to make SQZ-ADF_OMC_TRANS_SQZ_ANG oscillate around 0 (ended with a total change of -10deg), then requested SQZ_MANAGER back to 'FREQ_DEP_SQZ' to turn servos back on, and finally accepted on SDF (attached) to return to observing. It's been about 20 minutes since then, and so far H1 is observing with a much better steady range at around 160Mpc.
What happened that needed the ADF servo setpoint to be updated with a different SQZ angle? Investigation is ongoing.
Attaching the plot from after Corey got the SQZ locked and it was bad, you can see it looks like one of the loops was oscillating, plot attached. Compare to normal SQZ plot.
Mon Feb 17 10:13:43 2025 INFO: Fill completed in 13min 40secs
TCmins [-49, -48C] OAT (+2C, 36F) DeltaTempTime 10:13:43
TITLE: 02/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 2mph Gusts, 0mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.64 μm/s
QUICK SUMMARY: H1 has been locked for just over an hour but only observing for about half that as SQZ was having issues locking (see Corey's alog).
1452utc (652ampdt): Wake up call due to No Squeezing.
SQZ Symptoms & Solution:
It's been about 20min since we went back to Squeezing, but it appears the adjusting of the SHG TEC Setpoint Temperature made squeezing possible, but now the range did not improve at all. Left a note for the Day Shift in mattermost.
TITLE: 02/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Currently relocking and in ENGAGE_DRMI_ASC. After we lost lock right at the end of Ryan's shift, we were able to get back up relatively easily after I ran an initial alignment. We got knocked out by an earthquake though, and we just finished running another initial alignment. The only difficulty in getting relocked for me has been ALSX and Y - they've still been liking to drop out every once in a while, even right after an initial alignment.
After trying and failing to improve squeezing earlier today (two locks ago) with Ryan, squeezing (and subsequently range) also wasn't great when we got relocked this last lock. However, an hour in, we dropped out due to the SQZ filter cavity unlocking, and when it relocked, squeezing was back to being around -4db. Not sure what was changed there, but it got us back to around 155Mpc, which was very appreciated, even if it's not an amazing range.
LOG:
00:49 Lockloss
- Started an initial alignment since ALS flashes didnt look good and I knew there would be issues with ALSY dropping out
02:08 NOMINAL_LOW_NOISE
02:11 Observing
02:57 Out of Observing due to SQZ FC unlocking
03:01 Back into Observing
05:16 Lockloss
- Ran an IA
I was looking at the lockloss sheet and noticed that this weekend, there were three locklosses that were similar to each other. Ryan Short noted one in an alog a couple days ago: 82809.
The locklosses look similar to what we sometimes see when we lose lock due to ground motion from an earthquake or wind, but in all three cases there was no earthquake motion, and the wind was below 20mph. There will be an 11 Hz oscillation starting about 1 second before the lockloss, and it can be seen in DARM, all QUADs, MICH, PRCL, and SRCL.
Lockloss times:
There was another instance of a lockloss that looked just like these on February 7th 2025 at 05:47UTC as well.
Some more of these weird locklosses from the last day:
Lockloss @ 02/17 05:16 UTC after 3 hours locked due to an earthquake. Earthquake didn't shake the ground too hard, but we still lost lock becuase secondary microseism is also really high.
TITLE: 02/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 140 Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 9mph Gusts, 5mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.53 μm/s
QUICK SUMMARY:
Currently Observing and have been Locked for 3 hours. Our range was bad, which we figured was due to squeezing being way worse than last lock and not getting better with thermalization. We popped out of Observing to adjust squeezing but it was giving us issues and we had trouble getting IR to lock (see Ryan's alog). Finally were able to get the filter cavity locked by adjusting the OPO temp, but our squeezing was still bad, so Ryan adjusted the OPO temperature again and got a tiny bit of squeezing out (-1db), but not much. Range is basically back to where it was before all this.
Ryan's alog: 82840
This lockloss also has the strange oscillation in many LSC channels + QUADs right before the lockloss that was noted in 82847
03:05 UTC OBSERVING
Looking at front room ndscopes+QUADs/DARM in the minute leading up to LL: ndscope1
Oscillation seen by QUADS, ASC-INP1_P_IN, and ASC-CHARD_P_OUT
NOT seen in power recycling gain or circulating power (like the LL that happens after this one - 82865)
Looking at QUADS/DARM and LSC signals in the second before the LL: ndscope2
Seen by all QUADS, DARM, and LSC signals