Lockloss @ 01:12 UTC - link to lockloss tool

No obvious cause; maybe from suddenly higher winds? Gusts have recently hit close to 40mph and microseism is past the 50th percentile.

TITLE: 06/23 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY: H1 has been locked for almost 4 hours. After I arrived, the OPO pump ISS saturated and dropped H1 out of observing for 2 minutes after Guardian brought everything back. This strangely happened twice more before I decided to take SQZ_MANAGER to DOWN to try and reset things, and after doing that and bringing it back to FREQ_DEP_SQZ, things seem okay now.

• Wind is low but microseism is trending up
• All other systems nominal

TITLE: 06/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: RyanS
SHIFT SUMMARY:

Mostly straightforward shift, with a big Mexico earthquake in the middle and then we had some squeezer issues dropping us out of Observing in the last few minutes (Taking SQZ Manager to DOWN did the trick with fixing the loop of the squeezer going down).  And there was a superevent in the last few min, too! 
LOG:

• 1733 EQ Mode activated by M5.2 Mexico earthquake
• 1734 Lockloss due to earthquake
  • 1753 Seismic to Calm
  • 1758 Return to locking w/o running an alignment (since RyanS has been having luck during his shifts)
  • Eventually went for PRMI, but had a lockloss while ASC was offloading
  • Had issues with x-arm locking, so paused at Locking Arms Green a few minutes....then X did an Increase Flashes and this did the trick
• 1853 Seismic to Microseism (it has been slowly increasing up to the 50th percentile, but maybe the recent Mexico quake helped trigger transition)
• 1930 Back to Observing
• 2252 Started having issues with the Squeezer as ryan and I were doing the shift handoff (we are back to Observing).

This was an obvious & quick lockloss due to a 5.2 EQ in Mexico (looks like it took down L1 about 10min before H1).  Here in the control room:

• 1732 Incoming EQ alert on verbal
  • First seen on 1 of the Picket Fence traces as a yellow and then orange and red.
• 1733 Seismon activated
• 1734 LOCKLOSS & Observatory Mode marked for EARTHQUAKE
• On FOM of seismic signals velocity of ground motion went up above 1um/s very fast, but it is also dropping pretty fast.  So might try to relock at/before 1800utc.
• Willl hold here for a little bit and monitor seismic signals and will return to locking when the ground quiets.

Sun Jun 23 10:10:59 2024 INFO: Fill completed in 10min 56secs

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

GWISTAT has not been listing V1's Observing  status (been in "No Data" state for several days); yesterday the V1 operator mentioned they are aware and working on it.

H1's been locked, for almost 2.5hrs, but scanning Verbal Alarms, it said we weren't in Observing.  H1 GRDIFO was in the MANAGED state over night, so I took it to AUTOMATIC--this automatically popped H1 back to OBSERVING.  All that is understandable, but I guess I'm confused by the Range FOM (attached).  A quick glance would tell me H1 was observing since we have the H1 Clean trace (dark red) on the range FOM---maybe I'm not interpreting this correctly. 

NEVERMIND!!!   Since GRD-IFO was in MANAGED over night, for the quick lockloss which was automatically recovered from, the OBSERVATORY MODE was remained in OBSERVING after that lockloss.  I'm assuming the "H1 Clean Range" channel on the range FOM/nuc27 is non-zero when the OBSERVATORY MODE is selected to be in the OBSERVING state. 

So:

• 11:02-1436:  H1 should NOT be listed as OBSERVING, there was a
  • 1102-1214 Lockloss + Locking--which was completely automated AND had NO locklosses & took72min to get to NLN
  • 1214-1436 H1 current lock at NLN--where Intention Bit stayed in COMMISSIONING, but Observatory Mode remained in OBSERVING from previous lock.
