TITLE: 11/27 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY: One lockloss overnight from an unknown cause, but H1 has been observing for just over 6 hours. Calibration/commissioning time today is slated for 16:30 to 20:00 UTC (08:30am to noon local).

• Extremely dense fog on-site with temps below freezing
• Wind low; secondary microseism still dropping and almost down to the 50th percentile

TITLE: 11/27 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: 1 lockloss this shift (IMC tagged LL), DRMI struggled at first but after an IA relocking was smooth. There were FSS oscillations during initial alignment. The range has been hovering just under 160Mpc.
LOG:                                                                                                                                                                                                                                           

• 01:34 UTC lockloss
  • 01:55 I adjusted ETMY_Y a few steps as guardian wasn't making any progress on it (it had been trying for 20 minutes and already went through increase flashes and the camera looked very yawed). It locked almost immediately after my adjustments.
  • DRMI was taking a while to lock despite good flashes (200 and 150), even after a round of PRMI it was still not locking. It was able to lock once but as soon as ASC turned on it lost it
  • Sometimes I would see light on the HAM6 OMC TRANS camera while DRMI was flashing, I can't remember if this is typical
  • 02:48 UTC I dropped to do an IA as DRMI didn't seem to be making much progress
  • 03:00 UTC After finishing INPUT_ALIGN the IMC lost lock as usual but the FSS started oscillating and didn't stop for over 10 minutes, after it stopped the FSS and IMC relocked. alog81509
    • The FSS_NPRO_TEMP channel and the PMC_HV_MON have the same triangle shape during the first oscillation
    • Jason says if you turn off the ISS it should help the FSS to lock faster (OPS info) if this happens again
  • 03:30 UTC DRMI locked after 1.5 minutes now.
  • 04:05 UTC Observing
• I tested out the original settings for ETMY mode 1 as the microseism has decreased. It damped mode 1 but also slowly rang up mode 6. The new settings damped it faster without a noticeable mode6 rise.
• I also tried the original settings for ITMY mode5/6 and it seems to damp fine, the line is shrinking on DTT, the modes drive is converging and both long monitors (ITMY modes 10 & 20) are also going down. It looks to damp at the same rate as the new settings.

I went down to start an IA at 02:48 UTC as DRMI wasn't locking (it tried for a half hour) and the FSS and IMC unlocked after input align and the FSS has been oscillating for the past 10 minutes or so. As I posted this log it finally locked.

01:34 UTC lockloss

IMC tag, the IMC and ASC lost it at the same time and there was a small FSS oscillation (-2 to +4) 8 ms before. The FSS NPRO TEMP stepped up 30ms before the LL, the ISS also lost lock.

LHO EndX measurement made today.

python3 generate_measurement_data.py --WS "PS4" --date "2024-09-23"
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2024-09-23 corrected to ES temperature 299.3 K :
-4.711436365635769 -0.0002694340454223 4.121866697713714e-05
Copying the scripts into tD directory...
Connected to nds.ligo-wa.caltech.edu
martel run
reading data at start_time:  1416675755
reading data at start_time:  1416676330
reading data at start_time:  1416676692
reading data at start_time:  1416677299
reading data at start_time:  1416677800
reading data at start_time:  1416678168
reading data at start_time:  1416678360
reading data at start_time:  1416679388
reading data at start_time:  1416679723
Ratios: -0.46161620922202573 -0.46631546727413287
writing nds2 data to files
finishing writing
Background Values:
bg1 =        9.175134; Background of TX when WS is at TX
bg2 =        5.161980; Background of WS when WS is at TX
bg3 =        9.165405; Background of TX when WS is at RX
bg4 =        5.151518; Background of WS when WS is at RX
bg5 =        9.191307; Background of TX
bg6 =        0.664785; Background of RX

The uncertainty reported below are Relative Standard Deviation in percent

Intermediate Ratios
RatioWS_TX_it      = -0.461616;
RatioWS_TX_ot      = -0.466315;
RatioWS_TX_ir      = -0.456051;
RatioWS_TX_or      = -0.461524;
RatioWS_TX_it_unc  = 0.086881;
RatioWS_TX_ot_unc  = 0.091151;
RatioWS_TX_ir_unc  = 0.097094;
RatioWS_TX_or_unc  = 0.089816;
Optical Efficiency
OE_Inner_beam                      = 0.988013;
OE_Outer_beam                      = 0.990086;
Weighted_Optical_Efficiency        = 0.989049;

