TITLE: 07/08 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: One lock loss during the shift. During reacquisition I moved PR3 a little bit to help the comm beat note. After an initial alignment it went straight up and we've been observing for 2.5 hours now.
LOG:

• 0341 lock loss
  • The COMM beatnote was -18dBm when I got ALS locked, so I started running an initial alignment and then moved PR3 small amounts to see if it would quickly help. I ended up moving PR3 P from -122.2 -> -121.6 and Y from 98.8 -> 98.6. This brought the beatnote up to around -14.5dBm and ALSX power moved up as well. when DRMI locked POP18 looks to be higher than it was the last handful of locks over the last few days.
• 0528 Observing

Lock loss 1404445312

5 hours and 42 mins seems like a standard lock for this week. LSC-DARM saw an odd wiggle before lock loss, normally I see an ETMX output that matches this but I didn't see that this time.

I have replaced the original viewport covers so the LVEA is ready to go to laser safe.

At the last minute I finally found a beam on the MC baffle by HAM3. The beam is on the +X side of the baffle, near the hole for the viewport for the PRM camera. I will see if it moves with the CP when I return.

TITLE: 07/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Similar shift to yesterday (except we're around 102degF!), with a 4-5hr lock and 2-3hr reacquisition (with rough locking for the first 90min). 

(Since Observing time is precious, I didn't even think of running a calibration since L1 & V1 were UP all the times I could have run a calibration.)

Robert was onsite as well as JennyW for an RRT shift.
LOG:

• 1458 H1 back to Observing after 2.5relock with RyanS intervention (owl) to get thru issues w/ alsy.
  • IXm13 looking good with its new settings and 1kHz is 2 orders of magnitude lower than what we were having ~18hrs when it was rung up.
• 1934 Lockloss Of The Shift (after a 4hrs41min lock)
  • 1939-1959 Running Initial Alignment
  • For locking, first (2) locklosses were early and due to ALS glitches seen for both X & Y arms as noticed yesterday (before an alignment).  So for next lock, I paused at Locking Arms Green and then Locking ALS.  Then had no issues getting past these early steps.  Just odd and new behavior.
  • Sadly DRMI was a little sad/dead looking at first, but then flashes got better and looked centered, but still no dice.  Selected PRMI after about of 7min of DRMI locking....PRMI locked, but lost lock during PRMI ASC (possibly due to Japan EQ).
  • Several more ALS glitch locklosses, even with pauses.
  • Made it through PRMI, and then while trying to acquire DRMI, noticed the glitching appearing on both alsx & y a few seconds before the lockloss. 
  • ....and after about 100-110min, H1 finally makes it past DRMI and continues without a hitch.  (Robert suggests we have an opitc which gets hot, causes lockloss, takes time to cool down, and then allows us to relock.  Sounding about right.)

Commissioning time has been reduced recently by lock losses and other issues, so I have been trying a new technique for determining the ITM biases that minimize coupling of electronics ground noise. I have been making slow adjustments of the bias during observation, recording the times of those slow changes, and then monitoring the coherence between DARM and the current clamp on the electronics grounding cable in the CER for the new settings.

The times of the slow changes during observation mode, and the bias setting I have tried, are listed in 78791, 78767, 78734 and this log. The figure compares the original settings for O4b, the setting that we guessed would be best, 0V,0V, and the setting that was consistently better, ITMX: 0, ITMY: -40 V (a setting of -4 in the offset window).

TITLE: 07/07 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Corey got us relocked and we've been running good for an hour.

Link to report

• The duty cycle for this week was 63.3%
• Some days, the lock losses were due to earthquakes, some due to ETMX motion and some have unknown causes.
• Average range was between 155-160 Mpc, with some days have big dips due to wind motion.
• The week has relatively high wind motion with moderately high seismic motion.
• The End BSC 10 has constant high amplitude low frequency noise.
• The HVETO round winners were different every day.
• FScan: All plots have appeared with all days having the line count well below the threshold.

Once again, a diff for ALS-Y_WFS (Basically ACCEPTED filter which was originally enabled for the recent lock).

Then had an additional Diff for a TRAMP for LSC-XARM.  (see attached for both.)

H1's been locked almost 4.25hrs (kind of expecting it to lose lock any minute given H1's behavoir since Tues).  Around 95degF outside.

To get to Observing shortly after the beginning of the shift this morning, I needed to ACCEPT ALS-Y WFS filter changes (see attached).  These appeared to have occurred around the steps of DHARD_WFS & PARK_ALS_VCO (but I don't see this channel during those states).

The channels changed are:
H1:ALS-Y_WFS_DOF_3_Y

H1:ALS-Y_WFS_DOF_3_P

And ACCEPTED their FM9's ("-14dB" filter)

I have colour coded the FE RCG overview MEDM to show non-production RCG models with a red box. Clicking on the purple RCG box on the CDS overview will now open the RCG Overview MEDM.

Sun Jul 07 08:19:21 2024 INFO: Fill completed in 19min 16secs

TITLE: 07/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

H1 was past 25W when I arrived (thanks to an awakened RyanS for the 2-clicks for ALS!).  Waiting for H1 to get back to NLN.

Post Timing-Error (and pesky Tues Main), H1 has been riding rough; last 24hrs roughly 3-4hr long locks with 2-3 lock acquisitions.  We'll see how today's data point looks for h1!  With these short locks not sure we'll thermalize long enough to run a calibration, but we'll see if there's an opportunity (when other detectors are down).

H1 called for assistance at 13:30 UTC because it was stuck trying to lock ALSY. I gave ETMY two clicks in yaw and that seemed to be all it needed; H1 is relocking smoothly and up to PREP_DC_READOUT.

TITLE: 07/07 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

The first lock acquistion had the same issues that Corey saw during his shift with ALS unable to stay locked or unable to get past FIND IR. After some time it started to have longer times between lock losses and it eventually made it past ALS. I noticed that the COMM beat note was low (-18 dBm then grew to -16 over 30 min). This might explain part of the troubles. The second lock acquisiton was a very similar situation but the beat note started at -16dBm so ALS was more stable sooner. Maybe we found the threshold, and I did NOT touch PR3. I also had to run an initial alignment since DRMI was a bit too far off to catch. We are now on DC readout and moving forward.

ITMX mode 13 was rung up when I arrived and I was able to damp it fairly quick with Rahul's settings and then slowly adding gain.

LOG:

• 0009 Lock loss
• 0232 Observing
• 0642 Lock loss

Lock loss 1404369750

Again, not seeing much of anything on any of the plots. Another 4-5 hour lock.

Lockloss 1404346170

Quite sudden, I'm not seeing anything on the lock loss ndscopes, even the many new ones. DIAG_MAIN reports that the ref cav transmission is low, which it seems to have been this way for the past 4 days. This seems really low and potentially an issue, but we've had locks within these last 4 days so perhaps not. I'm running into the same issue that Corey had this morning with ALS. It seems that it won't stay locked. I'm still catching up on the week's alogs, so maybe I'll find a hint soon.

It seems earthquakes causing similar magnitudes of movement on-site may or may not cause lockloss. Why is this happening? Should expect to always or never cause lockloss for similar events. One suspicion is that common or differential motion might lend itself better to keeping or breaking lock.

- Lockloss is defined as H1:DRD-ISC_LOCK_STATE_N going to 0 (or near 0).
- I correlated H1:DRD-ISC_LOCK_STATE_N with H1:ISI-GND_STS_CS_Z_EQ_PEAK_OUTMON peaks between 500 and 2500 μm/s.
- I manually scrolled through the data from present to 2 May 2024 to find events.
    - Manual, because 1) wanted to start with a small sample size and quickly see if there was a pattern, and 2) because I need to find events that caused loss, then go and find similarly sized events we kept lock.
