1. Lockloss at 8:10 UTC due to DRMI unlocked - locking now
2. Lock 1:
   • Had to go to increase flashes (both)
     1. Had to touch X significantly 
   • Took a while to get Find_IR
   • DRMI unlocked
     1. Need to go through PRMI
     2. Put SQZ_MANAGER in DOWN as per Vicky's request
     3. Touched BS when PRMI locked to overlay the beams 
        • As with yesterday (5/30), had to go through PRMI at which point I assisted guardian (after letting it try and fail for a small time) through touching PRM to get PRMI to locked. While attempting to acquire DRMI (1F), I touched the BS while looking at the AS AIR camera in order to align the "peanut" beams on top of one another.
     4. Got NLN at 9:33 UTC but got stuck at ENGAGE_PUMP_ISS while trying to get LOCKED_CLF_DUAL in order to achieve FREQ_DEP_SQZ. Fixed itself somehow after 27 minutes of stalling.
3. IFO STATUS: In NLN and OBSERVING as of 9:59 UTC.
4. Other: NUC 30 DARM FOM working but near-constantly glitching.

TITLE: 05/31 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing
SHIFT SUMMARY:
LOG:

Lock#1:

Lock #2:

TITLE: 05/31 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING (and has been for 2 hours)

Closes FAMIS 19660, last done in 69690.

BSC CPS:

EX ST1 noise much lower than last week.

HAM CPS:

All look nominal. Seem to have lower low freq noise and sharper 12Hz peaks comapred to lask week.

Closes FAMIS 17559, last done 69145.

Trends attached, both look normal. 

After 2h44m in NLN with some violin damping changes (70020), we lost lock at 01:07UTC. Cause unknown, DCPD saturation at time of lockloss.

Went though an initial alignment, still had trouble at DMRI/PRMI locking but think I've jut tracked it down to sam SRC issue TJ/Sheila found earlier 70013, see attached to compare this afternoons successful and recent attempt.

H1dmtlogin is showing some disk errors.  It is older hardware, and will be replaced.

Today Erik and I racked a new server up.  I updated a puppet config for h1dmtlogin.  It will be replaced tomorrow morning when we are allowed by the control room.

Since we've changed the ETM ring heaters, the Jitter cleaning needed to be retrained.  Also, since jitter is the only one that's doing any cleaning right now, all the others also need to be retrained.

I used a time from over the weekend when the IFO had been online for ~9 hours, so plenty thermalized.  With some suggestions from Gabriele, I retrained the Jitter subtraction and the Laser noise (high frequency) subtraction.  I hope to try these out during the next time we have a short commissioning window (perhaps tomorrow afternoon, in coordination with LLO).

Attached are the offline results for Jitter and Laser noise. 

Note to self, the Jitter noise is even better with the N_SOS=16 that Gabriele suggests, but implenting that would require a restart of the h1oaf model, so this is with N_SOS=8.

The offline subtraction of noises that come from the h1bos model is not quite working right now.  This means that I cannot subtract the main LSC noises, MICH and SRCL, until that's figured out.  I can (and should) train PRCL, since that one is on the h1oaf model, and not modulated.  This may also be motivation to first do a linear subtraction of MICH and SRCL (in addition to PRCL), and let the bilinear h1bos model do less work.

As Ryan C notes in alog 70003, "IX12 & IY8 damping have changed phase, a negative gain damped IX12 down (-2, max of -4) instead of the +2 its set to in lscparams. IY8 also was rising, I changed its gain sign from 0.08 to -0.08 and it started to fall".

Both these modes have been falling well since but our troublesome ITMY Mode5/6 pair have been slowly rising. See attached. I first suspected the IY8 phase change could be causing this to turned the IY8 damping off for 20 minutes. IY8 stopped damping but IY5/6 continued to rise. I've now turned off the mode5 damping, will see what effect this has as I'm worried about adjusting it's phase.

Y2-8
Solar panels are mostly clear and in good condition, all cables are good.
Each battery was checked with a multimeter:
Top battery 13.21 VDC
Bottom battery 12.93 VDC
The LCD readout at the charge controller showed for both batteries 26.10 VDC, measured with clear skies.

