TITLE: 01/02 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 0mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY: H1 has been locked for almost 12 hours.

• Wind is low, microseism steady under 90th percentile
• All other systems nominal

TITLE: 01/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Lockloss right before I got on shift, was relocked just intime for a small earthquake.

H1 has been locked for 2 hours and Observing.
Looking good for the rest of the night.

TITLE: 01/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 8mph Gusts, 5mph 3min avg
    Primary useism: 0.36 μm/s
    Secondary useism: 0.53 μm/s
QUICK SUMMARY:

Lockloss from Observing via a 4.7 Magnitude Earthquake out of Cobb Ca.

The Lockloss web services tool is still not working but I'll include the URL generated via the command :

lockloss plot 1419820776

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1419820776

The Lockloss spread sheet is missing this lockloss, I imagine when the Lockloss tool starts workign again it will be generated on the spread sheet.

TITLE: 01/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.30 μm/s
QUICK SUMMARY:

1:24 UTC H1 currently In Nominal low noise for 2 minutes and Observing 1:26 UTC.
uSeism is on the rise for the past few hours.

Out side of that everything looks great. I expect a quiet night.

TITLE: 01/02 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Quiet shift until H1 unlocked this afternoon. Relocking has been going smoothly except for a lockloss at the end of TRANSITION_FROM_ETMX a few minutes ago. Otherwise, not much to report today.
LOG:

• 22:39 - Lockloss (alog82073)
  • 23:08 - Starting initial alignment
  • 23:30 - IA finished, starting lock acquisition
  • 00:27 - Lockloss within seconds of LOWNOISE_ESD_ETMX (likely actually from end of TRANSITION_FROM_ETMX as seen before)

Lockloss @ 22:39 UTC - online lockloss tool is still down.

Ends this lock stretch at exactly 30 hours. No obvious cause, but looks like there's a small ETMX glitch within a second of the lockloss.

State of H1: Observing at 156Mpc

H1 has been locked for 27.5 hours; quiet day so far.

Wed Jan 01 10:04:06 2025 ALERT: Fill done (errors) in 4min 3secs

Gerardo manually cancelled the fill after TC-A flattened out at -58C (trip is -60C). The discharge line pressure reached 0.8 PSIG (trip is 1.0).

TITLE: 01/01 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 0mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY: Welcome to 2025! H1 has been locked for almost 23 hours.

• Wind is low, secondary microseism just above 50th percentile and starting to trend upwards
• All other systems nominal

TITLE: 01/01 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

01:12 UTC Superevent S250101k candidate!

2:04 UTC PI mode 29 has been slightly elevated  for the past 10 minutes. 
H1: SUS-ETMX_PI_ESD_DRIVER_OUT_RIGHT_MON seems like its being driven at close to it's maximum.
No verbal alarm announced yet and it doesn't seem to be causing any problems.


2:16 UTC SQZ Manager not in nominal state. Dropped from Observing.
SQZ_MANAGER dropped to LOCK_PMC  and took around 4 minutes to regain lock.

2:22 UTC H1 Back into Observing.


Checking back in on this PI mode 29  at 5:46 UTC PI Verbal Alarm still not alraming, but it doesn't seem to be negatively impacting the DCPD readouts, sensitivity,  and we've now been locked for 13 + Hours.

Happy new year!

TITLE: 01/01 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY:
H1 locked and Observing for 8 hours now.
All systems running smoothly, aside from a dust monitor.

01:12 UTC Superevent S250101k candidate!

TITLE: 12/31 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: H1 has been locked for almost 8 hours. After relocking automatically this morning, H1 has been observing consistently with the brief exception when PI24 needed damping.
LOG:

• 15:45 - ACE on-site
• 16:40 - H1 starts Observing
• 17:18 to 17:20 - Briefly dropped observing for PI24 damping
• 17:35 to 19:31 - Norco on-site to MX for CP6 fill, drove by corner station
  • Notable brief range drops from CS ground motion at these two times (tagging DetChar)
