This is a continuation of the work discussed in 78734. 

After H1 lost lock this afternoon, I took the opportunity to do a quick RefCav alignment tweak since the TPD was showing the transmission was low at around 680mV. Using the two picomotor-controlled mirrors in the FSS path, mostly adjusting in pitch, I was able to improve the signal from about 680mV to 870mV. More of an increase than I was expecting, but this should be good to last until the PMC is swapped out on Tuesday (where this alignment may need to be done again). I suspect I could've spent more time to improve this further, but I stopped here so as not to delay IFO locking any longer.

Lockloss @ 23:39 UTC - link to lockloss tool

Locked for 26 minutes. No obvious cause, but I see the ETMX motion about 100ms before the lockloss this time.

I'm going to take this opportunity to do a quick FSS RefCav alignment adjustment so that it can hopefully make it until Tuesday when we swap out the PMC.

TITLE: 06/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Just got back to low noise after we had a lock loss that ended a 15 hour lock. Relocking was fully auto and it didn't even run an initial alignment.
LOG:

• 2215 Lock loss
• 2315 Observing                                                                                                                                 

TITLE: 06/30 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 lost lock about an hour ago but is relocking well; so far up to TRANSITION_FROM_ETMX.

• Wind is low, microseism starting to trend upwards
• All other systems nominal

Lockloss1403820932

Ending a 15 hour lock. This lock had the ETMX wiggles as well, but they happened almost a second prior to lock loss and were larger than I have seen.

FAMS26260

Laser Status:
    NPRO output power is 1.821W (nominal ~2W)
    AMP1 output power is 67.15W (nominal ~70W)
    AMP2 output power is 137.3W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 32 days, 23 hr 34 minutes
    Reflected power = 22.75W
    Transmitted power = 105.2W
    PowerSum = 127.9W

FSS:
    It has been locked for 0 days 11 hr and 42 min
    TPD[V] = 0.6936V

ISS:
    The diffracted power is around 2.0%
    Last saturation event was 0 days 11 hours and 43 minutes ago

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

Sun Jun 30 10:09:55 2024 INFO: Fill completed in 9min 52secs

TITLE: 06/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: Locked for 7.5 hours, noise and range look okay.

TITLE: 06/30 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Three locklosses this shift, all with unknown causes but only two with the ETMX motion before that we've been seeing. Recovery from each was fairly straightforward, however the ALS-X PLL continued to be problematic and unlock when trying to recover from the first lockloss.

• 23:57 - Lockloss - alog78748
  • Having trouble getting past DRMI due to ALS-X PLL repeatedly unlocking
  • 00:51 - Lockloss during TRANSITION_FROM_ETMX, unsure why
• 03:41 - Observing
• 04:15 - Lockloss - alog78751
• 05:13 - Observing; automated relock
• 06:00 - Lockloss - alog78753
• 07:01 - Observing

H1 has been observing for 1 hour.

LOG: No log for this shift.

Lockloss @ 06:00 UTC - link to lockloss tool

Locked for 49 minutes. No obvious cause; larger ETMX motion right before the lockloss this time.

Lockloss @ 04:15 UTC - link to lockloss tool

Locked for 38 minutes. No obvious cause, but I see the familiar small ETMX hit almost a half second before the lockloss.

We lost lock just as I was beginning  HVAC shutdowns to take advantage of the nearly 160 Mpc range. When we regained lock, the range was only about what it was for my last shutdown (77477), so I will defer.  Here are the times for what I did do:

Lockloss @ 23:57 UTC - link to lockloss tool

Ends lock at 6 hours. No obvious cause, and I don't see the ETMX motion prior to this lockloss as we've seen in the past.

TITLE: 06/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: One lock loss with a straight forward relock, and then a delayed calibration measurement. We've been locked for 5.5 hours.
LOG:

• 1655 Lock loss
• 2106-2133 Out of observing for coordinated calibration

Calibration sweep taken today at 2106UTC in coordination with LLO and Virgo. This was delayed today since we were'nt thermalized at 1130PT.

Simulines start:

PDT: 2024-06-29 14:11:45.566107 PDT
UTC: 2024-06-29 21:11:45.566107 UTC
GPS: 1403730723.566107

End:

PDT: 2024-06-29 14:33:08.154689 PDT
UTC: 2024-06-29 21:33:08.154689 UTC
GPS: 1403732006.154689
 

I ran into the error below when I first started the simulines script, but it seemed to move on. I'm not sure if this frequently pops up and this is the first time I caught it.

Traceback (most recent call last):
 File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 314, in _
bootstrap
   self.run()
 File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 108, in r
un
   self._target(*self._args, **self._kwargs)
 File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 427, in generateSignalInje
ction
   SignalInjection(tempObj, [frequency, Amp])
 File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 484, in SignalInjection
   drive.start(ramptime=rampUp) #this is blocking, and starts on a GPS second.
 File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/awg.py", line 122, in start
   self._get_slot()
 File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/awg.py", line 106, in _get_sl
ot
   raise AWGError("can't set channel for " + self.chan)
awg.AWGError: can't set channel for H1:SUS-ETMX_L1_CAL_EXC