• 1437: Intention Bit taken to OBSERVING.  (Segment plot from Summary page shows Intention Bit in Commissioning for last lock and jumping back to Observing this morning (attachment2), and this last one is showing "Operating Mode" (or OBSERVATORY MODE kept in OBSERVING a few hours over night, attachement3).

TITLE: 06/23 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Two locklosses this shift, one from an ITMY ISI trip and the other from an unknown cause. Most locking this evening was automated, at least.

• 23:56 - Started observing after locking DRMI by hand
• 00:07 - Lockloss from ITMY ISI trip - alog78595
• 01:08 - Started observing; automated relock
• 03:00 - Lockloss - alog78598
  • 04:23 - Lockloss in PREP_DC_READOUT from M6.0 EQ passing through
• 05:47 - Reached OMC_WHITENING, needing to damp violins
• 06:32 - Started observing

LOG: No log for this shift.

Lockloss @ 03:00 UTC - link to lockloss tool

No obvious cause. As usual with these, ETMX and LSC-DARM saw the first motion before lockloss.

FAMIS 26311, last checked in alog78477

All fans look largely unchanged from last check and all within range.

Lockloss @ 00:07 UTC - link to lockloss tool

Both stages of ITMY's ISI tripped, causing the lockloss. Some trends attached; looks like the GS13s and T240s saw a kick that ITMX did not. Unsure of the origin of this, but I was able to untip the WD and bring the ISI back without issue, and H1 is already relocking DRMI.

TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: RyanS
SHIFT SUMMARY:

Coordinated calibration run earlier & then a lockloss later in the shift was tough to recover from (ran an alignment immediately after the lockloss, but for locking, DRMI & PRMI looked bad.  When Ryan arrived he helped me tweak PRMI by hand (with huge pointing/alignment changes) to finally get flashes, and then PRMI locked!  And H1 is currently going to 60W).  Not sure why alignment didn't look good after an alignment.
LOG:

• 1830-1857 Out of Observing for Saturday CALIBRATION
• 2136 Lockloss:  There is a a spike around the LVEA near this time, but we also have had winds above 20mph (and gusts just under 30mph).
  • 2137-2204 Initial Alignment (Input Align took a while because of slow IMC & X-arm locking)
  • Several early locklosses after IA (at Green Arms and Check IR).
  • DRMI also looked horrible after the IA (so selected check mich fringes)
  • After CHECK_MICH FRINGES, PRMI looked bad, and ISC Lock immediately went to Check Mich Fringes again! :-/

TITLE: 06/22 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 13mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Corey is working on locking DRMI; he's ran an alignment and MICH_FRINGES has run, but buildups still don't look good. We'll keep working at it.

• Wind is elevated wiht gusts up to 30mph in the past couple hours
• Microseism is low
• All other systems nominal

Just completed the Saturday Calibration mesurement with L1 & V1.  H1's been locked 12hrs.  Winds are picking up slightly, outside temp is 88degF.

Coordinated with LLO & Virgo a few times for this--3hrs & 15min (via TeamSpeak) before the Calibration.  And then about 2min before 1830utc (1130amPT), I spoke with each operator for a final reminder and then jumped into it.

NOTE:  So, I knew about this measurement (which I'm fairly new at still) because of our Operator Checksheet, where this measurement is listed as 1130amPT.  Also, on the LHO Control Room whiteboard, Saturday at 1130amPT there is a note.  For a more official document for O4b Calibration measurements, Jenne pointed me to the document (L2400036).  In this document the times for the calibration measurements are listed in Sec3.3.  In the Ops Wiki Calibration Instruction page, old times were listed (mainly the wednesday dates).  For O4b, we now run these calibrations on Thursdays at 830amPT & Saturdays at 1130amPT---I updated the wiki to show this.

Measurement NOTES:

• 18:30:00 Received reminder for Calibration measurement (should this be earlier for a warning?)
• Following instructions (link)
• H1 is thermalized (locked for over 11hrs)
• Calibration_Monitor medm screenshot is attached
• 18:30:14  ISC LOCK to NLN_CAL_MEAS & Observatory Mode to COMMISSIONING
• 1830 - 1835 Broadband measurement run
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/
• 1835:40 - 1857:14 Simullines measurement
  • gps START time:  GPS:  1403116559.460699
  • gps END time:  GPS: 1403117852.165272
  • Files writtten to subfolders here:  /ligo/groups/cal/H1/measurements

Sat Jun 22 10:08:35 2024 INFO: Fill completed in 8min 32secs

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

H1's been locked the last 7.5hrs and it's very quiet seismically.  Today's forecast high is around 98degF.

Nuc33's gwistat webpage needed to have the tab/webpage reloaded.