• 21:36 to 22:28 - RyanS to all CS buildings for walkthroughs
• 23:30 to 23:47 - Tony to MER for TCS chiller checks

FAMIS: 27805

CO2X was found at 30.0, I added 150ml to get it to right to the MAX line at 30.5.

CO2Y was found at 10.3, I added 150ml to get it to the MAX line at 10.7.

Side note:
I was up there checking for leaks and I saw this old looking goopy mess toward the corner of the mezzanine. It looks like it is from an old Hepi fluid leak. Tagging SEI.

FAMIS 31066

Starting about 4 days ago, the steady increase in PMC REFL power leveled out and appears to have turned around over the past day or so. I don't see anything here that immediately points to a reason for this. Otherwise, no major events on these trends.

Tue Dec 31 10:12:37 2024 ALERT: Fill done (errors) in 12min 33se

TC-A min was -65C which is exactly the trip temp, so the fill did not automatically complete. After about a minute at this level I manually cancelled the fill at 10:12.

TC-A started very high today, at +19C, so I anticipated there could be an issue with the fill. I have increased the trip temp to -60C for tomorrow's fill.

TITLE: 12/31 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY: H1 lost lock at 14:43 UTC, ending this lock stretch at just over 29 hours. The online lockloss tool has not been updating since 12/26 at 20:14 UTC (5 days ago), so I don't know of a cause yet, but I plan to look into it. H1 is currently automatically relocking and up to RESONANCE.

• Wind low, secondary microseism trending down to around the 50th percentile
• LAB2 DM still in error
• All other systems nominal

TITLE: 12/31 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Currently Observing at 160 Mpc and have been Locked for over 20.5 hours. A few minutes ago we got another superevent candidate! Looking nice in H1! The evening has been quiet with nothing needing to be touched by me!

I did notice a notification on SQZ_OPO_LR that says "CMB EXC is on", and looking at the channel it checks, it looks like SQZ-OPO_SERVO_COMEXCEN went from 0 to 1 around 09:57 UTC on 12/30, which is a bit after we got locked last night and while we were having the SQZ issues. There are no excitations listed on the test point or CDS Overview screens, so I am wondering if this is some error? Tagging SQZ
LOG:

05:41 Superevent S241231bg

1556utc H1 was taken out of observing due to PI24 ringing up (it was damped out within a minute), BUT....

Since we were out of Observing (and I had already gotten a workspace ready to work on the Squeezer), I wanted to try a "simple" Squeezer check (basically what Oli did with taking the Manager to DOWN and going back to FDS.

I thought I was close to FDS, because all of the sub-nodes went to NOMINAL states and then I believe the Manager would get to FDS, but then go to NO SQUEEZING.....Then I realized all their NOMINAL states were set for NO SQUEEZING! 

So I worked on transitioning all 8-nodes Nominal states for SQUEEZING, to work on squeezing, but the issue I ran into was that the OPO_LR node had trouble getting to LOCKED_CLF_DUAL due to "USERMSG 0: No pump ISS means injecting bad squeezing. Going DOWN."

--->This sounds like yet another different SQZ issue.  I did not have issues with the SQZ_FC as far as I could tell (also did not get to see the "leap second" issue RyanC noted last night).

At this point, I was stumped, but got a mattermost from Sheila saying she could help in a bit. So I switched all SQZ node Nominal states for NO Squeezing to get more Observing in the mean time.

SIDE NOTE:  The buisiness for transitioning SQZ Nominal States is not quick or trivial (atleast for my slow self).  While  transitioning nodes for Observing WITH Squeezing, I ran into a LOADING error for the OPO_LR node.  Eventually found that it was a typo in the wiki (for editing all the nodes I copied the state from the wiki into the node python files.  I discovered the wiki had a typo [or the state had a slightly different name int he past].  For OPO_LR, the wiki said to make the Nominal -> "LOCK_CLF_DUAL".  Eventually figured out from the log, that this name was wrong it is "LOCKED_CLS_DUAL".  At any rate, I updated wiki.  And now have more Nominal node experience...I think this is only my 2nd or 3rd time going through the buisiness of "editing nominal states" for observing.