TITLE: 05/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
SHIFT SUMMARY: Today has been busy with recovery efforts for H1. The day started with touching up alignments to get DRMI locked again with some stability, although buildups didn't look as good as they have in the past. We discovered that we could not switch to the POP PD used for DRMI 3F without losing lock, which prompted a more thourough investigation into potential chamber motion (see alog 69924 for more information). After restarting models for HAMs 2, 3, 4, 5, and 7, restoring alignment for PR3, and relocking green arms, Shiela and TJ are off to realign and recover the ALS beatnotes on ISCT1. Please see other alogs from today (some to-be-written) for more detail.

LOG:

AM control room team: RyanS, TJ, Sheila, Keita, Vicky...

Trended alignment of PRM, PR2, PR3 over last 2 weeks. It is unusual to change PR3 alignment but recently we've had to touching PR3 to get PRMI locked (69751, 69917, 69924, 69903): 3urad in last 2 weeks. Top right pink trace attached.

Sheila noted that the the POPAIR and ALS (green) beat notes were reducing and then being brought back by PR3 moves (1st t-cursor). ALS beatnote realigning on ISCT1 in last 2 days (2nd t cursor, alogs 69897, 69897) brought back green comm/diff beat notes but not POPAIR.  Sheila/Keita/Vicky noted this suggests something common on the green + IR path is drifting.

For newer information including HAM yaw motion, see TJ's alog 69924 .

Quick summary: We've been able to get to DRMI_TO_POP and can now engage most of the DRMI ASC loops. Jim and Jeff are currently looking into an issue with the HAM yaw motion that might help explain the optic moves that we've had to make.

• PRMI will lock breifly but then quickly lose lock. This was from the ASC PRC1 gain going from 12 to 5, we bumped this up from 5 to 8 in lscparams for now. Might need to revert later.
• Tried walking PR3 in the direction that it has been moving (in the -yaw) and compensate with PR2, this didn't seem to help. We moved suspensions back to our best buildup position within this movement.
• We managed to lock PRMI and then DRMI with this alignment. We kept DRMI ASC off because the error signals were not well centered, and attempts to center were not sucessful. Most noteably INP1 and PRC2, but others were off as well. We decided to try moving past DRMI with only the MICH ASC loop engaged. We then made it up to DRMI_ON_POP, so past a CARM reduction and technically made it onto POP @1f.
• We've now repeated this a few times with little or no alignment changes, so we will step through the state by hand to find if there is an exact spot that it is failing.
• Jim had a look at the HAM CPS residuals and noticed that they have been exponentially driving away for the last ~45 days (plots attached). This might line up with the adjustments we've had to make in the input arm. Jim and Jeff are currently investigating.

While doing some manual checks of temperatures Fil and I again noticed the diffrent noise around HAM 7 area that has been heard before.  We took the time to track it down.  The vacuum pump for the dust monitors located on the mezzanine in the mechanical room was vibrating putting a loud harmonic on it's usually loud sound. Fil and I put foam and different isolating feet on the pump and the noise was gone.

During our locking troubles over the last few days, the LVEA temperatures have been in flux from fan flow changes. The temperatures have definitely stabilized over the last 20 hours, but they are higher than before these tests, zone 4 in particular. Just to rule out any rubbing we ran Jenne's ipynb that checks the top mass OSEMs with a reference time (alog). I tried a few different reference times with the same results - I didn't see any evidence of rubbing on these plots. Plots attached.

Edit: The pdf didn't have all the pages and I've struggled to get them all in and have the alog accept the upload. The currrent attachment has sort of visible plots, but if you're really interested it might be better to go open the notebook up yourself with these already saved.

We have been making progress towards recovering H1 to full lock. This morning, after running an alignment then manually touching several optics, including walking the beam between PR3 and PR2, we were able to lock DRMI with decent-looking buildups. So far, we've been bypassing DRMI ASC and able to reach DRMI_TO_POP before losing lock. Troubleshooting continues.

Fri May 26 10:06:16 2023 INFO: Fill completed in 6min 16secs

As suggested by Dan Brown, I checked if the HWS could see any ITM beam spots movement during the May 10th/11th temperature excursion alog 69525. I could see nothing.

