Lockloss 08/25 @ 23:41UTC due to 6.9 earthquake in Tonga. We were knocked out really quickly by the S-wave and the R-wave won't be arriving for another ~30 mins, so it might be a while before we're back up.

For FAMIS 26286:
Laser Status:
    NPRO output power is 1.829W (nominal ~2W)
    AMP1 output power is 64.59W (nominal ~70W)
    AMP2 output power is 137.5W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 5 days, 19 hr 56 minutes
    Reflected power = 21.01W
    Transmitted power = 105.7W
    PowerSum = 126.7W

FSS:
    It has been locked for 0 days 7 hr and 40 min
    TPD[V] = 0.6499V

ISS:
    The diffracted power is around 2.3%
    Last saturation event was 0 days 6 hours and 33 minutes ago

Possible Issues:
    AMP1 power is low
    PMC reflected power is high
    FSS TPD is low

Sun Aug 25 08:10:32 2024 INFO: Fill completed in 10min 28secs

TITLE: 08/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 141Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

H1's been lockwed for 3.5hrs (looked like Tony got a wake-up call during h1 downtime, but had minimal intervention).  BS camera is operational.  Seismically fairly quiet for the last few hours (notable noise was corner station 3-10Hz had elevated levels from 1210-1300utc, attached).  No Alarms.