- Channels I looked at include:
    - IMC-REFL_SERVO_SPLITMON
    - GRD-ISC_LOCK_STATE_N
    - ISI-GND_STS_CS_Z_EQ_PEAK_OUTMON ("CS_PEAK")
    - SEI-CARM_GNDBLRMS_30M_100M
    - SEI-DARM_GNDBLRMS_30M_100M
    - SEI-XARM_GNDBLRMS_30M_100M
    - SEI-YARM_GNDBLRMS_30M_100M
    - SEI-CARM_GNDBLRMS_100M_300M
    - SEI-DARM_GNDBLRMS_100M_300M
    - SEI-XARM_GNDBLRMS_100M_300M
    - SEI-YARM_GNDBLRMS_100M_300M
    - ISI-GND_STS_ITMY_X_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_Y_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_Z_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_X_BLRMS_100M_300M
    - ISI-GND_STS_ITMY_Y_BLRMS_100M_300M
    - ISI-GND_STS_ITMY_Z_BLRMS_100M_300M
    - SUS-SRM_M3_COILOUTF_LL_INMON
    - SUS-SRM_M3_COILOUTF_LR_INMON
    - SUS-SRM_M3_COILOUTF_UL_INMON
    - SUS-SRM_M3_COILOUTF_UR_INMON
    - SUS-PRM_M3_COILOUTF_LL_INMON
    - SUS-PRM_M3_COILOUTF_LR_INMON
    - SUS-PRM_M3_COILOUTF_UL_INMON
    - SUS-PRM_M3_COILOUTF_UR_INMON

        - ndscope template saved as neil_eq_temp2.yaml

- 26 events; 14 lockloss, 12 locked (3 or 4 lockloss event may have non-seismic causes)

- After, usiing CS_PEAK to find the events, I, so far, used the ISI channels to analyse the events.
    - The SEI channels were created last week (only 2 events captured in these channels, so far).

- Conclusions:
    - There are 6, CS_PEAK events above 1,000 μm/s in which we *lost* lock;
        - In SEI 30M-100M
            - 4 have z-axis dominant motion with no motion or strong z-motion or no motion in SEI 100M-300M
            - 2 have y-axis dominated motion with a lot of activity in SEI 100M-300M and y-motion dominating some of the time.
    - There are 6, CS_PEAK events above 1,000 μm/s in which we *kept* lock;
        - In SEI 30M-100M
            - 5 have z-axis dominant motion with only general noise in SEI 100M-300M
            - 1 has z-axis dominant noise near the peak in CS_PEAK and strong y-axis domaniated motion starting 4 min prior to the CS_PEAK peak; it too only has general noise in SEI 100M-300M. This x- or y-motion which starts about 4 min before the peak in CS_PEAK has been observed in 5 events -- Love waves precede Rayleigh waves, could be Love waves?
    - All events below 1000 μm/s which lose lock seem to have a dominant y-motion in either/both SEI 30M-100M / 100M-300M. However, the sample size is not large enough to convince me that shear motion is what is causing lockloss. But it is large enough to convince me to find more events and verify. (Some plots attached.)