The Legend button has been returned to the CDS Overview. It has been updated to include the RCG version tag.

TITLE: 06/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

H1 is still locked and has been for 5 hours and 45 minutes.
But the DCPDs are diverging again, Like there is some sort of Roll mode ring up again.
Turns out its the Same Roll mode from yesterday. I applied the same gain from yesterday to the roll mode and it has turned around immediately. I have accepted this as an SDF Diff so we can stay observing.
GRB-Short E573164 @ 1454 UTC stand down

it has been requested of me to run the PSAMS script if we were still locked this morning. Camilla just walked and I her and I will start working on PSAMs when the Stand Down ends.

I received an EPICS alarm at 6:27a regarding chilled water supply at EX. I arrived at the end station roughly 10 minutes after. I found the CHWP 2 running normally with normal supply line pressure. The temperature of the water was elevated at roughly 60F and most notably, Chiller 2 was in a run inhibit state stemming from a low refrigerant temp alarm. I reset the alarm, the inhibit condition lifted and the chiller started. It ran normally for about 15 minutes before I left. The chilled water is now back to set point. There is a small incursion to the EX space temp (roughly .4 F) and has since fallen back to its norm.

T. Guidry

Bypass will expire:
Thu Jun 12 01:10:10 PM PDT 2025
For channel(s):
    H0:FMC-EX_CY_H2O_SUP_DEGF
 

TITLE: 06/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

Currently Observing at 145 Mpc and have been Locked for over 8.5 hours. The wind is still a bit elevated and not very consistant. We do have an eaerthquake coming in, but it doesn't look like it'll be too bad (although it might cause a lockloss if the wind doesn't go down a bit).

I turned the roll damping off and accepted the sdf.

Occassionally PI24 will ring up and cycle through all the phases until it gets back to one that works, so I really need to work on that guardian and fix that. Luckily though, we haven't needed to do XTREME_DAMPING, so we've been able to stay in Observing during those ringups.

LOG:

23:30UTC Observing and have been Locked for 2.5 hours
04:30 Pushed out of Observing due to SQZ unlock
04:32 SQZ relockes by itself and we go back into Observing
05:25 Dropped out of Observing due to needing to turn the Roll gain off and accept that SDF diff
05:25 I accepted the diff and we went back into Observing

Observing at 146Mpc and have been Locked for 6.5 hours now.  The wind is a bit elevated and has been going up and down, but the ifo has been handling it well and it should go down a bit over the next couple of hours.

The ETMX roll mode is looking good, as are violins.

I edited the userapps/.../sqz/h1/scripts/SCAN_PSAMS.py script to use the 350Hz BLRMS rather than the high frequency ones to set SQZ angle. If locked at the start of commissioning tomorrow, we should pause SQZ_MANAGER guardian and then run this script.

TITLE: 06/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 24mph Gusts, 18mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.14 μm/s
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Recovered from the earlier lockloss!
An Initial_Alignment was ran, and we got back up to Nominal_Low_Noise at 20:46 UTC 
I did have to accept some SDF diffs for the SEI system, and reached out to Jim about it. He mentioned that the some of those channels should not be monitored.
When the SEI ENV went back to calm, and it dropped us from Observing a few moments later we unmonotored those channels.
We got back to Observing at 21:04 UTC

21:10 UTC we fell out of Observing because of a SQZ issue, returning to Observing at 21:24 UTC


SUS ETMY Roll Mode is growing!
H1:SUS-ETMY_M0_DARM_DAMP_R_GAIN was changed to account for an interesting Roll mode on ETMX, and accepted in SDF. YES, Ya Read That Correctly and I didn't make a mistake here. Changes to ETMY  damped a Roll mode on ETMX .
The Ops Eve Shifter should revert this change, before handing off the IFO to the Night Owl Op.

H1 has been locked for 2 hours and 40 minutes and is currently OBSERVING.

LOG:

TITLE: 06/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 24mph Gusts, 12mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

Currently Observing and have been Locked for almost 2.5 hours. Keeping an eye on the roll mode and it's still low.

Elenna, Camilla, Jenne, Ryan Short, Tony

We saw an increase in the DCPD monitor screen, which the roll monitor identified as ETMX roll mode.  The existing settings from a long time ago used AS A YAW to damp roll modes, I attempted to damp this by actuating on ETMY, which seems to have worked with a gain of 20. (settings in screenshot)

Camilla trended the monitor, and sees that this started to ring up slowly around 7 am today. 

We've gone back to observing with this gain setting, but we plan to turn it off when this looks well damped (if we are still locked by the end of the eve shift, we should turn it off so the owl operator doesn't get woken up by SDF diffs).

Kiet, Robert, and Carlos

We report the results of calibrating the LEMI magnetometers in the Vault outside of the X arm; 

We went out on May 15th, 2025 and took the following measurement with each lasted 2 minutes.
Far field injection: to calibrate the LEMI 

1) 17:36:45 UTC; X-axis far-field injection; without preamp on the Bartington 

