TITLE: 07/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

• We've been locked for just over 9 hours
• Wind is low/moderate, and secondary microseism is low
• 5.0 earthquake's R waves coming in from Japan in 10 minutes

Signal railed about 6:28 PM local time, I checked trend data for PT120 and no pressure rise noted inside the main volume.  Attached is a 14 hour trend of the pump behavior and PT120 (main volume internal pressure).

System will be evaluated as soon as possible.

TITLE: 07/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Currently relocking and in MOVE_SPOTS. This last relock was looking so bad up until ENGAGE_ASC_FOR_FULL_IFO, I am very surprised it made it (40min build ups). The first lock reacquisitoin of my shift, ALSX was having some issue with the crystal frequency and was losing lock a lot. Also, there were many times when it was looking really bad but would hold on (ndscope). Besides ALSX having trouble that first round of relocking, there haven't been any issues.
LOG:

21:20UTC Observing at 137Mpc and have been Locked for 29 minutes
21:23 Dropped out of Observing to touch up OPO temperature and run scan sqz ang
21:27 Observing

22:34 Lockloss
    - Alignment looked so bad during DRMI. I tried adjusting for a while, but eventually started an initial alignment
    - Multiple lockloss due to ALSX unlocking
00:52 NOMINAL_LOW_NOISE
00:55 Observing

04:12 Lockloss                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     

A partial continuation of showing the characterization of the OSEM noise before versus after the satellite amplifier swaps. Today, PR2, MC2, TMSX, and ETMX M0 R0 L1 were swapped out (85770), but here I am only showing the comparison plots for PR2 and MC2. I will have to wait until we have a longer period of being in DOWN before I can get good comparisons for TMSX and ETMX because there has not been very much time after the swaps where we weren't locking or where the seismic environment wasn't set to maintenance, which results in a ton of extra noise that isn't able to be properly regressed out.

Here are the previous comparisons: 85485, 85699

PR2
Results
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR2/SAGM1/Results/allDampRegressCompare_H1SUSPR2_M1_NoiseComparison_1435154988vs1436654703-1200.pdf
r12453
Data
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR2/SAGM1/Data/dampRegress_H1SUSPR2_M1_1435154988_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR2/SAGM1/Data/dampRegress_H1SUSPR2_M1_1436654703_1200.mat
r12453

MC2
Results
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC2/SAGM1/Results/allDampRegressCompare_H1SUSMC2_M1_NoiseComparison_1436631330vs1436638358-1200.pdf
r12454
Data
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC2/SAGM1/Data/dampRegress_H1SUSMC2_M1_1436631330_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC2/SAGM1/Data/dampRegress_H1SUSMC2_M1_1436638358_1200.mat
r12454

Lockloss at 2025-07-16 04:12 UTC after almost 3.5 hours locked

Closes FAMIS#28414, last checked 85483

The ITMX measurements actually had enough coherence this week!

ITMX

ITMY

ETMX

ETMY

9:00 - 12:30
Janos

The Kobelco compressor and drying towers have been switched on today during the maintenance period for validation purposes (similarly to the EX dry air system earlier - aLog 85469). At the X-manifold, a KF50 venting port has been opened up, and the air was flowing with full throttle during 3.5 hours. Despite of this, the compressor kept stopping, and the dew point went down nicely.
The measured data:
- Dew point right before switching off the dryer towers (measured by the in-built dew point meter): -49 deg F (=-45 deg C)
- Dew point at the end of the testing period at the X-manifold venting port (measured by our portable dew point meter): -43.6 deg C
- Particle count at the end of the testing period at the X-manifold venting port (measured by our portable particle counter): 0 for all sizes
- FTIR tests have also been taken at the vent port, and the vial is now in storage

This completes the installation and validation process for the Kobelco, and so it is now OK to use for venting (similarly to the EX system).

Lockloss at 2025-07-15 22:34 UTC from unknown causes

Using Vibration Sensors To Gauge Health Of HVAC Fans Site Wide Famis 26406

 

Monthly Dust trends FAMIS 37254

I've attached the Dust mon plots for the past month.

I have moved the DHARD control to be distributed between AS A and B RF45 Q instead of only on AS A RF45 Q to see if we can reduce the noise in DHARD.

On Monday, I ran an injection in DHARD P and Y (see pitch, see yaw) and determined that both AS A and B RF45 Q have equal SNR for DHARD. The difference is the phase, AS B RF45 is the opposite sign as AS A RF45. Therefore, I figured we could try a new sensing scheme, instead of using just AS A RF45 Q, we would use 0.5*A and -0.5*B signals.

Today, I first tested this by putting in my new input matrix into DC7 pitch and yaw. I watched my new signal compared to the nominal DHARD signal during the engagement of DHARD WFS. There were no offsets in the signal. I ran a quick passive transfer function to determine that the signals have the same magnitude and phase.