The attached plots of ITMX and ITMY show (L to R) the two locked before temperature changes and the two locks during temperature change. ndscope attached. HWS ref at at 76W input power compared to show time is 5 minutes after. Lock during the change was 50 minutes long. Videos didn't show anything either.

TITLE: 05/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: H1 is unlocked, sitting in LOCKING_ARMS_GREEN. I'll touch up flashes and see if I can get anywhere with locking this morning.

• CDS, SEI, SUS all okay
• All dust monitors working and levels okay
• No alarms overnight
• Temperatures in the LVEA appear to have stabilized

Continuing w/ PR3 move recovery.  Still having issues with PRMI.

Ran a Manual Alignment 2-3 times after TJ did one.  

• Once again INPUT ALIGN was finicky.  There were flashes on the order of 0.5-0.8 for TR_X, but no locks.  I tried PR2 yaw moves to try and improve alignment/flashes, but this did not help.  I also tried small moves w/ IM4, but that had no effect.
• Quit INPUT ALIGN since it was not working out.  
• Continued with other alignment steps (except green arms since they are fine).
• SRC Align continued to not work, so I did an SR2_ALIGN & OFFLOAD and then aligned SRM by hand.
• Then took a look at PRMI, but it was lifeless again (on ndscope) and misaligned on yaw via AS_AIR camera.
• Currently taking INPUT_ALIGN to ACQUIRE_XARM_IR
  • Sheila had some checks I could do here:  watch AS_AIR at this step to get an idea of how input alignment is misaligned (so would have idea of which way to point PR2)
  • Also could double the gain (i.e. from 0.04 to 0.08) for H1:LSC-XARM_GAIN to help Xarm lock (and restore gain after optimizing alignment)
  • ......But with Sheila on Teamspeak, she noticed a dark offset which was a bit off.  She fixed this by-hand and then TR_X immediately locked.  She touched up some of the alignment and then we let ALIGN IFO take over.  
  • Finally INPUT ALIGN completed successfully!
