TITLE: 03/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Quiet shift
LOG:
Travis had it locked when I arrived, it's still locked as I leave. EY vacuum was alarming all night, otherwise nothing to report.
CP7 dewar level alarm is due to the level being below 20% -> Accumulated tumbleweeds obstructing the Y-arm access road last Tuesday caused the cancellation of the originally scheduled LN2 delivery. Rescheduled delivery is for this Tuesday. No action is required by the CR operator.
TITLE: 03/13 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: One lockloss due to PSL trip. One unknown cause lockloss. I did have a couple of Tidal X and Y error again tonight during relocking, but they stopped without intervention. Otherwise a quiet night. I did get a call from both Chandra and DaveB about CP7 alarms, although I did not receive any alarms in the control room. Chandra advised to ignore these alarms until Tuesday since the dewar was not filled last Tuesday due to tumbleweed blockage, hence the low level.
LOG: See previous aLogs.
No issues coming back up.
Cause unknown. FOMs look good and environment is quiet.
Begin 1 hour standdown.
No issues coming back up after PSL restart.
PSL tripped. Calling Peter.
TITLE: 03/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.31 μm/s
QUICK SUMMARY: No issues handed off. Looks like a much better start to the night than last night.
Shift Summary: Ran A2L DTT check – Pitch and Yaw are a bit elevated. As LLO is down, dropped out of Observing to run corrective script. A2L script finished with errors. Back to Observing. Spoke with Keita about the A2L Script. See aLOG #34763 for details. Successfully ran the script from a Controls terminal. Pitch and Yaw are now below the reference.
Remained lock for the entire shift. No issues or problems to report.
A good first half of the shift for data collection. No problems or issues to report. Successfully ran the A2L script from a Controls terminal. Keita is looking into the permissions needed to run the script from the Ops terminal.
I am on site this morning to inspect the access roads down the arms and found that Y arm is partially blocked, X are is mostly blocked. I am trying to reach the landscapers at the moment to bring them out tomorrow at noon to start baling on the Y arm. This should give them ample time to clear that road by Tuesday morning and allow the required liquid nitrogen delivery. I have informed Keita of this plan.
There were errors in the A2L script when I ran it this morning. TJ had reported a problem with the script a couple of weeks ago. I had put it on the Ops white board. As the A2L line had been erased from the Ops white board, and there were no aLOG entries concerning the script, I assumed it had been fixed. After running the script with errors, the A2L is now worse than before the script ran. The low frequency noise is elevated. Range is still over 65 Mpc, so will leave it to the Monday crew. The errors are captured in the two attachments.
The problem TJ had was a result of the ASC model changes. Those were fixed that day, and the a2l script had been run successfully since.
It looks like the user account you're using doesn't have permission to write those figure files, so the script is failing on some random trial value of the a2l gain.
Try running the script from a personal account, not ops or controls - that is usually successful, and we can check on the permissions on Monday. If that fails, revert all the values to what they were...that is probably better than whatever trial value the script is leaving in there. Maybe TJ can help me change the script such that it reverts if there is some problem.
After speaking with Keita and reviewing Jenne's comments, I ran the A2L Script from a Controls terminal with no problems. The Pitch and Yaw signals are back to below the reference. Up to about 20 Hz the low frequency noise looks better.
Miriam, Hunter, Andy A subset of blip glitches appear to be due to a glitch in the ETMY L2 coil driver chain. We measured the transfer function from the ETMY L2 MASTER channel to the NOISEMON channel (specifically, for the LR quadrant). We used this to subtract the drive signal out of the noisemon, so what remains would be any glitches in the coil drive chain itself (and not just feedback from DARM). The subtraction works very well as seen in plot 1, with the noise floor a factor of 100 below the signal from about 4 to 800 Hz. We identified some blip glitches from Feb 11 and 12 as well as Mar 6 and 7. Some of the Omega scans of the raw noisemon signals look suspicious, so we performed the subtraction. The noisemons seem to have an analog saturation limit at +/- 22,000 counts, so we looked for cases where the noisemon signal is clearly below this. In some cases, there was nothing seen in the noisemon after subtraction, or what remained was small and seemed like it might be due to a soft saturation or nonlinearity in the noisemon. However we have identified at least three times where there is a strong residual. These are the second through fourth plots. We now plan to automate this process to look at many more blip and check all test mass L2 coils in all quadrants.
In case someone wants to know, the times we report here are:
1170833873.5
1170934017
1170975288.38
I have noticed similarly caused glitches on the 10th March, in particular for the highest SNR Omicron glitch for the day:

![]()
Looking at the OmegaScan of this glitch in H(t) and then the highest SNR coincident channels which are all the quadrants of H1:SUS-ETMY_L2_NOISEMON:


Hi Borja,
could you point us to the link to those omega scans? I would like to see the time series plots to check if the noisemon channels are saturating (we saw that sometimes they look like that in the spectrogram when it saturates).
I am also going to look into the blip glitches I got for March 10 to see if I find more of those (although I won't have glitches with such a high SNR like the one you posted).
Thanks!
Hi Miriam,
The above OmegaScan can be found here
Also I noticed that yesterday the highest New SNR glitch for the whole day reported by PyCBC live 'Short' is of this type as well. The OmegaScan for this one can be found here.
Hope if helps!
Hi Miriam, Borja,
While following up on a GraceDB trigger, I looked at several glitches from March 1 which seem to match those that Borja posted. The omegascans are here, in case these are also of interest to you.
Hi,
Borja, in the first omega scan you sent, the noisemon channels are indeed saturated. In that case it is difficult to tell apart if that is the reason for the spectrogram looking like that or if indeed it might be a glitch in the coil drive. Once Andy has a more final version of his code, we can check on that. In the second omega scan, the noisemon channels look just like the blip glitch looks in the calib_strain channel, which means the blip was probably already in the DARM loop before and the noisemon channels are just hearing it. Notice also that, besides the PyCBC_Live 'short', we have a version of PyCBC_Live that is dedicated specifically to find blip glitches (see aLog 34257), so at some point we will be looking into times coming from there (I will keep in mind to look into the March 10 list).
Paul, those omega scans do not quite look like what we are looking for. We did look into some blip glitches where the noisemon channels looked like what you sent and we did not find any evidence for glitches in the coil drive. But thanks for your omega scans, I will be checking those times when Andy has a final version of the subtraction code.
Head 3 flow rate looks to be the cause. Attached are two trend plots: one for the past 2 hours and one for the past 12 hours. The flow rate looked pretty clean for the past 12 hours before getting ragged. If there were any bubbles in the system because of yesterday's trip, this would be a good candidate for one.