OE_Inner_beam_unc                  = 0.060350;
OE_Outer_beam_unc                  = 0.060428;
Weighted_Optical_Efficiency_unc    = 0.085403;

Martel Voltage fit:
Gradient      = 1636.718975;
Intercept     = 0.130679;

 Power Imbalance = 0.989923;

Endstation Power sensors to WS ratios::
Ratio_WS_TX                        = -1.077666;
Ratio_WS_RX                        = -1.392000;

Ratio_WS_TX_unc                    = 0.054228;
Ratio_WS_RX_unc                    = 0.043548;

=============================================================
============= Values for Force Coefficients =================
=============================================================

Key Pcal Values :
GS           =      -5.135100; Gold Standard Value in (V/W)             
WS           =      -4.711436; Working Standard Value             

costheta     =      0.988362; Angle of incidence
c            =      299792458.000000; Speed of Light
             
End Station Values :
TXWS         =        -1.077666; Tx to WS Rel responsivity (V/V)
sigma_TXWS   =        0.000584; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS         =        -1.392000; Rx to WS Rel responsivity (V/V)
sigma_RXWS   =        0.000606; Uncertainity of Rx to WS Rel responsivity (V/V)

e            =        0.989049; Optical Efficiency
sigma_e      =        0.000845; Uncertainity in Optical Efficiency

Martel Voltage fit :
Martel_gradient         =        1636.718975; Martel to output channel (C/V)
Martel_intercept   =        0.130679; Intercept of fit of     Martel to output (C/V)

Power Loss Apportion :
beta          =        0.998895; Ratio between input and output (Beta)  
E_T          =        0.993960; TX Optical efficiency
sigma_E_T          =        0.000424; Uncertainity in TX Optical efficiency
E_R          =        0.995060; RX Optical Efficiency
sigma_E_R          =        0.000425; Uncertainity in RX Optical efficiency

Force Coefficients :
FC_TxPD          =        7.886467e-13; TxPD Force Coefficient
FC_RxPD          =        6.173183e-13; RxPD Force Coefficient
sigma_FC_TxPD          =        5.464959e-16; TxPD Force Coefficient
sigma_FC_RxPD          =        3.784130e-16; RxPD Force Coefficient
data written to ../../measurements/LHO_EndX/tD20241126/

Beam Spot
T1500062 procedure measurement and log
Martel
WS @ TX
WS @ RX
WS @ RX Both_BEAMS
LHO EndX PD report
Git Link: https://git.ligo.org/Calibration/pcal/-/tree/master/O4/ES/measurements/LHO_EndX/tD20241126?ref_type=heads

Lab measurements:
NOTES:
PS4 PS5 measurement used for the above measurement were made on 2024-09-23.
The Measurements done in the PCAL LAB today 2024-11-26 were significantly different from the last set of measurements. Due to a drop in the voltage reported in the following plots. 
https://git.ligo.org/Calibration/pcal/-/tree/master/O4/lab/measurements/t20241126_144208_PS4_PS5_FB?ref_type=heads
https://git.ligo.org/Calibration/pcal/-/tree/master/O4/lab/measurements/t20241126_160713_PS4_PS5_BF?ref_type=heads
And I will need review these further before re-running the ES data with these newest measurements.

This maybe due to some changes in the lab. More vetting time is needed.

TITLE: 11/27 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Busy but easy maintenance day followed by a fully automatic, albeit longer than usual, lock acquisition. H1 has been observing for almost 3 hours now.

• 15:40 - Taking ISC_LOCK to 'IDLE' and SEI_ENV to 'MAINTENANCE'
• 19:31 - Maintenance activities finished, starting initial alignment
• 19:51 - IA finished, starting lock acquisition
  • 20:35 - Lockloss immediately after entering LOWNOISE_ESD_ETMX (so really a TRANSITION_FROM_ETMX lockloss)
  • BS needed realigning to lock DRMI on next attempt, fully auto after
• 21:43 - Observing
  • Accepted SQZ ADF phase difference, attached (tagging SQZ)
  • Engaged Rahul's new violin damping settings from alog81465; these are working well

LOG:

TITLE: 11/27 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

• 2ndary microseism is still decreasing, wind is low
• We've been locked for 2.5 hours
• Violins look to be damping well
• The range has been slightly dcreasing, low frequency SQZing doesn't look the best on NUC33's DTT

Closes FAMIS28381

