Thu Apr 11 10:12:01 2024 INFO: Fill completed in 11min 57secs

Jordan confirmed a good fill curbside

BruCo scan from a good range time from last night: https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1396823046_GDS_CALIB_CLEAN/

Some highlights:

• there is coherence with PRCL between 15 and 40 Hz, and also with REFL_LF (RIN). This is similar to what we oberved before, and we managed to fix this by tuning the PRCL offset
• there is some coherence with CHARD_Y and INP1_Y at low frequency. This could be improved by trying the new HAM1 FF, since for both CHARD_Y and INP1_Y we expect some improvement using the new FF filters (note that we are not doing any HAM1 FF to Y now).
• there is little coherence with DHARD_Y at low frequency, so maybe the AS WFS offset is still ok

The last two plots show what improvement in sensitivity we should be able to get by reducing the above noise couplings, and which of the above noises contribute most at each frequency. Those plots are produced by offline subtraction with NonSENS

The MSR UPS went onto battery backup for 2 seconds at 07:35:02 due to an AC power glitch.

TITLE: 04/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY: 17 hour lock ended about an hour ago. H1 is currently running an alignment, but stuck at green locking with no light on Y arm. HEPI and both ISI statges at EY have tripped during locking, not sure of the cause yet.

TITLE: 04/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 167Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Very quiet shift (expect for the air handler) with H1 observing for all but 2 minutes.

• 00:07 - Dropped observing for 2 minutes to fix ETMX L2 cal line gains (alog77100)
• 00:20 - Control room air handler noise got much louder (alog77101)

H1 has now been locked for 10 hours.

LOG:

No log for this shift.

State of H1: Observing at 161Mpc

H1 has been locked for 6 hours, things are running smoothly.

Starting around 00:20 UTC (5:20pm PDT) this evening, the air has been much louder in the control room. Called Bubba to ask about it, and he says it's related to Eric's work today on the AHU-3 VAV (alog77092) and that the temporary ducting may have come undone. Other than it being louder in the control room, the duct should be fine and will be addressed in the morning.

I have not noticed a noticeable change in the IFO range since this noise increase, but I'll tag PEM and DetChar just in case.

TITLE: 04/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY: H1 has been locked and observing for 3 hours.

• Wind and microseism are low
• All systems nominal

TITLE: 04/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: One lockloss today with an easy relock. Some calibration work on the HVAC system that caused more fan noise in the OSB from 15:00-16:00UTCish. Rest of the day was quiet. We hit our current highest O4b range, 167.6Mpc!
LOG:

15:00ish-15:30ish Calibration of the CS HVAC system(77092) - fans much louder than normal - tagging Detchar

15:00UTC Detector relocking and at LOWNOISE_ASC
15:06 NOMINAL_LOW_NOISE
15:09 Observing

15:45ish HVAC calibration done but fans still slightly louder than normal while cooling the CS to correct temps - detchar
18:15-18:19UTC Richard and Eric going into LVEA to check for HVAC noise - detchar

19:46 Lockloss

20:41 NOMINAL_LOW_NOISE
20:56 Observing

There's been three locklosses today 04/10 and they all seem like they could've been caused by the same issue. For all three locklosses, it looks like the lockloss was seen by L2 of all four quads before it was seen by DARM or ETMX L3, which are usually the first that we see the locklosses hit. These three locklosses were seen in the order of: both ITMs at the same time, then ETMX, then ETMY, followed by DARM and ETMX L3. It's possible that the 19:46 LL had ETMX L2 see it at the same time as the ITMs, but the other two locklosses (07:21UTC and 13:11UTC) look to have hit the ITMs first.

I also looked the the last lockloss before 04/10 where there wasn't high wind or commissioning as a comparison and that lockloss had ETMX L3 and DARM seeing it first, like usual.

Lockloss 2024/04/10 07:21:20UTC - 77080
- ALL quad L2s saw the lockloss before DARM or EX L3 - Order: ITMs, EX, EY
Lockloss 2024/04/10 13:11:12UTC - 77082
- Same as above Order: ITMs, EX, EY
Lockloss 2024/04/10 19:46:48UTC - 77093
- Same as above - ITMs+EXmaybe, EY

Lockloss 04/10 19:46 UTC

late alog from work done yesterday:

I bumped up the ETMX L2 line to keep the uncertainty in the kappa PUM SUS line below a threshold of 0.01. Uncertainties above 0.01 clash with the hourly uncertainty services that run on the ldas clusters.

command and output:

gpstime;val=1.7 && caput H1:SUS-ETMX_L2_CAL_LINE_CLKGAIN $val && caput H1:SUS-ETMX_L2_CAL_LINE_SINGAIN $val && caput H1:SUS-ETMX_L2_CAL_LINE_COSGAIN $val && caput H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_CLKGAIN $val && caput H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_SINGAIN $val && caput H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_COSGAIN $val

