Looks like the CAMERA_SERVO had a CONNECTION ERROR for h1digivideo3 from 13:21:20-13:22:00 (taken out of observing during the error and taken back to OBSERVING at 13:22:01utc).

TITLE: 08/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

H1's been locked for almost 9hrs w/ a range of around 160Mpc.

On CDS Overview, there is a little RED for the SUSH2B front ends (attached, looks like CRC Sum errors).

Also happened to notice nuc30's H1 live DARM disappear for about 3-5 seconds at 1508utc.

TITLE: 08/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

- Arrived to an unlocked IFO, ran into the same issue as last night but was able to reconcile with these steps

- Back to NLN @ 1:27/OBSERVE @ 1:51 UTC

• The 102 Hz peak looks to be back for this lock
• Update: Peak seems to have dimished drastically after some time has passed, but it is still present (screenshot was taken around 2:55 UTC) - Tagging ISC

- EX saturations @ 3:47/4:04/4:22/4:35

- Lockloss @ 5:06

- Reaquired NLN unaided @ 6:09/OBSERVE @ 6:25

• Looks like there is still might be a 102 Hz feature for this lock as well (?), though not as apparent as the first lock from earlier today
• Also got a STAND DOWN alert ~6:10, but no new alerts came through on verbal and there were no recent events on GraceDB - screenshot of SD overview attached
• PI 31 ringups at 6:12 - successfully damped by the guardian

- EX saturation @ 6:36

- Setting H1 to auto and passing to Tony for the night

LOG:

No log for this shift.

Lockloss @ 5:06 - a short 3.5 hour lock, possible ASC ringup? Saw the ASC signals start to oscillate with growing amplitude on nuc29 leading up to the lockloss - scope attached.

Had some issues relocking after the lockloss, similar to last night, but has since been resolved. H1 has been locked and observing as of 1:51 UTC. Ground motion/wind low.

TITLE: 08/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY:

Just as Austin and I were chatting at the hand-off, H1 lost lock!  :(
LOG:

• 1741 H1 dropped out of Observing & taken back shortly after

TITLE: 08/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

- H1 has just lost lock as I am typing this...cause unknown

- SEI motion is a bit elevated in the EQ band, hovering around 0.1 um/s

Happened to look up and see a "Stand Down" state.  Did not receive any alerts for this.  The graceDB link for this lists this "GRB-SHORT" as NOTGRB.  Here's more info on this particular event (E432741):  https://gracedb.ligo.org/events/E432741/view/

PSL Report FAMIS report:
Laser Status:
    NPRO output power is 1.829W (nominal ~2W)
    AMP1 output power is 67.15W (nominal ~70W)
    AMP2 output power is 135.5W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN

PMC:
    It has been locked 20 days, 6 hr 1 minutes
    Reflected power = 16.33W
    Transmitted power = 109.2W
    PowerSum = 125.5W

FSS:
    It has been locked for 0 days 10 hr and 48 min
    TPD[V] = 0.9056V

ISS:
    The diffracted power is around 2.4%
    Last saturation event was 0 days 10 hours and 48 minutes ago

Possible Issues: None

H1's been locked for 8.5hrs.  At around 1630utc (930amPT) H1 took a step down in range.  There was also a brief drop out of Observing due to the Squeezer (noted earlier).

At 17:41:44, H1 was dropped out of OBSERVING...after quickling taking OBSERVATORY_MODE to "COMMISSIONING", H1 was ready to go back to OBSERVING at 17:42:21.

Using the Guardian Control command, there was a brief SDF diff due to syscssqz.  I am not sure how to find which channel dropped us out.  I ran guardctrl on Squeezer nodes and a few other guardian nodes, but could not find the culprit.  (see attached).

Sat Aug 26 10:10:48 2023 INFO: Fill completed in 10min 44secs

TITLE: 08/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

H1's been locked 4hrs.  H1 range continues at increased value of 150Mpc as was for the lend of the last lock.  There was a Labs Dust alarm needing to be acknowledged (it had been OK for last3hrs).  Winds slowly beginning to pick up.

Hanford site road work continues on a Saturday on Route10 (crack sealing) and I was turned around and had to take the long way around to get to work (this work was normally M-Th 7am-3pm, but they've been working Fri & Sat this week).

TITLE: 08/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

- EX saturation @ 11:10/1:48/2:13 UTC

- Lockloss @ 5:56 - new record for a O4 lock at LHO - 60:29!

- Issues getting light on the ALS Y PD - might be related to the chiller issue we had earlier today?

• Attached witness sensors and slider values over the course of the past day - does not seem to be much drift (the most recent movement was from me trying to find light on the PD)
• The ALS Y guardian is showing a ReflPD A/PDH error
• Looking on the trouble shooting wiki, Tony and I tried running the dither align script (under TMS pointing/dithering) to try and get some power on the PD - no luck
• Attaching oplevs - looks like there is movement/drift - mostly in pitch - scope attached
  • Tried moving the sliders back to their original oplev positions from ~2 days ago - still no light
• Followed Camilla's steps here, found in the wiki to be used "if there is no image on the ALS camera", still no luck
• At this point, we're out of ideas and will be contacting a commissioner to help troubleshoot, stay tuned for a further alog

LOG:

No log for this shift.