X2-8
Solar panels are mostly clear and in good condition, all cables are good.
Each battery was checked with a multimeter:
Right battery 14.66 VDC
Left battery 14.82 VDC
The LCD readout at the charge controller showed for both batteries 29.60 VDC, measured with clear skies.

FAMIS task 22072

TITLE: 05/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 124Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY: Locked and in Observing for 45minutes. 

Ryan/TJ notes that if we loose lock it's expected we'll need to do an initial alignment (but watch SRY locking 70013), due to continuing temperature changes. Ryan has had to touch PRM, BS during PRMI locking alog70003.

TITLE: 05/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 124Mpc
SHIFT SUMMARY:

• EY Vacuum pressure red alarm in the morning for PT-424 & PT-410, I told Travis about it, the alarms continued into the afternooon
• VAC PREP lab red 0.3 dust alarm at 17:10UTC, PSL 102 (Anteroom) red 0.5 dust alarm at 17:25TUTC & 17:35UTC. The CS wind is starting to pick up over the past hour, could be the cause?
• Ground motion is higher at both arms plus 20mph wind gusts while relocking
• DARM on NUC30 is back up and running

Lock#1:

Started off with an initial alignment after seeing some drifting on the OPLEVS, & OSEMS (esp. SR3 pitch, which seem to drift a large amount for only 4 hours). There doesn't appear to be a clear temperature correlation?

Both arms went through increase flashes, Yarm went smoothly and locked at a high 90%, Xarm struggled a bit and took more than twice as long, I tapped ETMX in pitch 0.3 microrads and it was enough for it to catch after it finished increase flashes and was still struggling on ENABLE_WFS. Good beatnotes, -4.5 (X) & -6 (Y).

SRM was badly aligned, after lots of SRM saturations and the ASC-AS_A signal was low (~2 instead of 4/5) I paused INIT_ALIGN and brought ALIGN_IFO to offload SR2 then I went to PREP_FOR_SRY and adjusted SRM mostly in pitch to make AS_AIR more symmetrical and to get higher highs, and lower lows on the H1:ASC-AS_A_DC_NSUM_OUT16 trace. I then unpaused INIT_ALIGN and rerequested SRC_ALIGN which went smoothly the 2nd try.

Lost it at FIND_IR, Yarm looked a little glitchy then it lost it

Lock#2:

Lost it at FIND_IR again, it seems like Yarm is killing it?

Lock#3:

Lost it at LOCKING_ALS, Yarm again I think

Lock#4:

COMM IR was found pretty easily, DIFF took a while, went through PRMI got it, took a little while for it to get DRMI despite good looking flashes.

Lockloss at MOVE_SPOTS 20:57, DCPD saturation right beforehand

Lock#5:

Couldn't get DRMI went through PRMI again, I had to tap PRM in pitch to catch, then in DRMI_1F I adjusted the BS in pitch

Had to stop at OMC_WHITENING for the violins to damp, IX12 & IY8 have changed phase, a negative gain damped IX12 down (-2, max of -4) instead of the +2 its set to in lscparams. IY8 also was rising, I changed its gain sign from 0.08 to -0.08 and it started to fall - Tagging SUS

Aquired NLN at 22:25UTC, we had to wait for ADS to converge for the CAMERA_SERVO as usual and some SEI SDF diffs to be checked

In Observing at 22:39UTC

DARM was glitching out a bit around 22:55 on the FOM

LOG:                                                                                                                           

I'm not fully sure that it's meaningful, and I've let Betsy and TJ know since they're doing a deeper dive into our temperatures and suspensions, but it seems that today (~5 hours ago, while we were unlocked) we had more motion around the microseism for several of our optics, including all 4 quads for some of their top mass degrees of freedom.  However, the BLRMS of our microseism don't seem to have increased by the ~order of magnitude that some of these suspension degrees of freedom seem to have moved.  I don't have any evidence that this is related to our locking difficulties, but it seemed worth writing down.

