Mon Jul 07 10:07:08 2025 INFO: Fill completed in 7min 4secs
Gerardo confirmed a good fill curbside.
TITLE: 07/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: EARTHQUAKE
Wind: 5mph Gusts, 1mph 3min avg
Primary useism: 0.29 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
H1 Unlocked due to earthquake when I arrived.
I think the ground motion has come down a fair amount, and in a few minutes we will be leaving EQ mode.
I've started an Initial Alignment to start getting H1 locked again.
12:39 UTC H1 called for help for the initial alignment timer expiring, I found Yarm to be notifying "Find by hand" so I helped it out and it locked after a few taps of ETMY and ITMY.
13:07 UTC finished IA, back to locking
13:52 UTC lockloss at POWER_25Ws from a 6.3 from New Zealand, holding in DOWN
11:14 UTC lockloss from an ETMX glitch
TITLE: 07/07 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Quiet shift where H1 remained locked throughout, although I did drop observing once briefly to run a SQZ angle scan, but it didn't make an improvement (afterwords I remembered the angle servo is running now, so it makes sense why it was already optimized). Current lock stretch is up to 9.5 hours.
Link to DQ Shift Summary here
TITLE: 07/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
I had to run an Initial alignment twice this morning before H1 would get past DRMI and Evetually reached NLN at 16:41:30 UTC.
@ 14:07 UTC Unknown Lockloss today.
Relock needed another Initial Alignment to get past DRMI. We eventually Arrived back at NLN at 19:26 UTC.
@21:01 UTC I noticed the Range drop and I started to Troubleshoot Range Related SQZ issues.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:18 | PEM | Robert | LVEA +X | N | Turning on Current Clamp | 16:22 |
| 18:20 | PEM | Robert | LVEA HAM 1 | N | More PEM commisioning. | 19:06 |
| 19:11 | PEM | Robert | LVEA | N | Shutting down PEM amps | 19:13 |
I noticed that the Range started to drop, and the guardians had some things to tell me.
I followed those instructions in the guardian messages and requested RESET_SQZ_ASC_FDS[97]
Immediatley, ZM4 Started to Saturate and wouldn't stop even if I took SQZ_MAN to down.
I eventually took ZM4 to Damped for a few minutes while I try to find a solution.
One of the solutions I tried were to "Gracefully clear the SQZ-ASC offsets.
Eventually I figured out that ZM4 slider needed to be moved in pitch since it had drifted off quite far.
I got SQZ_MAN back to FREQ_DEP_SQZ to see if that ZM4 move made a difference.
It did not..... then I requested a SCAN_ALIGNMENT_FDS to see if that would help.
I then took a Low range Coherence plot and a comparision plot from before the range fell in this lock and after.
Then I adjusted the OPO Temp and then requested SCAN_ALIGNMENT FDS again.
I was only able to get the range back up to 138 Mpc.
TITLE: 07/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 139Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 3mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: H1 has been locked for 4 hours. Range is looking a little low (as Tony is detailing in his alog) so I may tough that up this evening.
17:30 UTC Unknown Lockloss
The signal that seems to depart earliest is the LSC_DARM_IN1_DQ.
Sun Jul 06 10:07:10 2025 INFO: Fill completed in 7min 6secs
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.
Even after Initial_Alignment H1 was bouncing off of DRMI into PRMI & Check mitch fringes.
I requested another Inital_Alignment which went quickly.
H1 is already well past DRMI locking.
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.
Lockloss @ 02:12 UTC after 27 minutes locked - link to lockloss tool
No obvious cause.
Back to observing at 04:13 UTC. A lockloss during MAX_POWER caused violin modes to ring up, so on the next attempt H1 spent about 20 minutes damping in OMC_WHITENING. Fully automatic relock.
Using a script called histogram.py which calls statecounter2.0, I was able to determine how many times ISC_LOCK spent more than 60 seconds in ACQUIRE_DRMI_1F using Minute trends.
I broke this up into Pre Vent and Post vent:
Pre Vent:
Jan1st to April 1st 2025
Length of data 601
max Duration 19 Min
Average 3.5640
Post Vent:
June 1st 2025 to now
170 data points
Longest: 24 minutes.
Average: 5.1823 Min
Post vent break down.... break down:
Jun 1st to Jun 16th
Length of data 100
max Duration: 24min
Average 5.04 min
Jun 16th - now
Length of data 70
max Duration 13 Min
Average 5.38571
Link to a google sheet with all the exported data, and GPS times.
I copied Tony's awesome spreadsheet, and replotted the data sets while thinking about what they mean.
I have the same 4 data sets that Tony has (Jan-April, All of June, and then broken into Early June and Late June, with the divider being the time that I enabled the 'slow let go' of the BS pitch control). However, I've got all the x-axes fixed to be 0-25 minutes. I've also set the y-axes to be (0, number lock segments), so that they are roughly normalized. In the subtitle of the plot I note the percentage of the segments who are 10 mins or longer (actually, from the data set, the percent that have a value of 9 mins or greater). Since we have a 10 minute timer in the guardian that will flip over to trying PRMI or MICH locking, this percentage should help capture the number of locks that take a long time to acquire DRMI.
Notably, the number of segments that take a long time is about 2x larger after the BS slow let go was enabled, if we look at the percent in late June (48% take a long time) versus the percent in early June (28% take a long time) :( But, both of these are much higher than the 18% that took a long time before the vent.
This may mean that the slow letting go of the BS, as currently enabled, is not helpful.
If the statecounter.py code is able to, it could be interesting to get similar statistics, but have the durations start when we leave state 18 (Arms_off_resonance) and the duration end when we get to state 102 (DRMI_locked_check_ASC). That would enable us to more accurately see the total length of time it takes during an acquisition sequence. If we do this, we'd want to count and then exclude from the statistics the number of times we 'give up' and lose lock or do an initial alignment.
Updated Statecounter to find times that a value is between 2 user selected states.
And refined a script that makes Histograms specifically for DRMI Histogram Investigations that calls Statecounter.
tconvert jan 1 2025 = 1419724818
tconvert apr 1 2025 = 1427500818
tconvert jun 1 2025 = 1432771218
tconvert jun 16 2025 = 1434067218
tconvert now = 1435883245
The GPS Times are rounded off by Jim's round function so they fit into minute trend windows.