Then, Tony was holding us at 2 W to sweep the LVEA before observing, so I used the opportunity to try the new matrix. I put the new matrix in the DHARD B path, aka the DHARD blend filter path. I then ramped halfway between DHARD A, which is just on AS A, and DHARD B which is distributed between AS A and B. This worked well, so I ramped the rest of the way. This worked perfectly for both pitch and yaw. I decided I liked this, so I put the new intrix back in DHARD A and ramped back so I wouldn't have to deal with extra SDF diffs.

I continued to monitor the signals as we powered up and saw that everything was performing well. I updated the guardian to use this new intrix- this matrix is set in the DARM_TO_RF state, and then DHARD is first engaged at DHARD_WFS.

Sensibly, this corresponds to about a sqrt(2) reduction in the DHARD noise above 10 Hz, comparing the signals from today to signals during observing last night.

I accepted the differences in observe SDF as well. Note that I also accepted a CHARD tramp due to some other ASC changes I reported in this alog.

Leo, Jennie, Camilla, WP 12677

Setup steps:

• To get a clear SQZ beam to see, we turned up the SEED power from 0.6mW to 10mW (H1:SQZ-SEED_LAUNCH_DC_POWERMON with H1:SYS-MOTION_C_PICO_I  MOTOR 6).
• To stop ISC_LOCK interfering with us, I look SQZ_MANAGER to DOWN, AUTO and paused it. (As SQZ_MANGER is paused, the beam disappears, it could be that SQZ_PMC or SHG unlocked, and you need to re-request them to LOCKED).
• We then took SQZ_OPO_LR GRD to LOCKED_SEED_DITHER. Can watch it lcok using SQZ > SQZ Overview > SQZ scopes > "OPO locking" or "opo-ir dither locking".

Opened up the back side of SQZT7 and used the Nanoscan beam profile to profile the SQZ beam in 5 points between the LPM and MR13 (layout D2000242) with the nominal PSAMS settings [ZM4 92V Strain 6.0, ZM5 109V Strain -0.4]. And repeated with PSAMS set to 0V,0V [ZM4 0V Strain 2.25, ZM5 0V Strain -5.4], results attached, Leo will analyze.

To change PSAMS to Voltage we wanted:

• Turned off the PSAMS servo by ramping H1:AWC-ZM{4,5}_M2_SAMS_SERVO_GAIN to 0
• Edited the H1:AWC-ZM{4,5}_M2_SAMS_OFFSET with a 5s ramp time.
• Alternatively if we wanted to measure at set strains, we could have left the servo on and edited H1:AWC-ZM{4,5}_M2_STRAIN_VOLTAGE_TARGET.

Before we went back to squeezing, reverted the PSAMS offsets and put the servos back on (after clearing their histories), reduded SEED power back down to 0.6mW, also adjusted waveplates for PUMP rejected power, disabled picos and turned off OPO EXC that the dither lock left on.

TITLE: 07/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 28mph Gusts, 16mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

Currently Observing at 137 Mpc and have been Locked for 27 minutes. The wind is reaching 30mph.

LVEA Has been Swept,
I found that there was a hissing coming from an open connection from a Kobelco compressor.
Jordan has since shut that off.

WP 12675
WP 12676
ECR E2400330
Drawing D0901284-v5
Modified List T2500232

The following SUS SAT Amps were upgraded per ECR E2400330. Modification improves the whitening stage to reduce ADC noise from 0.05 to 10 Hz. The EX PUM SAT Amp was NOT upgraded. 

F. Clara,  J. Kissel

I wrote this state at the end of 2023, to automate the relocking of the PLL through turning on the Beckoff autolocker and inputting crystal frequency values to search around. These frequencies it uses to search are assuming the values will be close to zero, so it assumes there isn't an offset alog81425.

We've been going into this fault state more often recently. This state is more of a band-aid for this issue than an actual fix to whatever's happening with the PLLs. ALS-Y sees this issue more frequently than ALS-X, each arm is locking at a different frequency these days, around 0 Hz for Xarm and around 100 for Yarm. Yarm seems more dynamic than Xarm for its' frequency, it has been changing more than Xarm over the past year.

I've updated the code today to use a dictionary with a list for each arm from the single list it was using so hopefully it will make it a little faster.

I'm writing some code with Tonys' statecounter to see exactly how many times we are going into this state for each arm over the past months, and years.

FAMIS tasks 31305 and 31320, WP 12682

Procedure checklist for both stations completed.  No issues were identified at this time.

MX: Scroll pump hours: 228.5
       Turbo pump hours: 140
       Crash bearings: 100%

EX: Scroll pump hours: 7155.9
       Turbo pump hours: 1108
       Crash bearings: 100%

