TITLE: 06/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 2mph 5min avg
Primary useism: 0.07 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
There is still some ground motion happening. be we are going to try to relock.
IFO Current status: Relocking due to earthquake.
TITLE: 06/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
SHIFT SUMMARY: Multiple locklosses overnight from earthquakes.
Lock #1:
Lock #2:
Lock #3:
Lock #4;
Handing off to Tony for the day.
LOG:
No log for this shift.
Lockloss @ 14:14 UTC from a magnitude 5.8 earthquake from New Zealand. This lockloss happened at the same time as seismic configuration moved to EARTHQUAKE.
Holding in DOWN for ground motion to settle, then will start relocking.
Just a note that the lockloss tool did not log this as an earthquake lockloss. The buildups are very clearly oscillating at low frequency in the last few minutes leading up to the lockloss, and the seismic FOM shows increased ground motion. I am not sure what triggers an earthquake tag in the lockloss tool but I figured it would be useful to know that the tool did not properly classify this one.
Lockloss @ 10:05 UTC from what seems to be a nearby and sudden seismic event. The motion appeared quickly in both 0.03-0.1 and 0.1-0.3 Hz frequency bands and Picket Fence did show small motion on all sensors a minute or so after the lockloss. This event does not correspond to any earthquake reported by USGS.
Seismic configuration did not switch to EARTHQUAKE until the second wave hit (around -5m on attached ndscope). Waited in DOWN for about 10 minutes for ground motion to calm down, now relocking (and anticipating an incoming 6.2 from Japan).
The timing of this event in relation to the 6.2 magnitude quake from Japan is noteworthy, but this lockloss occurred before seismon or the USGS site reported the incoming Japan quake, which is why I hesitate to say whether the two events are the same or not (but still entirely possible).
TITLE: 06/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 135Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 7mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: Taking over from Austin. H1 has been locked and Observing for over 1.5 hours.
TITLE: 06/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 136Mpc
SHIFT SUMMARY:
- Lock #1:
- Lock #2:
- After the EQ, decided to do an IA just to make sure the alignment is still ok
- Lock #3:
- Leaving the IFO to Ryan S. locked and in observing
LOG:
No log for this shift.
H1 just unlocked potentially due to an 5.2 EQ from Japan (though I'm a bit skeptical that this was 100% the cause for reasons listed here). Doing an IA just to be safe and will begin relocking shortly.
LOCKLOSS @ 3:43, this one might be from the EQ. Interestingly enough, SEI_CONF went to CALM (it went to the EQ state, but there was no indicator on Verbal that it ever transitioned in the first place?), and we lost lock shortly after. Notice right after the lockloss the MC_TRANS camera was moving quite significantly in pitch, more evidence that this was potentially motion related.
However, the peakmon ndscope was showing very little movement (~100 counts at the time of the lockloss - scope attached), also the BLRMS for the EQ band was at or right below 0.1 um/s. This is pretty contradictiory, I'm wondering if this was just a coincidence and not EQ related at all? Tagging SEI
EDIT: The lockloss tool did not tag any ground motion related tags, and the lockloss select tool is not showing any ASC/LSC ringups from my eye, conclusion: inconclusive.
LOCKLOSS @ 23:53, looking at the lockloss select, potentially movement in CSOFT P, also noticing some instability in the LSC loops as well - scope attached - Tagging ISC
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
17:21 UTC a tour group came through the control room.
Confirmed a slow Climb in IMY Mode5. Gain H1:SUS-ITMY_L2_DAMP_MODE5_GAIN was set at -0.04 and I changed it to 0.
Looking at alog 70057 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=70057 I will try a gain of +0.01
Lockloss 19:50 UTC of unknown cause.
Locking Summary:
No Initial alignment was done before trying to lock again.
DRMI 1f didn't lock but i let it go to Aquire PRMI which then locked and we went on up.
NOMINAL_LOW_NOISE Reached at 21:04 UTC
Intention bit set to Observing 21:09 UTC.
Violin Modes:
ITMY mode 8 is increasing again. I will take the gain to 0 then then up to +0.04 as described in the following alog.
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=70057
That singular change of gain did not make any difference, but taking the gain back to 0 then turning on FM7 which is a -30 deg phase change then bringing the gain back up to 0.04 did start bringing ITMY Mode 5 down. Tagging SUS
IFO Current Status: NOMINAL_LOW_NOISE & Observing
TITLE: 06/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 135Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
- SEI/DM/CDS ok
- H1 is locked and in observing as of 21:04 UTC
The first attachment shows the distribution of data during O3, ordered by how long into a high-power lock stretch the data were taken. High-power lock segments were identified by either H1:GRD-LASER_PWR_OK:1 or L1:GRD-PSL_OK:1. Solid lines show the data during observing mode only ([HL]1:DMT-ANALYSIS_READY:1); dashed lines show all data accumulated during high-power operation.
Half of observing-mode data were accumulated within the first 9 hours of lock, a third of data were accumulated within the first 6 hours of lock, and a fifth of data were accumulated within the first 3 hours of lock. The distributions are remarkably similar between H1 and L1, and so far, L1's distribution for the first few weeks of O4 seems similar to the distributions for O3.
The second attachment shows the distribution of data during O3, ordered just by total lock length (i.e., without regard to how far into a particular lock stretch the data were taken). Half of observing-mode data were accumulated during locks of more than 20 hours.
Lockloss occured at 19:50 UTC:
Lockloss select URL : https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1370461864
Cause currently unknown, awaiting analysis.
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
Sat Jun 10 10:11:44 2023 INFO: Fill completed in 11min 43secs
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Current IFO Status: NOMINIAL_LOW_NOISE and OBSERVING for 6+ hours.
TITLE: 06/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 140Mpc
SHIFT SUMMARY: Mostly quiet shift after relocking and riding out earthquakes.
Handing off to Tony for the day.
LOG:
No log for this shift.
H1 has relocked and is Observing as of 08:37 UTC. There was one SDF diff on the CALEX model when we reached NLN regarding a PCal X OSC time ramp that appears to have been changed at the time of last lockloss. Since this is just a time ramp, it seemed harmless enough to revert it, which I did (tagging CAL, screenshot attached).
TITLE: 06/06 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 133Mpc
SHIFT SUMMARY: About to start maintenance day.
LOG:
H1 glitches nuc27 FOM isn't updating for Omicrom. I posted this in the LHO DetChar chat.ligo group.
I've had to restart the DARM FOM on nuc30 3 times and Ryan noted he did ~4 times during the evening. Tagging CDS.
I expected PEM magnetic injections to start at 7:25am, it was 14:30UTC to 14:48UTC. SUS_CHARGE started at 14:45UTC with lines at 11-14Hz when PEM_MAG_INJ was stilll at EY_EBAY_HIGH_INJ. So they overlapped by 2-3 minutes. Tagging PEM and Tagging SUS In-lock charge measurements caused a lockloss again at 15:00UTC 70062.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 13:21 | CDS | Erik | Remote | N | Rebooting work stations | 13:21 |
| 14:17 | COMM | Camilla | CR | N | PRCL OLG Measurement | 14:27 |
| 14:30 | PEM | PEM_MAG_INJ GRD | Auto | N | Automatic magnetic injections | 14:48 |
| 14:45 | SUS | SUS_CHARGE GRD | Auto | N | Automatic in-lock charge measurements | 15:01 |
To fix the overlap between the magnetic injections and in-lock charge measurements, I've moved the start time of the magnetic injections up to 7:20am from 7:25am (tagging PEM).