DCPD saturation then lockloss, no obvious reason.

STATE of H1: Observing at 146Mpc

We've been locked for 9:20, no issues aside from another MY low temperature alarm.

Briefly dropped from Observing from 08:18:42 to 08:18:59 from an unknown issue, whatever SDF diff or grd node issue resolved itself before I could open the medms.

TITLE: 07/23 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Taking over from Oli, we've been locked for 5:16

CDS/Vac/SEI/SUS/Dust looks good

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

23:00 Detector relocking (71617)

    23:03 Lost lock at TURN_ON_BS_STAGE2

    23:11 Lost lock at AQUIRE_DRMI_1F

    23:13 Lost lock at LOCKING_ALS

    23:22 Lost lock at ENGAGE_DRMI_ASC

23:24 H1_MANAGER decided to start INITIAL_ALIGNMENT

23:42 Disabled H1_MANAGER while in INITIAL_ALIGNMENT (paused 71619) bc it was stuck at AQUIRE_SRY in ALIGN_IFO - we are skipping initial alignment and going stright to trying to lock again

~00:30 Dustmon in PSL reached 230 counts for particles >300nm. Going back down now.

00:49 Entered OMC_WHITENING, damping violins

1:45 Entered NOMINAL_LOW_NOISE
    - SDF Diffs ACCEPTED for SUS-ITMX_L2_DRIVEALIGN_P2L_SPOT_GAIN and SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN (71618)

1:49 Entered Observing

6:35:02 Pushed out of Observing and into Commissioning - not sure why
6:35:28 I put us back into Observing with no issue

LOG:                                                                                                           

Lockloss from NLN @ 22:38 7/22 - Not sure of cause yet, but winds were very high.

While trying to relock, we lost lock at:

• TURN_ON_BS_STAGE2 @ 23:03 7/22
• AQUIRE_DRMI_1F @ 23:11 7/22
• LOCKING_ALS @ 23:13 7/22
• DRMI_LOCKED_CHECK_ASC @ 00:07 7/23

presumeably all from the wind.

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

H1 was humming along at almost 45hrs---and then a lockloss toward the end of the shift.  Did take out of observing for about 20min to adjust the SQZ ISS set point.  Winds have also been increasing through the day possibly rustling up dust.
LOG:

• 1504,1528, 1824 LOW temperature alarms at MY (Bubba contacted)
• 2018-2043 Squeezer ISS Setpoint adjusted. (alog 71613)
• 2228 Dust alarm for Optics Lab area
  • 2235 Dust alarm for PSL.
• 2238 LOCKLOSS (winds had been picking up and we didhave some gusts above 40mph around this time).
• Tweaked up X-arm; PRMI acquired and I tweaked BS in pitch to optimize; DRMI locked once, but lost lock and this is where I hand off to Oli.

TITLE: 07/22 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 10mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Detector lost lock a few minutes before I arrived, possibly due to high gusts of wind. Currently relocking using H1 Manager.

The DARM noise between 18 an 21 Hz is due to calibration line upconversion by ASC motion. 
This is shown by the bicoherence between DARM and ASC-DHARD_Y, and also by the fact thta DARM is coherent with calibration line signals multiplied by ASC signals (see two examples attached)

We should repeat a test with CAL lines off again now that the low frequency sensitivity is better.

On mattermost, Vicky mentioned that she and Naoki felt we needed to increase the Squeezer ISS setpoint from the value Ryan C used last night to improve H1 range.

SITUATION:

• H1 and L1 were both OBSERVING.
• Reached Jenne and because this was a quick change, we decided to make the change, as long as we contacted the LLO operator to let them know:
  • We would be dropping from Observing for a quick change
  • Give them a heads up in case they had any quick Target Of Opportunity out-of-observing tasks
  • Mike F said they had no reasons for dropping Observing (but he was also, at the moment, worrying a passing storm would possibly drop them out anyway.
• Dropped H1 from OBSERVING (marked OBS Mode as "CORRECTIVE MAINTENANCE")
• Followed the procedure from alog 70050, as Ryan noted and used.
• My notes from the procedure:
  • For Step #3, after I changed ISS Set Point, SAVED text file, and LOADED SQZ_OPO_LR guardian, I then tried to go to LOCKED_CLF_DUAL_NO_ISS (w/ Log open), but I never "arrived" (i.e. the STATE box remained orange --even after MANUAL request).  In hindsight, I don't think "arriving" mattered, because Vicky ended up phoning and walked me through several ISS Setpoint changes.  Just thought I would note this since this was my first time running through this procedure.
• Tried several ISS Set Point changes from it's 50uW value:  Went to 75, 80, 85, and then settled on 80, because it yielded the optimum Control Monitor Voltage we wanted (basically 3.0V vs anything closer to 2V). 
• Once settled on 80uW, tweaked "OPO TEC TEMP" slider on the SQZ Overview medm while maximizing *CLF-REFL_RF6_ABS (green) channel from the ndscope noted in procedure for Step#3.
• The single SDF diff was this temperature slider change noted above (see attached screenshot for what was ACCEPTED).
• 2018-2043 Out of OBSERVING
• Range increased roughly from 143 up to 149Mpc.

Smooth morning with only some low temperature alarms @MY, one EX saturation on H1, and 41hrs of lock w/ a range around 145Mpc.  Breezes have steadily been picking up over the last 5hrs.

Sat Jul 22 10:07:31 2023 INFO: Fill completed in 7min 27secs

Note TC-B was not static at -200C when LN2 was flowing and warmed up much faster than TC-A.

Received another Low MAJOR (red) Alarm Handler alarm similar to what RyanC reported overnight.  Attached are relevant trends.  The chiller looks operational; MY VEA temperature sensors took a step down on Tues morning (correlating with Tues Maintenace Fan lubricating), and the MY VEA is now a full 10degF lower since Tuesday's fan work.  Although it's only a mid-station, I will still send a text to Bubba (I reckon due to the drop is equalizing below the LOW alarm setting, this alarm will be ongoing until temperatures raise or the alarm settings are changed).

TITLE: 07/22 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.04 μm/s
QUICK SUMMARY:

Wow!  Walking in to a nice long shift (almost 37hrs).  RyanC mentioned a few issues he had earlier (SQZ bumping us out of OBSERVING, Mid-Station low temp alarm), so will be prepared for that.  80DegF & low winds.

TITLE: 07/22 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
SHIFT SUMMARY:

• Handing off to Corey, we've been locked for 36:50
• MidY temperature alarm at 8:54UTC, Zone202B specifically, it seems to be a low temperature alarm, the temps came back up after about an hour and the alarm stopped.
• We briefly dropped out of Observing due to the ISS pump saturating at 14:41UTC, guardian prompted me to alog70050 which I followed setting opo_grTrans_setpoint_uW to 50 and adjusted H1:SQZ-OPO_TEC_SETTEMP to recover the ISS, I had 1 SDF diff to accept from this. Back into observing at 14:48UTC.

LOG:

No log

STATE of H1: Observing at 151Mpc

All's stable, We've been locked for 32:5

TITLE: 07/22 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
SHIFT SUMMARY:

23:05 Detector Locked and Observing

7:00 Detector Locked and in Observing for 28hrs 50mins

Uneventful night besides the PSL dust monitors going off.
As of now PSL Dust monitor 1 for particles >300nm is down to a value of 90.

LOG:

No log

After Gabriele made a major improvement on the DHARD Y coupling (alog 71588), since LLO was still working on relocking, I checked the A2L gains for the 3 test masses that we use for ADS during locking.  The summary is that the change seemed to be small enough that it's not worth keeping long term, so I have not modified ISC_LOCK.  I did accept the changed A2L gains for this lock, so next lock, the operator will see SDF diffs and need to accept them. 

Rather than being fancy and using the ASC as a metric for when the decoupling is good, I used 'the old way' of dithering the suspensions using the ADS and changed the A2L gains to zero the error signals. (To see the ADS error signals I had to put the gains H1:ASC-ADS_[PIT,YAW][3,4,5]_DEMOD_I_GAIN to 1, because they are set to zero by the camera servo guardian). 

The first attachment is how the ADS error signals looked before I made any changes to the A2L gains for EX, EY, or IX. This is after Gabriele adjusted IY in alog 71588. 

The second attachment is after I adjusted two of the P2L gains (the only two I ended up changing), to get the ADS error signals closer to zero.

The third attachment is the SDFs that I saved in the Observe.snap, that I did not put into lscparams/ISC_LOCK, so will need to be re-accpeted next lock at the values that guardian will set them to.

The fourth attachment is a comparison of the spectra (Brown before I changed any A2Ls, Red after), where I don't see much of a difference, but maybe Brown is better-ish anyway, which is why I'm planning to leave the A2Ls alone in the guardian.  But, we'll be able to see throughout this lock whether there is a change worth making.

I'd like to start running the H1_MANAGER for the next few days in a testing phase. We can watch it and see what it does, then make tweaks as needed. The idea behind this node is to determine whether or not an initial alignment needs to be run and to flag for help when a human should intervene. Here's a quick rundown on how it works:

There are three main states that users will select: LOW_NOISE, IDLE, INIT.

To Engage the node - Select LOW_NOISE, then click INIT. It should determine if we are relocking, running an alignment, or if we are already in low noise.

To Diable the node - Select IDLE. Verify it gets there.

If the node has determined that it needs help, it will enter the ASSISTANCE_REQ state and it will stay there until someone does the following:

To Re-enage from ASSISTANCE_REQ - Select INIT, then select your final desired state.