With H1 returning to Observing yesterday, within hours, H1 returns to join L1 & V1 with the gravitational wave candidate, S240825ar (H1's last contribution to a gravitational wave candidate with L1 & V1 was back on July 16th for S240716b.)

TITLE: 08/25 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 139Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently Observing and have been Locked for over 10.5 hours. Shift has been quiet. Since Corey said relocking this morning was hands-off and smooth, so hopefully that'll continue through the night.
LOG:

23:30 Observing and have been Locked for over 5 hours
00:02 Verbal: "WAP on in LVEA, EX, EY" (Last time this happened that I could find was mid-May 77860)

Currently Observing and have been Locked for 9.5 hours. Since getting back to Observing we haven't had any issues!

TITLE: 08/24 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 135Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 15mph 5min avg
    Primary useism: 0.12 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Observing and have been Locked for 5.5 hours!

Completed tasks:

Calibration (unthermalized): 79676

Calibration (1.5 hours in): 79689

Calibration (fully thermalized): 79691

LSCFF measurements: 79693

TITLE: 08/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Have had the BS camera die on us a couple times in the last 24hrs (this requires contacting Dave to restart the camera's computer--atleast until this camera can be moved to another computer), and so the beginning of the shift was restoring this and also figuring out why H1 had a lockloss, BUT did not drop the Input Power down from 61W to 2W.

After the camera issue was fixed, ran an alignment with no issues, and then took H1 all the back to NLN also with no issues.  

Then completed taking Calibration measurements after 1.5hrs and 3hrs.  Oli also ran LSC Feedforward measurements......

Then there was ANOTHER BS Camera Computer Crash!  Dave brought us back fast.  

Now back to OBSERVING!
LOG:

• Arrived to see that H1 was stuck at ADS TO CAMERAS, BUT had had a lockloss.  ALSO: Input Power did not change after the lockloss---so, 61W was being dumped to MC REFL!  Mystery as to why this happened.  I took H1 DOWN and this took care of the High Power onto MC REFL.  
• 1611-1641 INITIAL ALIGNMENT
  • x+y green arms were way out and needed INCREASE FLASHES
  • Everything else went fine.
• 1635 Noise hunting in Mechanical Room off and on today (robert)
• 1643-1728 Locking H1 & then getting stuck at ADS TO CAMERAS (same as last night)---Noticed that the CAMERA SERVO had stalled and noted issues with CAM1 Pit & Yaw.  Posted this onto LIGO Chat and Ryan Short mentioned it's probably due to the BS' camera.  Sure enough it had died!
• 1800-1807 Contacting Dave to restart the BS camera
• Save & Loaded LASER_PWR.py  (It had already been edited for the change to 61W.)
• 1812 NLN for H1
• 1946-2015 Ran Calibration after H1 was locked for 90min.
• 2042 H1 back to OBSERVING (1st time since July12th!)
• 2113-2301 Out of Observing:  Running Thermalized Calibration + LSC Feedforward measurements
  • Since the BS Camera happen to die during Oli's last LSC FF measurement for PRCL, they ran it again.
• 2226 - 2243 BS Camera was down again!  (Dave brought it back for us pretty fast.)
• 2301 OBSERVING

3.5 hours into our lock we took LSCFF measurements. Files can be found in /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/ and are basically the name of the measurement template+'_20240824', but I'll list their filenames below anyway.

MICH Preshaping (run as 30 fixed averages)
MICHFF_excitation_ETMYpum_20240824.xml
MICHFF (30 accumulative averages)
MICH_excitation_20240824.xml

SRCL Preshaping (32 accumulative averages)
SRCLFF_excitation_ETMYpum_20240824.xml
SRCLFF (30 accumulative averages)
SRCL_excitation_20240824.xml

PRCLFF (30 accumulative averages)
PRCL_excitation_20240824.xml

For H1 recovery road back to Observing, it was requested to take calibrations (1) immediately at NLN, (2) 1.5hrs after NLN, and then the (3) standard one of atleast 3hrs after NLN.

Measurement NOTES:

• Following instructions (link)
• H1 at NLN for atleast 1.5hrs.
• Calibration_Monitor medm screenshot is attached
• 2113 Out of Observing, ISC LOCK to NLN_CAL_MEAS & Observatory Mode to CALIBRATION
• 2114- 2119  Broadband measurement run
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/
• 2121-2144 Simullines measurement
  • gps START time:  GPS: 1408569700
  • gps END time:  GPS: 1408571082.513554
  • Files writtten to subfolders here:  /ligo/groups/cal/H1/measurements

Now that this is complete, we can cross this off the white board, and Oli immediately started running LSC Feed Forward measurements.

(Corey, Oli, RyanS [remote], Sheila [remote])

After roughly 6-weeks (Jul 12, 2024), H1 made it back to Observing (at 2042utc Aug24) to join L1 & V1 (albeit briefly since we needed to drop from Observing to take a thermalized calibration measurement + LSC FeedForward offset measurement).  H1 range is only about 140Mpc.

We are running with input power setting of 61W (to help avoide PI Mode24). 

To get to Observing, SDF Diffs needed to be ACCEPTED (see attached image with all the diffs).

For H1 recovery road back to Observing, it was requested to take calibrations (1) immediately at NLN, (2) 1.5hrs after NLN, and then the (3) standard one of atleast 3hrs after NLN

Measurement NOTES:

• Following instructions (link)
• H1 at NLN for atleast 1.5hrs.
• Calibration_Monitor medm screenshot is attached
• 1946-  ISC LOCK to NLN_CAL_MEAS & Observatory Mode to CALIBRATION
• 1946-1951 Broadband measurement run
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/
• 1952-2015 Simullines measurement
  • gps START time:  GPS: 1408564372
  • gps END time:  GPS: 1408565741.455985
  • Files writtten to subfolders here:  /ligo/groups/cal/H1/measurements

h1cam26 (BS) was restarted Thur 12:56 PDT after stopping late Wed 22:23. It only lasted less than two days and stopped responding Fri night at 22:30.

I restarted it again this morning at 11:07 following the standard procedure.

H1 is currently stuck at ADS TO CAMERAS (same as last night); see attached screenshot.

CAMERA SERVO node has messages of:

"ASC-CAM_PIT1 (& YAW1)_INMON is stuck!  Do Not Advance!"

Will do some searching to see what the issue is. 

NOTE:  Sheila's alog that there was mention of PIT1 being updated.

Arrived to see H1's ISC LOCK at ADS TO CAMERAS, but no signals on the front ndscope and no DARM line on DARM FOM.  SUS  Violin screen looked like everyone was OFF or not damping.   Eventually, the telltasign was MC Trans was flashing (so IMC was NOT locked) and MC REFL was really bright (with OPS Overview saying the PSL was at ~61W.

OK, here's a rough timeline for last night (used the handy "guardctrl log" command line command which Camilla was able to help me find; I also attached the guardtrl log for all notes for the minute around the lockloss):

• 537utc (1037pmlocal):  ISC_LOCK at ADS TO CAMERAS
• 0718 Verbal Alarms:  "H1 Assistance Required"
  • Not really sure what this was about....I'm guessing its related to Automatic operations because H1 MANAGER guardian was STALLED and mentioned the "assistance required"
• 09:10:45utc On Verbal Alarms we get saturations for many SUS and PDs
  • (this is probably when the lockloss occured)
  • Fast Shutter closes (Camilla mentioned this, so I immediately checked that.)
  • IMC loses lock
  • PSL Power remains 61 Watts
• 1453 GRD IFO taken from AUTO to MANAGED
• 1500 ISC LOCK eventually taken DOWN and everything looks somewhat normal.

I will probably run an Initial Alignment and return to the game plan of locking H1 and running measurements at NLN.

Sat Aug 24 08:13:53 2024 INFO: Fill completed in 13min 49secs

TITLE: 08/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: n/a
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

Trying to figure out the state of H1, it was in automatic operation and is currently stuck at ADS_TO_CAMERAS since before 11pm local.  (My main confusion is why I don't see any signals on nuc 30 (no DARM signal and no signals on the PRMI.sb ndscope.  I also don't see Odd.)

WAIT. 

OK, H1 is DOWN, but Guaridian seems to think it's trying to get thru ADS to Cameras and Inject Squeezing.....my realization is that MC Trans was flashing!  Then I saw that MC Refl is really bright (I'm assuming close to the 60.8W Guaridan had taken us to via ISC LOCK.