We've been having issues during initial alignment with the ALIGN_IFO node falsely convinced that SRY is locked when SRM is actually very misaligned. This was due to the SRCL trigger turning on too early (see H1:LSC-SRCL_TRIG_MON). Sheila and I looked at the LSC SRCL trig thresholds and decided to bump these up to ON:0.3 OFF:0.2 (last two changes of this - alog54799 and alog63678). I also added a trigger delay of 0.5s since it seems to flash above this threshold even at times that we are very misaligned. This trigger looks at the POP A DC signal, so we aren't sure why the amount of light has changed on this PD. These settings worked for the one time we tried it with a well aligned SRM, so we should keep an eye on it the next few times we do alignments.

This second alog63678 reminds future us that we should recommission SRY to use the AS WFS rather than the REFL WFS. I'll remind future, future us the same thing.

I lowered the FC-ASC TRIGGER THRESHOLD's ON value from 0.8 to now 0.7, since it hadn't been triggering on during Friday's locks (trends). I noticed because the green beam spot on the FC green trans camera was clearly off from normal. This FC trans trigger was first setup in LHO:68587, where it said the trigger_on threshold was 0.6 -- but it was 0.6 for < 24 hours, then changed to 0.8, where it's been since. I have SDF'd the trigger_on threshold as 0.7.

Also, ISS tripped off again, so I reset it. From the SQZ_OPO_LR guardian, I requested "LOCKED_CLF_DUAL_NO_ISS" (which turns off ISS and resets lockloss counter), then requested "LOCKED_CLF_DUAL", so the guardian turns on ISS again. Sheila just did this a couple days ago 69890, but I didn't change the ISS setpoint this time. I think this is happening related to SHG output power drifts, we could check the on-table pump aom alignment. We shouldn't be driving the aom this marginally given the SHG power output and ISS setpoint, we used to be driving ~4-6V to maintain this trans power given even lower SHG output powers, and now we're driving often around 2-4V, so ISS is often in a marginal wayn now compared to before.

Jennie W, Sheila D, Jeff K

In order to get an understanding of output losses to understand why we are not getting the level of squeezing we expect I ran craig's scripts to step the DARM offset. Instead of measuring PCAL line heights on DCPD_SUM at each step we will look at these line heights on OMC REFL.

As this PD is much noisier than DCPD I had to do some tuning of the PCAL lines we use. Since we have limited measurement time and the IFO was still at MAX POWER, Sheila suggested we spend some time tuning the line heights to use in the measurement.

By this point we were waiting for violin modes to damp while in the OMC_WHITENING STATE.

original PCAL EY and EX values are first image.

I ran set_up_pcal_for_darm_offset_test.py. Originally this uses:

PCALX 255Hz 40000 counts

PCALY 410.3Hz 40000 counts

but this did not give us the correct resolution on OMC REFL for the higher frequency of the 2. Neither OFS PD was saturated.

See Ref0 (4th image attached) for the OMC REFL spectrum with these settings.

I manually stepped up the 410.3Hz line in ampltiude (on PCALY PCAL_END screen to 48 000 counts at which point the OFS PD saturated. Following Jeff's instructions I turned off the loop_enable switch on the PCAL_END screen for PCALY, changed the amplitude down to 46000 and swtiched the loop back on. OFS no longer saturated.

see Ref1 (5th image attached) for new OMC REFL spectrum. This still does not give a good SNR.

I then switched off the OSC_SUM_MATRIX (ie. the output) and changed this line to 11.5Hz at an amplitude of 40000 counts. This does not saturate the OFS PD.

See Ref 2 (6th image attached) for the OMC REFL spectrum.

The IFO moved to NLN and this did not change the PCAL settings I had on.

The third image attached shows the PCALEX and EY settings we used for the DARM offset measurement.

I then ran DARMOffsetStep.py starting at GPS 1368922456 to step the DARM offset.

Jeff reset the PCALEY and EX values using sdf.

xml from tuning measurements is in /ligo/home/jennifer.wright/git/OMC_mode_matching/2023-05-23_DARM_offset_meas.xml

Code is in /ligo/gitcommon/labutils/darm_offset_step

DARM offset results are in data/darm_offset_steps_2023_May_24_00_13_58_UTC.txt

Stay tuned for processed measurements.