Jennie W, Sheila

We want to do an OMC scan after unlocked today so we can estimate the mode-matching into the OMC with a hot OM2.

Set SRM, ITMX and ETMs to mis-aligned, IMC locked in guardian.

Ran DC centering loops 3 and 4 to centre on AS_A and AS_B QPDs, then ran OMC ASC to align into OMC_A and OMC_B QPDs. Waited for this to converge spots in centre of QPDs with current nominal QPD offsets.

Made sure that OMC guardian was paused then moved PZT2 slider to bottom of its range on ther OMC_Control screen and ran scan with template:

Did scan but sidebands are still on so can't do visibility measurement easily.

Ref 12-14 are today's scan measurements saved in /ligo/home/jennifer.wright/Documents/OMC_scan/2024_06_27_OMC_scan.xml.

Analysis ongoing.

06/27 16:03 Lockloss after calibration sweep was done and right as commissioning was started. Unknown cause

Calibration was run between 06/27 15:33 and 16:01 UTC

Calibration monitor screenshot

Broadband (2024/06/27 15:33 - 15:39 UTC)

File: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20240627T153409Z.xml

Simulines (2024/06/27 15:39 - 16:01 UTC)

Files:

/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20240627T153950Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20240627T153950Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS/SUSETMX_L1_SS_20240627T153950Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20240627T153950Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20240627T153950Z.hdf5

15:32 UTC I took us out of Observing to run a calibration sweep and then we will be doing some commissioning.

TITLE: 06/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

Observing at 155Mpc and have been Locked for almost 5 hours. We have commissioning today starting at 15:30UTC

TITLE: 06/27 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Another Lockloss
This Lockloss has some really interesting motion on the ETMS and ITMS  for atleast about 2 minutes before the lockloss.
My heade was burried in my laptop at the time, but I don't know what I would have done had I looked up and seen DARM acting that strange.
And once again SUS-ETMY PI ESD Driver had sustained elevated activity up above 2000 - 3000. there were no verbal alarms about elevated PI's 

I readjusted the H1:SQZ-SHG_FIBR_REJECTED_DC_POWER back down again.
Sitemap -> SQZ overview -> SQZT0 -> click half wave plate. seen here:
then opened the controller screen via the button.
then clicked on the correct Pico motor,  then enabled it.
This allowed me to move the pico motors in the Up down and left right directions which move 2 differerent wave plates while watching the NDSCOPE to minimize the signal.
be sure to move the pico motor slowly, and dont request a move while it's yellow. I was told to click it & let it finish.
 

TITLE: 06/27 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:
Lockloss 4:42 UTC
I checked for a spike in the wind at the time and didn't see anything abnormal, low seismic activity at the time too. There was some PI ESD DRIVER motion that seemed mildly elevated, but earlier during that lock it had been higher.

Relocking was simple after an Initial_Alignment.
Observing reached by 6:13 UTC

TITLE: 06/26 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently relocking and at ENGAGE_SOFT_LOOPS. Two locklosses during my shift, and we had a good amount of trouble messing with ALSX during relocking this second time.

After thislast lockloss, I went to Initial alignment, and while trying to lock green arms I had the same issues with the beatnote frequency and so Sheila and I went to adjust the fiber polarization to get it back to the values that it seems are ideal for ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT and ALS-X_FIBR_LOCK_FIBER_TRANSRIGHTPOL, the closer we got to the correct values for those two channels, the worse the beatnote would get. It seems like the ideal max splot for the ALSX beatnote is 8.8dB and we started with it around -20dB, but as we adjusted the fiber polarization, the beatnote went down to -30dB. Trying to then adjust the fiber polarization to maximize the beat note sent the two fiber polarizatoin channels the complete opposite direction that we wanted, so we went back and based our movements on those two channels to slightly improve those values, and changed the minimum beatnote value to be -20dB (tagging ops, needs to be accepted in sdf) instead of -10dB as a temporary fix for now to make sure that we don't get stuck in fault again like last night.

LOG:

14:30 Detector unlocked and at FIND_IR
    - Initial alignment had been done by H1 Manager, but it had become stuck at the end at 10:46UTC and hadn't tried relocking again until 13:54UTC, and by that time it seems like the alignment had drifted because it couldn't lock
14:37 We started going through CHECK_MICH_FRINGES so I took us to DOWN and ran another initial alignment
14:52 Initial alignment done, relocking
15:41 NOMINAL_LOW_NOISE
15:47 Observing

16:04  Lockloss
16:29 Initial alignment complete, relocking
17:11 NOMINAL_LOW_NOISE
17:14 Observing