2) 17:43:23 UTC; X-axis far-field injection; without preamp on the Bartington 

3) 18:01:53 UTC, X-axis far-field injection; without preamp on the Bartington 

4) 18:04:15 UTC, X-axis far-field injection; without preamp on the Bartington 

5) 18:23:25 UTC; Y-axis far-field injection; with preamp on the Bartington 

6) 18:26:00 UTC; Y-axis far-field injection; with preamp on the Bartington 

The preamp gain is 20; all injections are done at 20Hz. The coil used for far field injection has 26 turns, 3.2 Ohms.

The voltage that was used to drive the injection coil for farfield injection: Vp-p: 13.2 +- 0.1V. It was windy out so we decided to use the preamp on the Bartington magnetometer.
The LEMI channels used for this analysis: H1:PEM-VAULT_MAG_1030X195Y_COIL_X_DQ; H1:PEM-VAULT_MAG_1030X195Y_COIL_Y_DQ

Bartington calibration

7) 18:49:38 UTC; with preamp on the Bartington 

8) 18:52:50 UTC;  with preamp on the Bartington 
the voltage that was used to drive the injection coil for farfield injection: Vp-p: 1.88V +- 0.01V 
We inserted the bartington magnetometer to the center of a cylindrical coil to calibrate its z axis(1000 Ohms, 55 turns in 0.087 m) 

The final results of LEMI calibration after taken accound the all the measurements is (9.101 +- 0.210)*10^-13 Tesla/counts, there is a 20% difference between this measurement and the measurement taken pre O3. Robert noted that when taking the previous measurements, the calibrating magnetometer was not fully isolated from the LEMI. This time they are completely independent.

We recommend analyses that use LEMI data to use the calibration value of  9.101 * 10^-13 +- 5% Tesla/counts to be consersative.  

Using Camilla's No SQZ time yesterday, I made a comparison to the No SQZing time from Mar 26 2025 16:01 UTC GPS Time: 1427040078.  
Note: I'm not sure how much of an effect this has , but Camilla's No SQZ time was before the Calibration Update yesterday.
Here we see a broadband loss of range from 2-7  Mpc starting around 50hz and above. 
 

After H1 lost lock this morning, the vacuum team started some work on HAM1, which gave me an opportunity to do a much-needed adjustment of the FSS RefCav alignment. As I expected, this was a very straightforward alignment where I was able to get immediate and significant improvements by walking the beam into the RefCav mostly in pitch, but some in yaw also (all with the IMC offline). My results:

• TPD start: 705 mV
• TPD end: 830 mV

A great improvement; even better than the alignment was before the drop-off over the weekend.

Lockloss @ 18:33 UTC after 12.5 hr lock stretch - link to lockloss tool

Looks to be from some very local sudden ground motion. USGS has nothing to report yet, but site seismometers and Picket Fence certainly saw activity.

Here is an executive summary of the ASC changes that have been made, why they were made, and the potential impact on the noise:

• DHARD P boost is currently disengaged
  • as a part of investigating a still-mysterious 1 Hz instability, I disengaged FM8, which is usually engaged in LOWNOISE_ASC.
  • This boost was designed by Gabriele to reduce the DHARD P RMS, which was beneficial to reducing the DARM RMS
  • This may overall impact the DARM RMS
• MICH P and Y have been reverted to an older loop design
  • during locking, some 0.5 Hz ring ups in the MICH ASC impacted locking, even causing a lockloss
  • I changed the loop design back to a design that was in place pre-O4, which uses FM7 instead of FM10 in MICH and FM5 instead of FM10 for MICH Y
  • This may result in more MICH ASC noise coupling to DARM
  • Changing back to this old design has reduced the RMS in MICH P and Y
• Disengaged BR filter in MICH P and Y
  • I disengaged a bounce/roll filter in the MICH ASC that had been added during O4. We disengaged this same filter in the MICH LSC
  • We may see the beamsplitter B/R modes in DARM, but unlikely because we have dampers on the BS for this
• A new DC centering loop, DC6
  • centers the beam on POPX using PM1
  • likely very low coupling to DARM
• PRC2 ASC is now on POPX
  • this would change the noise in the loop, however PRC2 has very low coupling to DARM, unlikely to impact noise

I ran a coherence in NLN with all the arm loops, MICH and PRC2 ASC. There is some coherence with CHARD P, and with MICH P and Y that would be worth investigating with a noise budget injection.

I went down to end Y to retrieve the usb stick that I remotely copied the c:\slowcontrols directory on h1brsey to, and also to try to connect h1brsey to the kvm switch in the rack. I eventually realized that what I thought was a vga port on the back of h1brsey was probably not, and instead I found this odd seeming wiring connected from what I am guessing is a hdmi or dvi port on the back of h1brsey, to some kind of converter device, then to a usb port on a network switch. I'm not sure what this is about, so I am attaching pictures.

TITLE: 06/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY:
H1 was in IDLE when I arrived.
I will start trying to lock now.