TITLE: 12/07 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 14:14 UTC (11 hr lock).

Of note:

• SQZ dropped us out of OBSERVING and relocked automatically
• During the drop, we took the time to reinstate some of the cleared SDFs that Tony accepted, and then accepted those. All-in-all, I reloaded ALS_XARM, ALS_YARM and ISC_LOCK guardians. We also made the changes in the SDF screenshotted below.
• Hanford authorities informed Tyler (who informed me) that they will be conducting their military loud exercises. Robert confirmed that these would not hurt our observing data.

LOG:                                                                                                                                                                                                                                   

TITLE: 12/07 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

We're Observing and have been Locked for 11 hours. Winds are low and secondary microseism is not too bad.

Closes FAMIS#26345, last checked 81548

Corner Station Fans (attachment1)
- All fans are looking normal and within range.

Outbuilding Fans (attachment2)
- MY FAN1 accelerometer 1 has become a little more chaotic looking the past three days, but is still well within range. All other fans are looking normal and are within range.

The way that I used to run bruco didn't work for me today.  With help from Elenna and Camilla I was able to run it, so here is what I did:

ssh into ssh.ligo.org, select 4 for LHO cluster and c for ldas.pcdev1

made a fresh clone of https://git.ligo.org/gabriele-vajente/bruco in a directory called new_bruco

cd /home/sheila.dwyer/new_bruco/bruco

python -m bruco --ifo=H1 --channel=GDS-CALIB_STRAIN_CLEAN --gpsb=1417500178 --length=400 --outfs=4096 --fres=0.1 --dir=/home/sheila.dwyer/public_html/brucos/GDS_1417500178 --top=100 --webtop=20 --plot=html --nproc=20 --xlim=7:2000 --excluded=share/lho_excluded_channels_O4.txt

The bruco now appears at: https://ldas-jobs.ligo-wa.caltech.edu/~sheila.dwyer/brucos/GDS_1417500178/

This is for a quiet time overnight last night.

Input jitter does have a contribution, as Robert suspected based on looking at the DARM spectrum.  Jenne looked at cleaning, and plans to try out a new cleaning during Monday's commissoning window.

Note to Operators: During the CP1 fill (which starts daily at 10am) the CDS ALARM system shows RED because the LN2 Liquid Level Control Valve (LLCV) is ramped up to 100% open. The alarm system puts this channel into alarm when its value exceeds 50%. This alarm should clear within 1 minute of the end of the fill.

Fri Dec 06 10:07:29 2024 INFO: Fill completed in 7min 25secs

Gerardo confirmed a good fill curbside.

TITLE: 12/06 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 14:14 UTC.

Looks like we got to NLN at 13:30 UTC but IFO couldn't go to OBSERVING, which caused guardian to call OWLOperator (Tony) - alog 81643

TITLE: 12/06 Owl Shift: 0600-1530 UTC (2200-0730 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
LOG:
H1 called me to help with SDF issues.
SUS ETMX and ITMX SDFs

These seemed like they were changed randomly in the night but also seemed like that may have unlocked the IFO if reverted so I accepted them.
But now that i'm looking back at Francisco's Alog I think some may have been intentional.
 

More than 1 IFO H1 call tonight:
H1 Called me earlier in the night and I slept though the calls because I did not realise my phone was not properly set up for this owl shift before I went to sleep.
 

TITLE: 12/06 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Quiet shift with H1 observing throughout; current lock stretch is at 7 hours.

TITLE: 12/06 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: The day started with Calibration and commissioning, with a commissioning lock loss. Recovery was striaght forward, then a large 7.0 earthquake off the coast of CA took us down for 4 hours. Recovery here was also straight forward. Observing for 1.5 hours.
LOG:

• 1619 Out of Observing for Calibration
• 1701 Lock loss
• 1833 Back to low noise, more commissioning
• 1846 Lock loss from earthquake
• 2308 Observing

TITLE: 12/05 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 1mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY: H1 recovered easily after the earlier EQ and has been observing for just over an hour.

Recovered after the 7.0 earthquake off of the coast of CA. Recovery was basically automatic, the only thing I did was untrip ISIs and SUS watch dogs when I could, and tell guardian when to start initial alignment.

Initially we went into Observing but Francisco realized that his his from earlier today (alog81630) didn't make it in. We updated lscparams.py with the new value and the Observe.snap. The safe.snap was saved at a value of 1.0, so we must be relying on ISC_LOCK to make the change.

One other SDF was found from the pico H delay. This was unmonitored.

Camilla, Sheila, help from CDS team

We've been having some locklosses during the ESD transitions, some of them seem to be related to a large glitch that happens at the end of the 10 second output ramp time when DARM1 FM1 (a boost) is turned off in preparation to switch back to ETMX control where the boosts are in the pum rather than the DARM bank. 

Erik and Jonathan told us that since the filter ramp is linear, it's not suprising that there is a discontinuity when the ramp time ends.  They have opened a ticket after a discussion about ways to avoid this: 667

We could make this better by increasing the ramp time, but we want to keep this state short because of a slow instability we can get if we wait here: 81430. 

For now we've removed the boost which was being turned on in the state DARM offset before the ASC gets engaged, during the power up. The attachments compare the ESD drives with and without this filter being ramped off, the glitch is gone.

At Sheila's suggestion, I've turned the IMC gain redistribution back on in LASER_NOISE_SUPPRESSION, ISC_LOCK state number 575. Just a reminder, this is the code (lines 5793-5806 now):

       if self.counter ==5 and self.timer['wait']:
            if self.gain_increase_counter <7:  #icrease the imc fast gain by this many dB
                #redistribute gain in IMC servo so that we don't saturate splitmon in earth quakes, JW DS SED
                #setting this to not change the gain sliders October 9, because Camilla saw that the IMC locklosses that we think are due to laser glitches started happening on the day we did this gain redistribution. alog 80561
                ezca['IMC-REFL_SERVO_IN1GAIN'] -= 1
                ezca['IMC-REFL_SERVO_IN2GAIN'] -= 1
                ezca['IMC-REFL_SERVO_FASTGAIN'] += 1
                time.sleep(0.1)
                self.gain_increase_counter +=1
            else:
                self.counter +=1
        
        if self.counter >= 6 and self.timer['wait']:
            return True

This can be turned off by setting changing gain_increase_counter <0, on line 5794. If we are losing lock during this state we should turn it off again, or reduce the gain_increase_counter to <5 or something.

FranciscoL, SheilaD

Changed H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN by 3.63 % using KappaToDrivealign.py at gps 1417450784.

Script output:

Average H1:CAL-CS_TDEP_KAPPA_TST_OUTPUT is -3.6267% from 1.
Accept changes of    
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN from 191.711517 to 198.664299
Proceed? [yes/no]
yes
Changing
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN => 198.6643

First figure (kappa2drivealign_ndscope) is an ndscope of the relevant channels. The the second plot (top to bottom) is CAL-CS_TDEP_KAPPA_TST_OUT with a verticar marker aligned at a time where the uncertainty from CAL-CS_TDEP_PCAL_LINE3_UNCERTAINTY (third plot)  increased. This increase in uncertainty is expected from turning off lines before calibration measurement.

KAPPA_TST_OUT is around 1 from minute 5 to the marker, which is the objective of changing the drive gain.

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.