22:04 Lockloss
- Went to Initial alignment, had the same issues with the beatnote frequency and so Sheila and I went to adjust the fiber polarization to get it back to the values that it seems are ideal for ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT and ALS-X_FIBR_LOCK_FIBER_TRANSRIGHTPOL, the closer we got to the correct values for those two channels, the worse the beatnote would get. It seems like the ideal max spot for the beatnote is 8.8dB and we started with it around -20dB, but as we adjusted the fiber polarization, the beatnote went down to -30dB. Trying to then adjust the fiber polarization to maximize the beat note sent the two fiber polarizatoin channels the complete opposite direction that we wanted, so we went back and based our movements on those two channels to slightly improve those values, and changed the minimum beatnote value to be -20dB instead of -10dB as a temporary fix for now to make sure that we don't get stuck in fault again like last night.

TITLE: 06/26 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 16mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Current SQZ issue is Pump Fiber rej port in HAM7 High, nominal 35E-3, align fiber pol in sqzt0
H1:SQZ-SHG_FIBR_REJECTED_DC_POWER  = 0.312
I understand I should move the Pico motors before Inject Squeezing.
 

In the seiproc model we have some code that produces IFO basis ground motion channels i.e.: XARM_GND=ETMX_X_GND - ITMX_X_GND. There's X/Y arm and CARM and DARM channels.  They've in for years, but I'm not sure that much has been done with them. While talking to Neil about some earthquake stuff, I realized we don't have blrms calculated for these IFO dof ground channels, something that might be really useful for earthquake or microseism studies.So, I've filed ECR E2400233, channels went in at LHO yesterday. I'll let Huyen know, but the seiproc model parts aren't common between the sites.

Built a second SHG with the PPKTP crystal from MIT, did a measurement on the conversion efficiency and fit for the single pass nonlinear conversion efficiency E_nl = 0.0055W^-1. The single pass measurement of the PPKTP crystal give a nonlinearity d_eff = 5.41 pm/V. Generally d_eff of PPKTP is quoted around 9.3pm/V (Table 5.1 of Georgia's thesis)

Measurement of the phase matching curve with input power of 60 mW shows a dip around 35 celcius. The temperature controller reads in kOhm and is converted into celcius via the Steinhart-Hart equation:

A1 = 0.003354016
B1 = 0.0002569850
C1 = 2.620131e-6
D1 = 6.383091e-8

R25 = 10000
R = R_meas / R25
T = ( 1 / (A1 + (B1 * np.log(R)) + (C1 * np.log(R)**2) + (D1 * np.log(R)**3) ) ) - 273.15

Phase matching curve is plotted by using Equation 3.14, 3.20 and Table 3.2 from Sheila's thesis. I have fitted the sinc curve with T₀ = 34.9 and i_max = 11.79 , 18.00 and 32.00.

Lockloss @ 06/26 22:04UTC - most likely from wind

Last night the ALS_XARM node was stuck in a loop of tryin to go to increase flashes but Beckhoff was reporting some errors (PDH, PLL, others) so the node would jump to fault state (see Oli and Ryan C's alog78669). There were two issues I found: the unstall decorator that re-requested the node to jump out of FAULT only looks for Beckhoff error messages which might be temporarily not present, and the FAULT state has a jump transition in it to allow us to go to UNLOCKED. I have three possible solutions for this:

1. Line 208 of ALS_ARM.py forces a jump transition to UNLOCKED while in the FAULT state if the target state is unlocked. Based off of a comment in the code there, I believe the intent was to allow us to still go to unlocked if ALS is shuttered. This isn't desireable because I can't really see another state that would be the target, so it will always jump out of this FAULT state. Changing this line from looking at the target state to the request state should allow it to stay in fault unless we want it to go to unlocked.
2. Make the unstall node decorator smarter looking at more than just if there are any node notifications. In this case the notifications would only come from Beckhoff error messages, so this isn't good enough at times since the messages can flash by or temporarily go away.
3. Create a state just before Increase_Flashes that does a check of the ALS Beckhoff errors and will wait here until they are cleared. I worry that this will not be a clear enough indicator that we are in an error state though. It also could create a way to get stuck here and force more user intervention.

For now we'll try option #1 and see how that works. If we need to make it more sophisitcated we can test it out. The code with this change has been saved and will be reloaded when we drop out of Observing.

We are Observing at 154Mpc and have been Locked for 2.5 hours. Nothing to report.

RCG5.3.0 reads out the FPGA chip temperatures for both the Timing Card and the new LIGO 28AO32 DAC card. These are available as EPICS channels and can be trended in ndscope.

The attached image shows the past 24 hour trend, and where you can find these temperatures on the RCG MEDMs.

Closes FAMIS#27792, last checked 78496

TCSX: Originally at 29.6. Added 300mL to get to 30.1

TCSY: Already at 10.4. Nothing added.

No leak in water cup