We lost lock from the calibration, so we tried to lock ALS without the linearization (some background in this alog: 83278.)  An active measurement of the transfer function from DRIVEALIGN_L to MASTER out was 1 without the linearization, and -0.757 with the linearization on.  So I've changed the DRIVEALIGN gain to -1.3 in the ALS_DIFF guardian when the use_ESD_linearization is set to false.  

We tried this once, and it stayed locked for a DARM gain of 400, but unlocked as the UIM boosts were turning on. We tried this again but it also didn't lock DIFF, so it is now out of the guardian again.

I looked at a few more of the past ALS DIFF locks, both sucsesful and unsucsesful attempts we are saturating the ESD (either the DAC or the limiter in the linearization) in the first steps of locking DIFF.  We do these steps quite slowly, stepping the darm gain to 40 waiting for the DARM1 ramp time, stepping it to 400, then waiting twice the ramp time, then engaging the boosts for offloading to L1.  I reduced the ramp time from 5 seconds to 2 seconds to make this go faster.  This worked on the first locking attempt, but that could be a coincidence. 

We will leave this in for a while, so that we can compare how frequently we loose lock at LOCKING_ALS.  In the last 7 days we've had 48 LOCKING_ALS locklosses, and 19 locklosses from NLN, so roughly 2.5 ALS locklosses per lock stretch. 

The calibration measurement caused another lock loss at the end of the measurement (alog83351)

Simulines start:

PDT: 2025-03-13 08:36:53.447733 PDT
UTC: 2025-03-13 15:36:53.447733 UTC
GPS: 1425915431.447733
 

End of script output:

2025-03-13 15:58:59,923 | INFO | Drive, on L2_SUSETMX_iEXC2DARMTF, at frequency: 42.45, and amplitude 0.41412, is fin
ished. GPS start and end time stamps: 1425916738, 1425916753
2025-03-13 15:58:59,923 | INFO | Scanning frequency 43.6 in Scan : L2_SUSETMX_iEXC2DARMTF on PID: 795290
2025-03-13 15:58:59,923 | INFO | Drive, on L2_SUSETMX_iEXC2DARMTF, at frequency: 43.6, is now running for 23 seconds.
2025-03-13 15:59:01,039 | INFO | Drive, on DARM_OLGTF, at frequency: 1083.3, and amplitude 1e-09, is finished. GPS st
art and end time stamps: 1425916738, 1425916753
2025-03-13 15:59:01,039 | INFO | Scanning frequency 1200.0 in Scan : DARM_OLGTF on PID: 795280
2025-03-13 15:59:01,039 | INFO | Drive, on DARM_OLGTF, at frequency: 1200.0, is now running for 23 seconds.
2025-03-13 15:59:02,168 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 11.13, and amplitude 13.856, is fini
shed. GPS start and end time stamps: 1425916735, 1425916753
2025-03-13 15:59:02,168 | INFO | Scanning frequency 12.33 in Scan : L1_SUSETMX_iEXC2DARMTF on PID: 795287
2025-03-13 15:59:02,169 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 12.33, is now running for 25 seconds
.
2025-03-13 15:59:07,162 | ERROR | IFO not in Low Noise state, Sending Interrupts to excitations and main thread.
2025-03-13 15:59:07,163 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L2_CAL_EXC
2025-03-13 15:59:07,163 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L3_CAL_EXC
2025-03-13 15:59:07,163 | ERROR | Ramping Down Excitation on channel H1:CAL-PCALY_SWEPT_SINE_EXC
2025-03-13 15:59:07,163 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L1_CAL_EXC
2025-03-13 15:59:07,163 | ERROR | Aborting main thread and Data recording, if any. Cleaning up temporary file structu
re.
2025-03-13 15:59:07,163 | ERROR | Ramping Down Excitation on channel H1:LSC-DARM1_EXC
ICE default IO error handler doing an exit(), pid = 795246, errno = 32
PDT: 2025-03-13 08:59:11.496308 PDT
UTC: 2025-03-13 15:59:11.496308 UTC
GPS: 1425916769.496308
 

Closes FAMIS 26034, last checked in alog83240

The script reports high freq noise is elevated for these BSCs.

• ITMX_ST1_CPSINF_V1
  • It doesn't look higher than it did last week.
• ETMY_ST2_CPSINF_V2
  • ST1_H1, ST2_{V1,V3} also look elevated at high frequency.

All the HAMs noise looks to have reduced except for HAM8, particularly a peak at just over 1 Hz in H3 and H1 looks reduced on almost all of the HAMs. HAM8s mid freq looks overall noisier and the high freq V3 peak looks elevated (just over 100Hz).

1425916765

This happened at the end of the calibration measurement. This also happened last week (alog83210).