I previously noted a glitch about 30 seconds before lockloss in LOWNOISE ASC, 85685. However, we had two more locklosses from this state last night and I do not see such a glitch so that is a random coincidence. One of those locklosses appears to be caused by an earthquake. However, since 6/11, we have had 9 locklosses in this state that occurred exactly 47 seconds into the state, which seems suspicious, one of those occurred last night, and the lockloss with the glitch was the same.

This seems to be coincident with the engagement of a few DHARD P filters:

2025-07-14_14:26:54.641531Z ISC_LOCK executing state: LOWNOISE_ASC (522)
2025-07-14_14:26:54.642230Z ISC_LOCK [LOWNOISE_ASC.enter]
2025-07-14_14:26:54.655894Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT3_OSC_CLKGAIN => 300
2025-07-14_14:26:54.656325Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT4_OSC_CLKGAIN => 300
2025-07-14_14:26:54.656732Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT5_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657043Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW3_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657438Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW4_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657892Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW5_OSC_CLKGAIN => 300
2025-07-14_14:26:54.658134Z ISC_LOCK [LOWNOISE_ASC.main] timer['LoopShapeRamp'] = 5
2025-07-14_14:26:54.658367Z ISC_LOCK [LOWNOISE_ASC.main] timer['pwr'] = 0.125
2025-07-14_14:26:54.783581Z ISC_LOCK [LOWNOISE_ASC.run] timer['pwr'] done
2025-07-14_14:26:59.658298Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:26:59.719537Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_GAIN => 200
2025-07-14_14:26:59.720456Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW1 => 256
2025-07-14_14:26:59.846249Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW2 => 20
2025-07-14_14:26:59.971686Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y => ON: FM3, FM8, FM9
2025-07-14_14:26:59.972384Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW1 => 5392
2025-07-14_14:27:00.098073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW2 => 4
2025-07-14_14:27:00.223528Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y => ON: FM1, FM3, FM4, FM5, FM8
2025-07-14_14:27:00.224135Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_P_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.224497Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_Y_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.224868Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.225188Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.225433Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:10.225728Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:10.281803Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_TRAMP => 5
2025-07-14_14:27:10.408120Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 16
2025-07-14_14:27:10.533563Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => OFF: FM9
2025-07-14_14:27:10.534285Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW1 => 256
2025-07-14_14:27:10.660088Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 4
2025-07-14_14:27:10.785453Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => ON: FM3, FM8
2025-07-14_14:27:10.786315Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_GAIN => 208
2025-07-14_14:27:10.786535Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5
2025-07-14_14:27:15.786858Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:15.847152Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_TRAMP => 5
2025-07-14_14:27:15.847580Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_GAIN => 5
2025-07-14_14:27:15.848666Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_GAIN => 5
2025-07-14_14:27:15.848917Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5
2025-07-14_14:27:20.849050Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:20.906577Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.907206Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.907700Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.908422Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.908830Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909148Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909562Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMY_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909789Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:30.910055Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:30.968166Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_P_GAIN => -0.2
2025-07-14_14:27:30.968527Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_Y_GAIN => -0.2
2025-07-14_14:27:30.968806Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_L_GAIN => -0.2
2025-07-14_14:27:30.969073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_R_GAIN => -0.2
2025-07-14_14:27:30.969343Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_T_GAIN => -0.2
2025-07-14_14:27:30.969606Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_V_GAIN => -0.2
2025-07-14_14:27:30.969838Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:40.970003Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:40.972085Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW1 => 1024
2025-07-14_14:27:41.097962Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW2 => 4
2025-07-14_14:27:41.223313Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P => ON: FM4, FM8
2025-07-14_14:27:41.223637Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:41.593743Z ISC_LOCK [LOWNOISE_ASC.run] Unstalling IMC_LOCK
2025-07-14_14:27:41.765955Z ISC_LOCK JUMP target: LOCKLOSS

I will take a look and see if there is anything unstable about these filters. Whatever is occurring seems to be too fast to be seen in the ASC signals themselves, and at first glance I don't see anything strange in the suspension channels either.

DHARD FM4 is engaged with a 10 second ramp- this is a change I made on 6/11: 84973 because we had lost lock on that day twice in the same spot. Two of the locklosses at 47 seconds occurred before that change. Then, later that day on 6/11 I reengaged a boost in DHARD P, which only has a 5 second ramp, 84980. Engaging that boost shouldn't be unstable, but maybe something bas occurrs when they ramp at different times. I'm lengthing the ramp to 10 seconds.

(Jordan V., Gerardo M.)

Today we replaced the MKS gauge at FC-C-1, this is the first 6 way cross inside the filter cavity tube enclosure, we installed serial number 390F00490, twice, yes two times.  It turns out that the flange has some scratches on the knife edge, and it was not going to seal regardless of the effort that we put into it.  Once the gauge was removed the scratches transferred to the copper gasket.  We replaced it with serial number 390F00495, this one seems to be doing good.  New conflat was leak tested and no leak was detectable above 2.42e-10 torr*l/sec.

The old gauge serial number is 390F00406 with a date code of June 2021.