The in-lock charge measurements did not run this week due to the IFO losing lock from an Earthquake.

FAMIS 27803 (logging for TJ who actually did this check)

CO2X

• Before: 29.1
• After: 30.0
• Added 300mL

CO2Y

• Before: 9.2
• After: 9.8
• Added 250mL

There was no water in the leak cup. Spreadsheet in T2200289 has been updated.

Now that I have the function working pretty well for my liking (testing from last week - alog81420), I wanted to try it out in a few different scenarios and see how well it performed and how long it took. I also wanted to compare it to our current Increase_Flashes state both in duration and execution. The big changed from last week's testing is that now that we have a working PSL, the PLL and PDH loops are locked. This seemed to really help out and it seems like a very viable solution for a faster alignment state.

Overall, Scan_Alignment seems to work well and in these tests it was faster. I haven't put the functionality back into Scan_Alignment to hold and alignment if it get above threshold, so once I can test that out again it will speed up the smaller misalignment scans. Saving a few minutes for every acquisition that needs some alignment work should add up pretty quick. If given more time next week, I'd like to test this some more with that functionality and see how much faster it is. I'd love to get this into production soon, but I really want to thoroughly test this.

Last week Jenne had to comment out an import of aslArmconfig out of ALS_ARM.py in order for ALS_XARM to run (alog81424). This was a bit odd to me since this file contained info for both arms, and should be fine. I ended up restarting ALS_XARM and this worked. Seems like another case of issue 22. This particular issue is seem in the sei guardians frequently.

The 35.5MHz was switched from the Marconi (IFR2023) to the LHO 35.5MHz RF Source. Temporarily switched to the Marconi as part of troubleshooting of the PMC, see alog 81277. Both the PMC and SQZ were taken down prior to switching the RF signal.

Due to limited maintenance time between diagnosis and action, we triaged the fan failures with IFO uptime.  The following solution while not perfect is just good enough to get us to next Tuesday maintenance.

1 - Failed supply fan on CER-C5 LHS ISC-R2&R4 +24V is runnning at 90F front and rear, no airflow.  The ambient air in that location is very cool, and the current draw is quite low, so we do not expect this supply to trip in these conditions.  Fernando noticed that the -24V supply on the same rack is also slightly elevated in temperature and does not have good air flow, so we suspect this supply fan is comprimised as well.  Neither of these supplies have had their fans upgraded yet.

2 - Failed supply fan on EX-VDD-1 ISC-R1 +24V 3A was running at 110F front and rear, no airflow.  This supply has not had its fan upgraded yet.  The PCAL team was using this supply so we could not replace it before close of maintenance window.  We applied supplementary cooling to the power supply to see it through until next Tuesday.  After supplemental cooling we measured 85F front and 95F rear.

The power supply tray had to be pulled out about 1 foot into the walkway to make space for the supplemental cooling, I placed cones around the hazard, be mindful of the extended rack tray if you do go out to EX berfore next Tuesday.

WP12221

J. Figueroa, F. Mera, M. Pirello

Maintenance activities have finished, the LVEA has been swept, and initial alignment has just finished. Starting lock acquisition now.

Oli, Camilla WP12203. Repeat of some of the work done in 2019: EX: 52608, EY: 52636, older: part 1, part 2, part 3.

We misaligned ITMY and turned off the ALS-Y QPD servo with H1:ALS-Y_PZT_SWITCH and placed the Ophir Si scanning slit beam profiler to measure both the 532nm ALSY outgoing beam and the ALSY return beam in the HWS path.

The outgoing beam was a little oblong in the measurements but looked pretty clean and round by eye, the return beam did not! Photos of outgoing and return beam attached.  Outgoing beam was 30mW, return beam 0.75mW. 

Attached is the 13.5% and D4sigma measurements, I also have photos of the 50% measurements if needed. Distances are measured from the optic where HWS and ALS beams combine, ALS-M11 in D1400241. 

We had previously removed HWS-M1B and HWS-M1C and translated HWS-M1A from whats shown in D1400241-v8 to remove clipping. 

Until we figure out these laser glitches, I've increased all of the timers in H1_MANGER and IFO_NOTIFY by 50%. This will hopefully help avoid the late night notifications that resulted in no actual interventions.

I added a laser_fudge = 1.5 to both nodes, and then multipled the defined timers in H1_MANAGER lines 149-152  and IFO_NOTIFY lines 30-35.