PDT: 2024-04-09 15:42:06.558045 PDT
UTC: 2024-04-09 22:42:06.558045 UTC
GPS: 1396737744.558045
Old : H1:SUS-ETMX_L2_CAL_LINE_CLKGAIN 1.5
New : H1:SUS-ETMX_L2_CAL_LINE_CLKGAIN 1.7
Old : H1:SUS-ETMX_L2_CAL_LINE_SINGAIN 1.5
New : H1:SUS-ETMX_L2_CAL_LINE_SINGAIN 1.7
Old : H1:SUS-ETMX_L2_CAL_LINE_COSGAIN 1.5
New : H1:SUS-ETMX_L2_CAL_LINE_COSGAIN 1.7
Old : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_CLKGAIN 1.5
New : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_CLKGAIN 1.7
Old : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_SINGAIN 1.5
New : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_SINGAIN 1.7
Old : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_COSGAIN 1.5
New : H1:CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_COSGAIN 1.7

Many of the VAV terminals on the lab side of the OSB have been showing erroneous airflow readings and damper positions. I believe the cause of this is the VAV programming, which was written to drive the dampers closed during unoccupied hours, during which the damper actuators would calibrate their zero points to maintain correct readings of airflow and damper positions. Because these VAV units never go unoccupied since they are not on a schedule, the controllers have drifted over time and their zero points are no longer accurate. To correct this, I switched half of the VAV units to unoccupied mode, but the fans in AHU-3 did not respond quickly which led to an overpressure condition in the supply ducting which tore the flexible ducting at a VAV terminal in the control room. We had to shut down AHU-3 in order to get the duct reattached. This shutdown occurred ~8:30 local time and lasted about a half hour. Prior to the shutdown, their was a period of time ~10 minutes in which the airflow noise in the control room dramatically increased. 

The VAV reset was mildly effective; the cold deck static pressure was trending at .06" W.C. before the reset. After the reset it is trending closer to .09" W.C. The hot deck static pressure was trending at .09" W.C. prior to the reset, and at 1.4" W.C. after the reset. This shows that some of the terminal units have adjusted their flow rates, but there are still erroneous readings which will require further investigation.

HAM1 ASC FF was off from 1396381762 to 1396382969 (20 minutes starting 90 minutes into lock). Using this data I could retune the feed forward filters that subtract HAM1 motion from the ASC signals.

I based the attached jupyter code on an older version, and automated the subtraction training for all pitch and yaw ASC signals (CHARD, INP1, PRC2, DC1 and DC2).

Looking at the filters that are loaded now, we used to do the FF only for the pitch degrees of freedom. The subtraction seems to be doing something good in yaw too, so I suggest we upload and try the yaw feedforward filter.

The first plot shows the expected subtraction predicted by NonSENS. The second plot shows the absolute value of the transfer functions.

Finally, the attached text file contains the foton filter definitions for all the feedforward filter banks. I haven't upload those flter to foton, and not tried them yet. Before each filter there is the name of the filter bank where it should be loaded, for example H1:HPI-HAM1_TTL4C_FF_CART2ASCP_1_1

Eric, Naoki, Vicky, Jennie W, Sheila

We did SQZ OMC mode scan with cold OM2. The PSAMS is 175/100 (strain voltage 8.9/-0.69). The attached figure shows the result (ref 34). The SQZ OMC mode matching is 0.64/(0.64+2*0.03)~91.4%.

We followed the instruction in 74892. Here are some notes.

• We increased the seed power to 76mW and requested the OPO guardian to LOCKED_SEED_DITHER and FC guardian to MISALIGNED. The OPO_IR_PD_DC_POWERMON reached only 0.3mW while it was 0.89mW in 74892. We noticed that the seed was locked on the higher order mode. Vicky fixed the OPO guardian and the seed was locked on TEM00. The OPO_IR_PD_DC_POWERMON reached 1.26mW.
• We opened SQZ beam diverter and requested SUS_SR2 guardian to MISALIGNED (SUS_SRM guardian is ALIGNED). After we engaged DC3/4 centering loops, ASC-AS_{A/B}_DC_NSUM_OUT16 are ~75 and ASC-AS_C_DC_NSUM_OUT16 is 0.0009.
• We manually locked OMC. We turned on input and output switch, increased the gain to 1, turned on boost and integrator.
• For rough OMC alignment, we turned on OMC ASC by increasing the OMC ASC master gain "one click up" to 0.025. After that, we decreased the OMC ASC gain to 0 and manually aligned the OM3/OMC to maximize the OMC-DCPC_SUM_OUTPUT. After the manual alignment, OMC-DCPC_SUM_OUTPUT is 0.63.
• For OMC scan, we set the OMC-PZT2_OFFSET to -50 and ran the scan template in $(userapps)/sqz/h1/Templates/dtt/OMC_SCANS/April9_2024_PSAMS_OMC_scan_coldOM2.xml

PSAMS 175/100, cold OM2

• LOCKED: 1396722738 (2024-04-09 18:32:00 UTC) + 60 seconds 
• UNLOCKED: 1396722978 (2024-04-09 18:36:00 UTC) + 60 seconds
• Mode-scan (ref 34): 1396723292 (2024-04-09 18:41:14 UTC) + 200 seconds

DARK

• DARK: 1396723968 (2024-04-09 18:52:30 UTC) + 60 seconds