SEI seismometer mass position check - Monthly FAMSI 26503

Averaging Mass Centering channels for 10 [sec] ...

2025-07-06 09:20:59.267796
There are 2 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -4.661 [V]
STS EY DOF Z/W = 2.355 [V]

All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.465 [V]
STS A DOF Y/V = -0.711 [V]
STS A DOF Z/W = -0.668 [V]
STS B DOF X/U = 0.173 [V]
STS B DOF Y/V = 0.977 [V]
STS B DOF Z/W = -0.395 [V]
STS C DOF X/U = -0.805 [V]
STS C DOF Y/V = 0.816 [V]
STS C DOF Z/W = 0.606 [V]
STS EX DOF X/U = -0.079 [V]
STS EX DOF Y/V = -0.064 [V]
STS EX DOF Z/W = 0.065 [V]
STS EY DOF Y/V = 1.178 [V]
STS FC DOF X/U = 0.194 [V]
STS FC DOF Y/V = -1.139 [V]
STS FC DOF Z/W = 0.616 [V]

Assessment complete.

--------------------------------------------------------------------------------------

Averaging Mass Centering channels for 10 [sec] ...
2025-07-06 09:21:50.265931

There are 12 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -1.373 [V]
ETMX T240 2 DOF Y/V = -1.269 [V]
ETMX T240 2 DOF Z/W = -0.959 [V]
ITMX T240 1 DOF X/U = -2.0 [V]
ITMX T240 1 DOF Z/W = 0.441 [V]
ITMX T240 3 DOF X/U = -2.121 [V]
ITMY T240 3 DOF X/U = -0.942 [V]
ITMY T240 3 DOF Z/W = -2.559 [V]
BS T240 1 DOF Y/V = -0.349 [V]
BS T240 3 DOF Z/W = -0.431 [V]
HAM8 1 DOF Y/V = -0.521 [V]
HAM8 1 DOF Z/W = -0.843 [V]

All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = -0.124 [V]
ETMX T240 1 DOF Y/V = -0.124 [V]
ETMX T240 1 DOF Z/W = -0.167 [V]
ETMX T240 3 DOF X/U = -0.102 [V]
ETMX T240 3 DOF Y/V = -0.187 [V]
ETMX T240 3 DOF Z/W = -0.11 [V]
ETMY T240 1 DOF X/U = 0.002 [V]
ETMY T240 1 DOF Y/V = 0.097 [V]
ETMY T240 1 DOF Z/W = 0.159 [V]
ETMY T240 2 DOF X/U = -0.132 [V]
ETMY T240 2 DOF Y/V = 0.156 [V]
ETMY T240 2 DOF Z/W = 0.033 [V]
ETMY T240 3 DOF X/U = 0.164 [V]
ETMY T240 3 DOF Y/V = 0.019 [V]
ETMY T240 3 DOF Z/W = 0.062 [V]
ITMX T240 1 DOF Y/V = 0.237 [V]
ITMX T240 2 DOF X/U = 0.161 [V]
ITMX T240 2 DOF Y/V = 0.25 [V]
ITMX T240 2 DOF Z/W = 0.218 [V]
ITMX T240 3 DOF Y/V = 0.106 [V]
ITMX T240 3 DOF Z/W = 0.117 [V]
ITMY T240 1 DOF X/U = 0.033 [V]
ITMY T240 1 DOF Y/V = 0.095 [V]
ITMY T240 1 DOF Z/W = -0.0 [V]
ITMY T240 2 DOF X/U = 0.026 [V]
ITMY T240 2 DOF Y/V = 0.246 [V]
ITMY T240 2 DOF Z/W = 0.079 [V]
ITMY T240 3 DOF Y/V = 0.036 [V]
BS T240 1 DOF X/U = -0.085 [V]
BS T240 1 DOF Z/W = 0.157 [V]
BS T240 2 DOF X/U = 0.067 [V]
BS T240 2 DOF Y/V = 0.156 [V]
BS T240 2 DOF Z/W = 0.017 [V]
BS T240 3 DOF X/U = -0.166 [V]
BS T240 3 DOF Y/V = -0.3 [V]
HAM8 1 DOF X/U = -0.234 [V]

Assessment complete.

TITLE: 07/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Ops Owl shift was woken up last night
H1 unlocked when I arrived.
Initial_ Alignment was completed.
Attempting to lock now.

I got a call 05:39 UTC and found the SQZ to be struggling to lock, notifying "LO RAILING", I consulted the alog and found a report alog81027 from Vicky and myself where we faced the same issue. I checked the FC alignment and found it to be the same, I then checked the ZMs and found ZM6 to be in a very different spot, especially in pitch. I brought back ZM6s alignment which let the LO lock but our range was terrible, I then adjusted the OPO temperature and ran a SQZ ang adjust as it was reporting that the angle was out of range then everything looked good.

