05:09 UTC lockloss

TITLE: 07/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: A lockloss towards the end of the shift and right after relocking.
LOG: No log

I've added the damping settings I found the other day (FM1+FM2+FM10 G=-50) into lscparams after seeing it work for many lock stretches, the VIOLIN_DAMPING GRD could use a reload to see this change.

• 00:01 - 00:05 UTC dropped Observing from the SQZer's PMC losing lock
• 02:56 UTC lockloss from an ETMX glitch
  • 03:58 UTC initial alignment, DRMI locked after 7 minute now
  • 05:08 NLN
• 05:09 lockloss, ??? Annoying

I took some high resolution spectra in the 1460 - 1500 bandwidth of DARM to look at the second harmonic violin mode region, all of these might not be violin modes. I found 5 over 10^-16, 1468.4961 1472.7793, 1481.9717 (monitor filter on ETMY mode19), 1492.0198, and 1497.1934 (the worst offenders), these were reduced to 3 when I took another spectra with a smaller bw an hour later. There were also several above 10^-17, 1464.5293, 1464.0234, 1467.3916 1468.5879, 1471.2969, 1471.7012,  1472.9668, 1482.0117, 1494.3535, 1494.3711, 1499.5937, 1500.4248. The frequencies I saw don't match the old ones reported in the wiki's violin mode table or in T1800327 but I believe these documents were from pre-O3.

Lockloss 02:56 UTC from an ETMX glitch just under 1/4 of a second before the LL

TITLE: 07/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Pretty straightforward day of public site tours and only one lockloss with a fully automatic relock after. Planned calibration sweep was missed because of this; Ryan C. says he'll run it if L1 drops out of observing this evening. H1 has now been locked for 4.5 hours.

• 14:25 - S250712cd
• 17:23 - Lockloss - alog85709
  • 18:01 - Finished initial alignment
• 18:54 - Observing

TITLE: 07/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

• We've been locked for just over 4 hours
  • We had our best range ~30 minutes after locking, I can see ZM4 is drifting a bit mostly in P, but the angle is probably not optimized for being fully thermalized as the ANG servo isn't being used right now
• The calibration measurement was not run due to a lockloss, if LLO loses lock I'll drop observing and run the measurement
• The SQZ_PMC GRD is reporting the PMC PZT volts are low

Closes FAMIS26404, last checked in alog85561

Everything looks the same as it did last week.

Lockloss @ 17:23 UTC after 8 hrs locked - link to lockloss tool

Looks to be an ETMX glitch about a half second before the lockloss.

Sat Jul 12 10:08:39 2025 INFO: Fill completed in 8min 36secs

TITLE: 07/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: H1 has been locked and observing for 5.5 hours. Looks like one automatic relock overnight, and currently in a stand down for a candidate event at 14:25.

• Wind low, microseism also low and falling
• All other systems nominal

TITLE: 07/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: One lockloss with an easy relock. We've been locked for just over 3.5 hours.
LOG:  

• 23:57 UTC lockloss
  • After DRMI struggled, during PRMI I held in PRMI_LOCKED and adjusted PRM by hand, DRMI then locked quickly and the camera spot looked good.
  • 01:27 UTC Observing, I ran a SQZ SCAN_ANG before going into observing and adjusted the OPO temperature while relocking

I ran my damp_regression_compare script (85369) on the suspensions that we swapped the satellite amplifiers for today, BS, PRM, PR3, SRM, and SR3. The results show a decrease in the OSEM noise of at least 2x!

Part of what the script does is save the channel data as a .mat file so it's quicker to run next time, so I'll post that as well as the results.

On Tuesday Fil swapped the sat amps for ITMX, ITMY, and SR2 (85619). Like I did for the first set of satamp swaps (85485), I've used my damp_regression_compare script found in sustrunk to compare the noise performance (85369).

ITMX
M0
Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Results/allDampRegressCompare_H1SUSITMX_M0_NoiseComparison_1435482383vs1436080373-1200.pdf
         r12442
Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/dampRegress_H1SUSITMX_M0_1435482383_1200.mat
      /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/dampRegress_H1SUSITMX_M0_1436080373_1200.mat
      r12442
R0
Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Results/allDampRegressCompare_H1SUSITMX_R0_NoiseComparison_1435482383vs1436080373-1200.pdf
         r12443
Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/dampRegress_H1SUSITMX_R0_1435482383_1200.mat
      /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/dampRegress_H1SUSITMX_R0_1436080373_1200.mat
      r12443

ITMY
M0
Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Results/allDampRegressCompare_H1SUSITMY_M0_NoiseComparison_1435482383vs1436080373-1200.pdf
         r12444
Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/dampRegress_H1SUSITMY_M0_1435482383_1200.mat
      /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/dampRegress_H1SUSITMY_M0_1436080373_1200.mat
      r12444
R0
Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Results/allDampRegressCompare_H1SUSITMY_R0_NoiseComparison_1435482383vs1436080373-1200.pdf
         r12445
Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/dampRegress_H1SUSITMY_R0_1435482383_1200.mat
      /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/dampRegress_H1SUSITMY_R0_1436080373_1200.mat
      r12445

SR2
Results: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Results/allDampRegressCompare_H1SUSSR2_M1_NoiseComparison_1435482383vs1436080373-1200.pdf
         r12446
Data: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/dampRegress_H1SUSSR2_M1_1435482383_1200.mat
      /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/dampRegress_H1SUSSR2_M1_1436080373_1200.mat
      r12446

23:57 UTC lockloss

TITLE: 07/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Two locklosses this shift, but recovery so far has been straightforward. H1 is currently relocking and up to MAX_POWER.

• 15:41 - Lockloss - alog85685
  • 17:06 - Lockloss during LOWNOISE_ASC
• 18:00 - Observing
• 22:23 - Lockloss - alog85697

LOG:

TITLE: 07/11 Eve Shift: 2330-0500 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: 10mph Gusts, 6mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

• We are still trying to recover and lock DRMI after a 22:23 UTC lockloss
• 2ndary microseism is increasing
• Wind is low

Lockloss @ 22:23 UTC after 4.5 hours locked - link to lockloss tool

No obvious cause, but ETMX starts moving strangely about a half a second before the lockloss.