TITLE: 09/03 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 19mph Gusts, 15mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
Detector in Observing and has been Locked for 12hrs 35mins.
Sun Sep 03 10:07:14 2023 INFO: Fill completed in 7min 10secs
TITLE: 09/03 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 20mph Gusts, 17mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY:
Wind Is elevated
PSL Dust mon 101 alarming when I walked in.
Inherited and Interferometer that has been locked for 4.5 hours.
TITLE: 09/03 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY: We have now been Locked for 4hrs 50mins. There were two locklosses from NLN during my shift, but both times locking back up was fast and hands-off. I could not find a cause for either of them.
The code changes made earlier today(72636) for mode24 seem to be working well, and there was only one time (that I saw at least) where the phase was cycled through fully, and mode24 didn't get above ~15.
Just before posting this, I heard the building creak and the wind speed at all buildings jumped up really high!
23:00UTC Detector in Observing and Locked for 1 hour
23:48 Lockloss from NLN (72644)
23:50 Lockloss from LOCKING_ALS
00:17 GRB-Short alert E434681 - Fermi, NOT_GRB
00:34 Reached NOMINAL_LOW_NOISE
00:47 Into Observing
01:28 Lockloss (72646)
02:18 NOMINAL_LOW_NOISE
02:30 Observing
04:30 Optics lab dustmon jumped up from 0 to 4300 counts for 10mins, and then back down to 0. Lines up with a temporary increase in wind at the corner station.
LOG:
no log
09/03 1:28UTC Another Lockloss from NLN just 54 minutes after having reached NLN :(
02:30UTC Observing again!
00:47UTC Back to Observing
TITLE: 09/02 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
Taking over from Tony, we've been Locked for just over an hour and are currently Observing. Winds are low.
TITLE: 09/02 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
LOG:
Stand Down request went away.
16:00-Ish UTC PI 24 was ringing up again, and it had rung its self up 3 times. on the 4th time
I changed H1:SUS-PI_PROC_COMPUTE_MODE24_PLL_PHASE to a value that would work WITHOUT changing the state of the PI Guardian which allowed me to stay in OBSERVING the entire time.
PI Guardian Needs to be reloaded After Naoki's Changes.
Lockloss 20:45 UTC
PI Guardian was reloaded.
Initial Alignment Not run before locking. But this lock did go through Check Mich fringes.
Observing Reached @ 22:09
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 18:42 | FAC | Tyler | Mech Rm | N | Draining the Air Handler Condensation | 19:12 |
Lockloss https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1377722766
Ground Motion, wind, and PI's can be ruled out. But otherwise unknown Lockloss.
Famis 26481
Check_T240_Centering.py:
ITMX T240 2 DOF X/U = 0.11 [V]
ITMX T240 2 DOF Y/V = 0.197 [V]
ITMX T240 2 DOF Z/W = 0.196 [V]
ITMX T240 3 DOF Y/V = 0.115 [V]
ITMX T240 3 DOF Z/W = 0.137 [V]
ITMY T240 1 DOF X/U = 0.048 [V]
ITMY T240 1 DOF Y/V = 0.011 [V]
ITMY T240 1 DOF Z/W = -0.129 [V]
ITMY T240 2 DOF X/U = 0.082 [V]
ITMY T240 2 DOF Y/V = 0.134 [V]
ITMY T240 2 DOF Z/W = -0.019 [V]
ITMY T240 3 DOF Y/V = 0.009 [V]
BS T240 1 DOF X/U = -0.221 [V]
BS T240 1 DOF Z/W = 0.013 [V]
BS T240 2 DOF X/U = -0.163 [V]
BS T240 2 DOF Y/V = -0.063 [V]
BS T240 2 DOF Z/W = -0.218 [V]
BS T240 3 DOF X/U = -0.272 [V]
HAM8 1 DOF X/U = -0.198 [V]
HAM8 1 DOF Y/V = -0.19 [V]
Assessment complete.
check_sts_centering.py:
STS EY DOF Z/W = 2.596 [V]
All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.572 [V]
STS A DOF Y/V = -0.811 [V]
STS A DOF Z/W = -0.548 [V]
STS B DOF X/U = 0.527 [V]
STS B DOF Y/V = 0.91 [V]
STS B DOF Z/W = -0.591 [V]
STS C DOF X/U = -0.366 [V]
STS C DOF Y/V = 0.826 [V]
STS C DOF Z/W = 0.206 [V]
STS EX DOF X/U = -0.187 [V]
STS EX DOF Y/V = 0.055 [V]
STS EX DOF Z/W = 0.066 [V]
STS EY DOF Y/V = 0.109 [V]
STS FC DOF X/U = 0.378 [V]
STS FC DOF Y/V = -0.786 [V]
STS FC DOF Z/W = 0.744 [V]
Assessment complete.
LockLoss :
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1377686651
I just happend to see the PI's ring up this morning durning my shift and started to trend them back to see just how high PI 24 can go with out us losing lock. While just goofing off I discovered that just last night, literally the last lockloss, PI 24 had run up from 20 to 2213.5 and caused a lockloss in under 12 minutes. screenshot included. The cursor T1 cursor is set at the point were PI 24 reaches 20. T2 cursor is set to GPS Time 1377686651 which is the Lockloss timestamp.
PI FOM plots over the time LockLoss time. Top plot is log scaled.
We think that the PI guardian did not have enough time to evaluate the correct damping phase for mode 24 (10.431 kHz PI) so we updated the PI guardian as we did in alog69800. We increased the phase step from 30 to 60 deg, the average time to calculate the new rms from 1 to 5s, and the timer for each step from 5 to 10s. The PI guardian is not reloaded yet and we asked the operator to reload it when lockloss happens.
Sat Sep 02 10:07:32 2023 INFO: Fill completed in 7min 28secs
TITLE: 09/02 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY:
Inheirited an Interferometer that has been locked and Observing for 3 hours.
GRB-Short E434553 Candidate had a Stand Down Request active when I walked in.
TITLE: 09/02 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY: We are still Observing and have now been Locked for 10 hours. A few minutes ago we got a GRB-Short alert and a Stand Down (Fermi, labeled as NOT_GRB).
The top FOM on nuc26 disconnected from the port for ~30 seconds saying that nothing was connected, before turning back on by itself. Later on in the evening the top FOM of nuc5 also lost contact with its computer for a few seconds before coming back on its own.
23:00UTC In Observing and detector has been Locked for 2hrs 4mins
06:55 GRB-Short on Verbals and Stand Down on lock clock
LOG:
no log
Closes FAMIS#26248, last checked 72443
Corner Station Fans (attachment1)
All fans are looking good with no concerns, with MR_FAN5_2 being very variable in noise level (as it usually is), and MR_FAN5_1 being the loudest at just below 0.4.
Outbuilding Fans (attachment2)
All fans are looking good and are well below any noise level that would be of concern to us.
Notes:
- Monday night, 08/29 at 6:13UTC, EX_Fan1 turned off for a minute before a power glitch(coincidence??) turned it back on (attachment3).
- 09/01 16:39UTC, something similar happened with EY_FAN2 (attachment4), although this one is probably related to the work that Randy and Tyler were doing at EY around that time(72628)
We are still in Observing and have now been Locked for almost 7 hours.