05:55 UTC Observing

TITLE: 07/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Two locklosses this evening with lengthy relocks, but things generally have been straightforward. H1 has now been locked and observing for an hour.

• 23:26 - Lockloss - alog85562
• 01:47 - Observing
• 02:12 - Lockloss - alog85565
  • 03:03 - Lockloss in MAX_POWER
  • 03:53 - Reached OMC_WHITENING, damping violins
• 04:13 - Observing

Lockloss @ 02:12 UTC after 27 minutes locked - link to lockloss tool

No obvious cause.

TITLE: 07/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

Lockloss first thing in the morning.
Got relocked just in time for SuperEvent S250705cb candidate!
Had another Lockloss that pushed the Calibration sweep off until later in the day due to thermalization.

Dropped from Observing for SQZ "Beam diverter is open but no 3MHz on OMC, could be an alignment problem"  Issue @ 20:31 UTC.
When I cleared the History on H1:SUS-ZM6_M1_LOCK_ filters and allowed the SQZ_MAN to do lock everything it seemed to work.
Note: Did not have to move ZM4 or ZM6 sliders to get SQZ_LO_LR back to LOCKED_OMC[20].

Thermalized Calibration measurement @ 21:39 UTC.

LOG:
                                                                                                                                                                        

Lockloss @ 23:26 UTC after almost 5 hours locked - link to lockloss tool

Looks to be some motion on ETM L3 shortly before the lockloss, but hard to say where this came from.

FAMIS 26401, last checked in alog85398

All fans largely the same as last check and within noise thresholds, aside from a very small increase in noise for MR fan 1.

TITLE: 07/05 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 9mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: H1 has been locked for 4.5 hours.

• Wind and microseism low
• All other systems nominal

CAL Broadband:
pydarm measure --run-headless bb ran at 21:39 UTC

diag> save /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250705T213846Z.xml
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250705T213846Z.xml saved
diag> quit
EXIT KERNEL

2025-07-05 14:43:57,424 bb measurement complete.
2025-07-05 14:43:57,424 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250705T213846Z.xml
2025-07-05 14:43:57,425 all measurements complete.

anthony.sanchez@cdsws29: gpstime;python /ligo/groups/cal/src/simulines/simulines/simuLines.py -i /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_20250212.ini;gpstime
PDT: 2025-07-05 14:48:44.048708 PDT
UTC: 2025-07-05 21:48:44.048708 UTC
GPS: 1435787342.048708

....computer noises....

2025-07-05 22:11:19,494 | INFO | Commencing data processing.
2025-07-05 22:11:55,344 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250705T214844Z.hdf5
2025-07-05 22:11:55,352 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250705T214844Z.hdf5
2025-07-05 22:11:55,357 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250705T214844Z.hdf5
2025-07-05 22:11:55,362 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250705T214844Z.hdf5
2025-07-05 22:11:55,367 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250705T214844Z.hdf5
PDT: 2025-07-05 15:11:55.502174 PDT
UTC: 2025-07-05 22:11:55.502174 UTC
GPS: 1435788733.502174

Relocked from the Prior lockloss this morning.
H1 Made it to NLN and Observing by 16:25 UTC

Superevent S250705cb candidate !

17:27 UTC Unknown Lockloss

Relocking Notes:
H1 Relocked it self reaching NLN at 18:34 UTC after bouncing between Locking ALS and Down a few times.

The Plan:
Since H1 barely got back to Observing at 1830 UTC and wont be Thermalized until 21:30 UTC. I plan to drop out of observing at 21:30 to get a Calibration done here at LHO.
 

Sat Jul 05 10:06:44 2025 INFO: Fill completed in 6min 40secs

TITLE: 07/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:
H1 has been Locked and Observing for 2 Hours & 51 min.
All systems are running smoothly.

Expected:
1830 UTC -1900 UTC  Calibration

Update:
14:40 UTC Lockloss right after I got here.

TITLE: 07/05 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Started the shift by troubleshooting a SQZ issue that once resolved made for a straightforward evening. Two locklosses tonight, but relocking each time went automatically. H1 has now been locked and observing for almost 2 hours.

• 00:18 - Resumed observing after fixing squeezer
• 00:45 - Lockloss - alog85552
• 02:09 - Observing
• 02:10 - Lockloss - alog85553
• 03:17 - Observing

Lockloss @ 00:45 UTC after almost 12 hrs lock - link to lockloss tool

No obvious cause.