Overhaul of the failed roofing at the LSB finished on Tuesday.


T. Guidry

We had a vacuum glitch in the LVEA at 01:57 Thu 13mar2025 PDT which was coincident with a lockloss. The glitch was below VACSTAT's alarm levels by an order of magnitude, so no VACSTAT alert was issued.

The glitch is seen in most LVEA gauges, and took about 10 minutes to pump down.

Attached plots show a sample of LVEA gauges, the VACSTAT channels for LY, and the ISC_LOCK lockloss.

TITLE: 03/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 134Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 24mph Gusts, 18mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY: Locked for 1.5 hours. Planned calibration and commissioning today. Elevated winds already present, some gusts above 40mph. The PSL 101 dust monitor has been in alarm.

As a potential optic for the new TT for the in-vac POPX WFS in HAM1, we tested the transmission of what is supposed to be the old ZM2 mirror from O3 days as a function of AOI.

The results summarized below doesn't make sense because it's least transmissive at 0 deg AOI and it's not HR at 45 deg (3.3% transmission). It's supposed to be E1700103 according to the label but with a handwritten note saying "verify??? doesnt look the same" or something like that. Anyway, if it is indeed E1700103, it should be R>99.99% @ 1064nm for both P and S at 45 +- 5 deg AOI.

This mirror is probably usable for POPX in that the transmission is not disastrously big at the proposed AOI (~30deg or so?) but this is a mystery optic as far as I'm concerned. If the mirror in ZM1 is better, we'll use it.

Other things to note:

We mounted the mirror in a class A siskiyou mirror holder on a dirty rotational stage with a clean sheet of foil inbetween so we can easily change the AOI in YAW.

The apparatus was NPRO - BS (to throw away some power) - HWP - PBS cube transmission (to select P-pol) - steering - ZM2 optic transmission - power meter.

The beam height between the steering mirror and the ZM2 optic was leveled, then ZM2 was adjusted so the beam retroreflects within +-2mm over 19 inches, and this became our AOI=0 reference point with uncertainty of ~+-2mm/19inches/2 rad ~ +-0.1deg. We used the indicator on the rotational stage to determine the AOI, and overall AOI error should have been smaller than 1 deg.

Before/after the measurement, the power impinging the HR side of the mirror was 180.3mW/176.1mW. Since the transmitted power only had 2-digits precision at best, I used 1.8e2 mW as the input power. The ambient light level was less than 10uW and is ignored here.

Another obvious candidate is ZM1 (again from O3 days). The mirror was not removed from TT after deinstallation though. We'll see if we can roughly determine the AOI while the mirror is still suspended, as it's a hassle to remove it from the suspension and there's a risk of chipping.

TITLE: 03/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Observing at 147Mpc and have been Locked for almost 16 hours. Nothing happened during my shift. This also means I didn't get to do any of the tests with the cameras or A2L changes.
LOG:

Observing my entire shift                                                                                                                                                                                                                                                                                           

Observing at 144Mpc and have been Locked for 14 hours. Our range has been moving around quite a bit unfortunately.

Closes FAMIS#28396, last checked (injections last made) 82537

The ITMX data initially wasn't analyzed due to some issue with grabbing the data yesterday, but I got it to work today by just having it redownload the data and this time there were no issues with it.

I'll be editing the process_single_charge_meas.py script to make sure that if there is an error with downloaded data, the script tries to redownload the data instead of reading in previously downloaded corrupted/incomplete data, failing, and just giving up on that measurement.

We noticed that the range was dropping even lower than our already low ~145Mpc. There was a lot of low frequency noise that was creeping up. Sheila suggested that we look at the PIs and sure enough, PI31 had started to slowly creep up the same time as the range degredation (see attached). The SUS_PI guardian node will turn on the damping at 3 according to the H1:SUS-PI_PROC_COMPUTE_MODE31_RMSMON channel and turn it back off when it gets below 3. For now we just tried changing that threshold to 0 to all for continuous damping. This let the mode damp down completely and it brought our range back up.

We should think more about damping this down lower and having two thresholds, an on an off.

WP9880

I removed the O3 ZM2 tip tilt from HAM5 and moved the SRM heater optics to be used in the upcoming temporary laser setup for OFI alignment.

Summary of activities:

• Dust counts were 0's or low 10's before and after opening soft covers, using grey handheld
• Collected 4" and 1" CC samples with Nidhi's help
• Removed cables, BOSEMs, and optic from ZM2
• Corey and I bagged the TT, BOSEMs, TT spacer, beam dump spacer, dog clamps
• I left 3 beam dumps and the SRM heater mirrors on the South side of the table to be, potentially, used for the upcoming temp. laser setup.