• Now going to rerun PRC ALIGN, MICH BRIGHT and attempt SRC (if latter doesn't work, will skip).
• Then try PRMI again and check for improvements.

Daniel made model updates to h1ascsqzifo this Tuesday, adding in 2 new signals to the ASC trigmatrix (+omc_trans_rf3, +hd_diff_rf3), and he also added in model blocks to run ADS. For all the SQZ-OMC ADS new model parts, I've just accepted and monitored them (all gains are 0, etc).

Today I changed our SQZ AS42 ASC trigger to use the OMC_TRANS-CLF beatnote now available in the ASC trigger matrix, SQZ-OMC_TRANS_RF3_Q. This signal has much better SNR of the squeezer in omc transmission than the QPDs AS_A/B_RF42_SUM's we were triggering on before (green middle trace). Settings and signals attached in this screenshot, and saved to SDF. I don't think this should cause problems for locking later, but I'll watch out for it.

TITLE: 05/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
SHIFT SUMMARY: We are still trying to get our comm/diff beatnotes and PR3 alignment understood. Sheila and Ryan S went on table this morning (alog69907) and maximized our beatnotes with our old PR3 position (Yaw slider 148.5). We struggled to get DRMI locked well after that. Sheila noticed that our green qpd offsets and ITM camera offsets were set back to the old values, incorrect values, so they might have not been saved in SDF and then reverted. Sheila and Ryan made a second trip to the table and retouched the alignment with the correct qpd offsets, camera offsets, PR3 settings, and aligned green arms. Trying to lock again but it looks like we need another initial alignment, running that now.
LOG:

TITLE: 05/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

TJ was at early steps of locking (noticed some odd offset sweeps for COMM/DIFF while FINDING IR).  PRMI does not look very good sadly and he's moving to CHECK MICH FRINGES.

Sheila, Ryan S, TJ

This morning we continued the ISCT1 and PR3 alignment from 69903 , 69897 ,  69857. 

TJ reverted the X arm green references to what they were yesterday morning, seen snapshot here, and re-ran intial alignment of the X arm.  Ryan S and I went to ISCT1 and saw that the beatnotes weren't well aligned, but the whole table alignment was better than what TJ and I found yesterday.  We toggled PR3 between 151.6 and 148.5 yaw slider, and saw that the ISCT1 alignment was sort of close to OK for both of these, such that beams were clearing their appertures and making it to the diodes they should have without clipping. 

This means that after our table realignment yesterday, the table was in a sort of OK alignment (beams not totally missing their optics) for 4 configurations: both of the green arm alignment set points and both the PR3 pointings.  This means that the table alignment that TJ and I did yesterday fixed some gross misalignment that wasn't due to either of those things, (it has been a long time previously since the alignment on table was fixed up). 

From the control room TJ, Ryan and I, with PR3 set to 148.5 yaw slider (setting for locks yesterday), adjusted PR2 to lock the X arm in IR, ran the WFS for INPUT align, and did a MICH bright alignment.  Ryan and I returned to the table and moved the bottom periscope mirror to improve the alignment of the Y beam onto the trans diode, which allowed TJ to lock the Y arm in green and run inital alignment for that.  In the meantime, Ryan and I adjusted the position of the X trans diode, and improved the COMM beatnote using the beatnote BS and the one upstream of it in the X arm path.  We eneded up with a COMM beatnote of 6dBm, which drifted down later when TJ re-ran inital alignment for the X arm and is now at -1dBm. 

After TJ finished the Y arm green inital alignment, and a MICH bright alignment, Ryan and I realinged the DIFF beatnote, which is now -7dBm.  TJ then completed the intial alignment steps we had skipped (PRC and SRC) and is now trying to lock DRMI.

TITLE: 05/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
SHIFT SUMMARY:

Lock#1

Couldn't lock PRMI, lockloss

Lock#2

Went right into an initial alignement, OM1 & OM2 were saturated during PRC in initial alignment

DRMI's lock didn't seem great on the buildups but the spot looked ok

OMC locked first try on its own

NLN @ 08:44, 30 ASC SDF diffs but they were all for the camera servos, I waited for ADS to converge for the camera servos to turn on (~ 16mins) which cleared these diffs

Observing mode @ 09:02 while we thermalize

Out of observing at 11:05UTC for a new FF filter test/measurement and then a calibration suite, new FF filter applied at 11:07UTC

I used Coreys template (/ligo/home/corey.gray/Templates/dtt/DARM_05232023.xml) which I had to enable "read data from tape" for it to run. Measurement started at 11:10UTC, finished at 11:12UTC. My DTT session then immediately glitched and crashed before I could save it, great... I restarted the measurement at 11:15UTC, finished at 11:16UTC. It wouldn't let me save it (error: Unable to open output file), but I added it as ref 27 on the previously mentioned xml file in Coreys directory but this might have not saved from that issue. I grabbed a screenshot of it.

I switched back to the old filters to take the calibration suite at 11:21UTC, I wasn't sure if we wanted them on or not for this, apologies if we did want them on.

Lockloss @ 11:25, possibly from PI29, but on NUC25s scope guardian appeared to be successfully damping it? It was tapering down when when the DCPDs saturated and we lost lock, it also coincided with a ground motion spike from that 5.5 from NZ. I then stepped down the EX ring heaters to 1.2 using the console commands Sheila provided in her alog.

Lock#3:

Yarms power was drastically lower after the lockloss and looked clipped on the camera, increase flashes ran twice and wasn't able to get it above 50%, I stepped in and still wasn't able to even get it to 80%. I gave guardian another shot after this and increase flashes ran another 2 times and was not able to get it, I tried again to lock it and was unsuccesful. Lockloss at LOCKING_ALS after some more rounds of adjusting and trying to lock.

Lock#4-11

ALS locklosses

Lock#12

Beatnotes aren't great, -19 & -20, I'm starting another initial alignment. Lots of SRM saturations during SRC align, trending SRMs OSEMs there doesn't appear to be any unusual motion in the past 20 hours.

After a suggestion from Betsy and Jenne, I check PR3 and it seem to have drifted a bit, I moved PR3 in yaw 0.8 microradians negatively which increased the COMM beatnote. I was able to lock ALS after this but got no flashes on PRMI so I started another initial alignment but it didn't do the SRC align correctly again, TJs going back to try and fix this.

Handing off to TJ

LOG: