TITLE: 08/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Detector still Observing and has been Locked for 37hrs 37mins.
Throughout my shift there were a few instances where a GW candidate came in on GraceDB with the EARLY_WARNING tag(but very high FAR), and then possible subthreshold GRB candidates that came in closely after would cause Verbals to announce them.
Also, around 8/25 4:36ish UTC, I noticed that the lock clock said to stand down, but there had been no alert on Verbals, and going to GraceDB, there hadn't been any GRB events in the previous couple of hours.
23:00UTC Detector in Observing and Locked for 29.5 hours
23:19 SubGRBTargeted on Verbals E432118
23:22 SubGRBTargeted on Verbals E432119
- A bunch more SubGRBTargeted on verbals, along with some getting repeated alerts a few minutes later
23:24 Earthquake mode activated for earthquake from Japan (and from off Oregon Coast)
23:24 Back to CALM
23:39 Earthquake mode activated from another earthquake from off the coast of Oregon
23:49 Back to CALM
4:36ish - 4:43UTC lock clock says to Stand Down
LOG:
no log
We're going on 34 hours of being Locked and Observing at 147Mpc.
Genevieve and I did about a dozen scattering injections in the LVEA on July 20th and 21st. For this round of injections we inserted the retro-reflector into the guillotine port for 10 seconds, removed for 10 seconds and repeated 6 times. We are still working through the data on those but it appears as if we had some scattering noise on HAM3 in the left guillotine port. There is an increased noise source present when the reflector is inserted. I did more scattering injections yesterday on HAM3 and HAM6 during commissioning and will parse through that data soon. Spectrograms of accelerometer on HAM3 and DARM: -Acc -DARM -Stacked with red lines around the time the reflector was inserted and noise was present
TITLE: 08/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 13mph Gusts, 9mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
Taking over for Ryan C. Detector in Observing and has been Locked for 29.5 hours. The EX Pirani pressure gauge, VAC-EX_X2_PT524B_PRESS_TORR, is still down even though it should have come back up by now (tagging vacuum team even though they know already).
L. Dartez, J. Kissel We're investigating some issues with time-dependent correction factors (TDCFs) as computed by the front-end vs. GDS, and reminding ourselves of the parameters that define the "smoothing out" of the computation. In particular the uncertainty threshold against which the live uncertainty is compared. Apparently, all front-end thresholds are set at 5% uncertainty. H1:CAL-CS_TDEP_CAVITY_POLE_F_C_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_CAVITY_POLE_KAPPA_C_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_D2N_SPRING_F_S_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_D2N_SPRING_Q_S_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_KAPPA_PUM_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_KAPPA_TST_GATE_UNC_THRESH 0.05 H1:CAL-CS_TDEP_KAPPA_UIM_GATE_UNC_THRESH 0.05 (Remember, the live uncertainty is defined by taking each calibration line's coherence, coh, with DARM_ERR, converting it to uncertainty via sqrt([1-coh]/[2*Navg*coh]), where Navg is determined by the FFT length -- see LHO:69175 for a recent review of this calculation.) I could make up a story from my foggy memory as to why the front-end thresholds are set at 5% (and not 0.5%, like we expected -- and like what we *think* the GDS pipeline's threshold is), but I'll spare you. They've been this way since Apr 2021. Attached is the time-series comparison between GDS (in red) and Front-end (in gray) computed \kappa_C for the 24 hour period after July 31 2023 00:00 UTC. The gray, front-end trace shows the characteristic ~3 hour thermalization transient we've come to know and love from our 76W IFO (see e.g. LHO:69796). The red trace, doesn't show this, and it's in fact frozen at the "last good value" by the GDS gating system -- because it's uncertainty threshold is much lower than 5%. We presume that this is because the detector noise was pretty DARM bad during this time period -- see 24-hour statistics on the sensitivity in second attachment.
TITLE: 08/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Pretty quiet day, no commissoning activites today. We stayed locked and Observing the whole shift, 29:36 lock time as of 23:00UTC
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:02 | EE | Ken | H2 | N | Lights | 17:02 |
16:53 | FAC | Cindy | MidY | N | Tech clean | 18:41 |
19:41 | EE | Fil | MidY | N | 05 electronics inventory | 20:50 |
21:38 | PCAL | Tony, Nyath | PCAL lab | LOCAL | PCAL work | 21:46 |
Following up on TJ's alog from 8/17 (72293), it was noted that a garbage truck at LSB was quite loud. The seismometers in the LVEA clearly picked up the noise, and it seems to coincide with noise in DARM. It's hard to be certain with only one signal, but it probably warrants further investigation.
Spectrogams attached of one seismometer and DARM for 2 minute time span around when noise was reported:
-Of signal
-Zoomed in with boxes on noise regions
-Stacked with some boxes around correlated noise
Oli relayed to Genevieve that the garbage truck left at 16:05:00 local time yesterday (8/24). No noise was reported on site, but approximately 2 minutes before the truck left we see a signal in the LVEA seismometers similar to that from the truck last week, and the signal once again shows up in DARM.
Thu Aug 24 10:16:47 2023 INFO: Fill completed in 16min 42secs
Travis confirmed a good fill curbside.
TITLE: 08/24 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: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 3mph Gusts, 1mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
TITLE: 08/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Nice smooth shift with Ryan taking H1 to Observing minutes before the shift and H1 staying in Observing the whole shift (w/ only one M5.4 Mariana Islands EQ of note & not an issue). There was also O4's 34th Gravitational Wave candidate (S230824r).
LOG: N/A
TITLE: 08/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 11mph Gusts, 7mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.13 μm/s
QUICK SUMMARY:
H1's been locked for just over 6hrs (& in observing the last ~30min and L1 joining slightly after us). Fairly nice environmentally (w/ winds calming in the last hour).
Alarm Handlers:
Important Highlights
Other Highlights
After chatting with Sushant at LLO, I followed his advice to add a bit of weight to the minimization metric at 60 Hz, and was able to get cleaning parameters that do a pretty good job of subtracting jitter and laser frequency noise, but don't inject noise at the 60 Hz line. The jitter subtraction is a little less good than alog 72276, but it's important to not inject noise with the cleaning, so this is a good balance. I similarly retrained the laser noise, and with both of them on (while other commissioning work was ongoing), I see good subtraction and no noise injection at 60 Hz. This is shown in the first attachment.
After having collected a bit of time with the jitter and laser noise subtracted, I retrained the LSC modulated cleaning. Unfortunately, when trying it in the online system (I don't have the offline mimic of this working yet), it needs a similar mysterious minus sign much like the jitter subtraction needed until I recompiled the code last week. I'm starting to suspect that the LSC NonSENS c-code also needs to be regenerated and recompiled, and hopefully that will solve my minus sign issue. Anyhow, when the LSC noise estimate has that minus sign in place, it gives a reasonable amount of subtraction, as shown in the second attachment.
The third attachment shows the improvement (when blue is above pink/orange) in range from the cleaning. Around 19-20 hours on that plot I'm just subtracting jitter and laser noise. Around 21 hours I add in LSC subtraction, and we get back to ~150 Mpc. So, likely our LSC FF is becoming mistuned, and we'd benefit from either retuning the LSC FF or finally implementing the NonSENS subtraction.
The cleaning review committee meets tomorrow. All of this is turned off when the IFO is in Observing until given approval by the review committee.
While some calibration work was ongoing, I turned off the HAM1 -> CHARD feedforward, so that Elenna / Gabriele can potentially retrain the filters to make further improvements now that Jim has installed new HAM1 seismic feedforward filters (alog 72393).
The switch H1:HPI-HAM1_TTL4C_FF_OUTSW was off from 23 Aug 2023 22:03:47 UTC to 22:55:20 UTC.
TITLE: 08/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Optics lab and PSL anteroom dust alarms have been off and on today just as yesterday.
Lock#1:
Lockloss at 15:33UTC
Lock#2:
No flashes on DRMI or PRMI, tried check mich, no luck, went into IA. I had to help out Yarm during green arms (ENABLE_WFS state on Yarm) by tapping pitch a microradian.
NLN at 17:20UTC with no interventions, in Observing at 17:35UTC.
Out of Observing at 19:08 for planned commissioning work. I brought us to NLN_CAL_MEAS to take a calibration measurement at 21:33UTC
Back into Observing at 22:55UTC
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:29 | EE | Ken | MidY | N | Light fixtures | 19:26 |
16:12 | FAC | Randy | MidX | N | Parts check | 16:32 |
16:35 | Lance | LVEA | N | Quick check | 16:40 | |
16:39 | FAC | Cindy | Wood shop | N | Tech clean | 17:21 |
16:52 | PCAL | Tony | PCAL lab | LOCAL | Martel measurement | 17:08 |
17:21 | FAC | Cindy | Mech room | N | Tech clean | 18:13 |
19:09 | SQZ | Vicky | Remote | N | SQZ work | 20:12 |
19:32 | FAC | Ken | H2 | N | Drop off lights | 20:36 |
20:11 | PEM | Lance | LVEA | N | Scatter injection, HAM3 | 21:17 |
20:37 | EE | Ken | MidX | N | Pick up equipment | 21:03 |
21:00 | ISC | TJ | FCES | N | Grab stuff | 21:22 |
21:08 | SEI | Jim | CR | N | HAM1 FF | 22:08 |
21:34 | CAL | RyanC | CR | N | Calibration measurement | 22:05 |
I reduced the amplitude of the 17.1 Hz PCALY calibration line. This is a continuation of LHO:71945. Channel Old Gain New Gain Reduction Factor ================= ========= =========== =========== H1:CAL-PCALY_PCALOSC1_OSC_SINGAIN 250 115 2.17 The changes have been saved to observe and safe snap files in the SDF system.
Louis double checked, and these are not touched by Guardian, so with these SDF saves everything should come back just fine next lock.
Naoki, Vicky
Today we tested higher generated SQZ level and FC detuning, summary screenshot here. We turned up non-linear gain from NLG 11 to 17, so gen sqz level from 14.7dB to 17dB, and very barely got more sqz (< 0.2dB?). We set it back to the "normal" 80uW operating point, leaving the injected sqz level unchanged. We ended up changing FC detuning from -25 Hz to -28 Hz. Notes:
I stole the filter that Huyen used for her HAM1 feedforward test, and tried it on the LHO HAM1, with a gain tweak of 17% (ie I multiplied by a gain of 1.17 vs LLO ) to match my measurements and it seems to work well. I was having difficulty with my hand fits with excess low frequency noise or gain peaking where I tried to roll my filters off. First plot shows the on/ off asds for the HAM2 sts and the HAM1 Z HEPI l4cs. I don't know if I quite believe the improvement below 1 hz is due to the feedforward, but Huyen said she got improvement kind of 1-70hz and that seems to be the case here as well. I'm leaving this filter on overnight, to get good low frequency data.
Second image compares one of my filters(red) with the (green) LLO filter. One thing I still don't understand is that my filters have often caused broad low frequency noise, but the LLO filter doesn't seem to. We don't currently have a noise model for HEPI that allows modeling the ff performance, that would help a lot.
Attaching long spectra comparing HAM1 with the LLO feedforward. Still looks pretty good, we should run with this. Live traces are with the feedforward on, refs are with it off, so the improvement in the HAM1 HEPI l4cs is brown to bright green, so something like a factor of 20 improvement at 15 hz, which is the frequency where HAM1 just catches briefly up to the performance of HAM 2 and 4 with this feedforward running.
Second plot compares CHARD pitch asds during these same times. The improvement here is less dramatic, but there is still a factor of almost 2 around 8-9 hz. I suspect the low frequency (.1hz and below) differences is due to wind. I looked at cal deltal, but it seems that squeezing was off or something during my reference time, there's a lot of extra signal above 10 hz.
DCPD saturation then lockloss
A few signals saw a kick less than a second before the lockloss, and it looks like CSOFT rang up
If you get a refined time for the lockloss by looking at ASC-AS_A_DC_NSUM_OUT_DQ, you get that the power fell off the PD at 15:33:23.95UTC (1376840021.95)(see attachment - PD channel is bottom right), so the kicks in the ASC channels happened right after the lockloss. That being said, the jumps in the ASC channels right after the lockloss are all kind of small looking? as opposed to the giant jumps we usually see.