https://earthquake.usgs.gov/earthquakes/eventpage/us7000nr0v/
ISI Watchdog trips:
BS: Stage 1 & 2
ITMX 1 & 2
ITMY 1 & 2
ETMX 1 & 2
ETMY 1 & 2
HAM 8
HAM 7
TITLE: 11/10 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.33 μm/s
QUICK SUMMARY:
H1 was still locked when I walked into the control room, due to Ryan C waking up with the IFO.
Incoming 5.9M EQ from Cuba: https://earthquake.usgs.gov/earthquakes/eventpage/us7000nr0n/
Lockloss 2024-11-10 16:08:52 https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415290150
Earthquake lockloss. Screenshots: Log , ASC , SUS , PSL & IMC , LSC , SEI
OWL Locklosses:
2024-11-10 10:18:11 https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415269109
This Lockloss was tagged as an ETM Glitch. Screenshots: Log , ASC , SUS , PSL & IMC , LSC , SEI
2024-11-10 09:08:40 https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415264939
This Lockloss was tagged as IMC, screenshots: Log , ASC , SUS , PSL & IMC , LSC , SEI
H1 called for help after the NLN timer expiring at 08:15 UTC, we were at MOVE_SPOTS. We reached NLN at 08:28 UTC, in observing at 08:31 UTC.
TITLE: 11/10 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
IFO is LOCKING in LOCKING_ARMS_GREEN
Shift has been very smooth with a behaving IFO. I was locked the entire time up until now, where an IMC glitch took us down most likely (alog 81170)
Also took a thermalized IFO calibration sweep with the temp/new ini file. Alog 81169.
LOG:
None
Lockloss seemingly PSL/FSS related. Glitching in FSS started around 1s Lockloss. It's still glitching right now.
TITLE: 11/10 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Calibration
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
The morning was plagued with IMC Fault issues alog .
After simply holding ISC_LOCK in DOWN and holding IMC in LOCKED [ Specifically to Not be in "ISS_ON " ] to wait for the IMC to be calm before starting to relock. Then wait again for a 5.8M EQ from Panama, I was able to get a lock all the way to Observing.
I was able to pass a locked IFO to Ibrahim.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 21:41 | SAF | Laser | LVEA | YES | LVEA is laser HAZARD | 08:21 |
| 15:58 | PEM | Robert | CS Mech room -> Chiller Yard | N | Cable crossing road to End X from Mech room to Chiller yard | 23:58 |
| 17:27 | PEM | Robert | LVEA | Yes | Setting up chiller pad & turning off the lights. | 22:06 |
| 20:30 | Tours | Mike, Fred & co | Control Room | N | Saturday tours | 23:58 |
Calibration Sweep done with new ini file Louis asked us to use for Simulines: /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_20241005_lowerPcal_higherPUM.ini
Broadband Start Time: 1415232600
Broadband End Time: 1415204090
Simulines Start Time: 1415233192
Simulines End Time: 1415234617
Files Saved:
2024-11-10 00:42:42,493 | INFO | Commencing data processing.
2024-11-10 00:42:42,493 | INFO | Ending lockloss monitor. This is either due to having completed the measurement, and this functionality being terminated; or because the whole process was aborted.
2024-11-10 00:43:19,012 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20241110T001937Z.hdf5
2024-11-10 00:43:19,020 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20241110T001937Z.hdf5
2024-11-10 00:43:19,025 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20241110T001937Z.hdf5
2024-11-10 00:43:19,030 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20241110T001937Z.hdf5
2024-11-10 00:43:19,034 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20241110T001937Z.hdf5
ICE default IO error handler doing an exit(), pid = 3252963, errno = 32
TITLE: 11/10 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 122Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 2mph Gusts, 0mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.43 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of 21:24 UTC
Since we are thermalized, I am about to go into CALIBRATION for our calibration sweep of the day.
TITLE: 11/09 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 2mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.44 μm/s
QUICK SUMMARY:
I set ISC_LOCK into Idle while waiting for the 5.8M Earthquake to stop shaking us for a few minutes.
I've been tryign to get this IFO to lock since I walked in this morning.
The IMC is unlocking and going into Fault at random times in the Locking process and In the Initial Alignment process.
15:47UTC
15:56:31 UTC
And multiple other times, including when I had taken ISC_LOCK to IDLE.
I called Elenna to try an confirm where this glitch was coming from and was the reason that I was losing all my locks.
Observing reached at 21:24 UTC
Sat Nov 09 10:05:20 2024 INFO: Fill completed in 5min 17secs
Note to FMCS, MY chilled supply water temp increase which started around 9am Fri 08nov2024 PST.
Sunday trend attached. MY VEA temps are holding steady around 65F. The second pump started around noon Fri, but this did not bring the H2O_SUP temp back to nominal.
TITLE: 11/09 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 4mph Gusts, 3mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.40 μm/s
QUICK SUMMARY:
Walking in I was greeted with ISC_LOCK in Engage Soft Loops.
Unfortunately we lost lock at Transition_From_ ETMX and again at DRMI
Starting an Initial_Alignment
Notes on OWL:
IFO called Ryan early in the morning https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=81160.
Over the Owl Shift there were a number of locks and locklosses, I'll follow up with a comment to this alog with more information about each lockloss.
Relocking notes:
Relocking has been difficult as it seems the IMC is unlocking at random intervals.
Called Dr. Capote, for back up.
Holding in IDLE for the IMC to become stable.
IMC has been stable for 5 minutes now.
Starting the Initial_Alignment.
I wanted to get to this earlier this morning but a break down of the locklosses last night:
Lockloss ID 1415198551 https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415198551
Multiple - ScreenShots - attached -for this Lockloss - including one of the PSL-FSS_FAST_MON Zoomed way in , but all the normal ones are there too.
This has that weird PSL/ IMC issue and was even tagged so on the Lockloss page.
Lockloss ID 1415193456 An unknown Lockloss. Which this does have some PSL-FSS_FAST_MON motion before hand but it doesnt seem as pronounced. Also it's not tagged as an IMC via the Lockloss page.
Multiple - ScreenShots - attached -for this Lockloss , Just to deliniate from other locklosses
Lockloss ID 1415184378 was an earthquake I'm not attaching screenshots for this one.
Lockloss ID 1415176335 https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415184378
Multiple - ScreenShots - attached -for this Lockloss - including one of the PSL-FSS_FAST_MON Zoomed way in , but all the normal ones are there too.
This has that weird PSL/ IMC issue and was even tagged so on the Lockloss page just like the first one.
H1 called for assistance from the 2 hour "NLN" locking timer expired, We were at LOWNOISE_COIL_DRIVERS and reached NLN shortly after and Observing at 10:41 UTC. I didn't have to touch anything.
TITLE: 11/09 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
I was passed a Locked IFO:
Lockloss potentially Caused by PSL issues: https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1415141124
Relocked by 23:38 UTC
Lockloss potentially Caused by PSL issues https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=81153
Relocked by 3:50 UTC after an Initial Alignment
Unknown Lockloss https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=81156
H1 Is currently Locked and Observing for 2 Hours.
Everything is currently running smoothly now.
LOG:
Josh -> H2 building to retrieve laptop.
J. Freed,
PRM shows very little coupling but there was a strong ~9.6Hz unknown noise was introduced.
Yesterday we did damping loop injections on all 6 BOSEMs on the PRM M1. This is a continuation of the work done previously for ITMX, ITMY, PR2, and PR3
As with PR3, gains of 300 and 600 were collected (300 is labled as low_noise).
The plots, code, and flagged frequencies are located at /ligo/home/joshua.freed/20241031/scrpts. While the diaggui files are at /ligo/home/joshua.freed/20241031/data. This time, 600 gain data was also saved as a reference in the diaggui files (see below), saved in 20241107_H1SUSPRM_M1_OSEMNoise_T3_LN.xml
Unknown Lockloss
This Lockloss does not have the same PSL_FSS signal signaturet that the previous locklosses tonigh have had.
Vickie and I are both thinking that this was a different type of lockloss then what we have seen earlier tonight.
TITLE: 11/08 Eve Shift: 0030-0600 UTC (1430-2200 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 1mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.43 μm/s
QUICK SUMMARY:
H1 has been locked for 1 hour.
All systems running well.
Lockloss potentially Caused by PSL issues
The first Channels that show motion is the H1:PSL-FSS_FAST_MON_OUT_DQ
Relocking now, Currently @ Engage soft loops.
Trends on this lockloss are coincident with PSL FSS / ISS / TPD glitches - so I think the PSL tag is appropriate here.
We added MC2_TRANS to the scope (top right subplot), and it shows power changes earlier than IMC_TRANS_{IN1_OUT}_DQ channels.
I think this means that IMC power changes do happen within 1 ms of FSS glitches starting, which wasn't clear from the IMC_TRANS channel we've been using (where the 16k IN1_DQ and 2k OUT_DQ channels both showed >ms delays of IMC power changing).
