TITLE: 11/06 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently trying to relock and at ENGAGE_DRMI_ASC after finishing an initial alignment. It's been a rough shift, with issues relocking.

Trouble with locking:

• We had a lockloss from CARM_5_PICOMETERS where it looked like something was being seen in FSS fastmon, IMC-TRANS, and the ISS_AOM_DRIVER channel for over a minute before the lockloss (attachment1)(maybe this is normal and alwys happens during this state?). After this, the FSS would not let the IMC lock. There would be giant FSS oscillations in the fastmon channel while PSL_FSS moved between READY_FOR_MC_LOCK and FSS_OSCILLATING (attachment2). Even after it stopped oscillating, there were a few quick glitches that were also seen in the IMC (attachment3). Tagging PSL
• Not completely sure if this is related to the PSL/IMC issues, but while running an initial alignment, we couldn't get past MICH_BRIGHT_ALIGN and IMC-MC2_TRANS_SUM looked like attachment4. IMC-TRANS and FSS_FASTMON were oscillating, but I'm not sure if that's happening as the issue or as a response to something else. Tagging PSL again, sorry :( To solve the problem I took the detector out of initial alignment and waited for everything to calm down (the beamspots and table on the PSL cameras were going crazy), and then continued the IA once that had settled.
• When we got to ENGAGE_DRMI_ASC/the end of PREP for DRMI, before I ran the initial alignment, the beam spots on AS AIR would be shaking and the beamsplitter would start saturating and we would either unlock DRMI or lose the lock. I tried adjusting SRM because we were getting through PRMI fine, but it just seemed to make it worse, so I ran an initial alignment. After that we got up fine without the shaking, but after the next lockloss we started having the shaking/saturations again so I ran another initial alignment. No shaking/saturations this time in ENGAGE_DRMI_ASC. Tagging ISC

Good news is that we haven't had the new AS AIR PD(81080), PEM-CS_ADC_5_19_2K_OUT_DQ, saturate during the last three locklosses! The highest number of counts we've gotten have been around 16k counts. I have also put in a feature request for the integral of the channel's peak at lockloss to be calculated and put onto the lockloss pages, and assigned it to me (Issue#223). (ISC)
LOG:

00:00UTC In DRMI and trying to relock after a 28 minute lock
00:44 NOMINAL_LOW_NOISE
00:50 Observing

00:58 Lockloss
    - 01:21 Lockloss from CARM_5_PICOMETERS, and FSS wouldn't let the IMC lock?
        - Started getting giant FSS oscillations while it was trying to lock/was locked(attachment2)
        - Went to DOWN, went to IDLE, tried toggling FSS autolock, nothing worked
        - Put detector in DOWN for 10mins and then tried again
        - Seemed fine??
    - DRMI locklosses during ENGAGE_DRMI_ASC x 3
        - BS saturations and beams on AS AIR visibly start shaking from end of PREP until DRMI unlocks
    - 02:12 Started an initial alignment
        - At MICH, started having issues with it not being able to get past MICH_BRIGHT_ALIGN (attachment4)
        - PSL table flashing all over the place
        - Took ifo to DOWN, waited a while, then tried again with manual IA and no issues
    - 02:37 Initial alignment done, relocking
03:43 NOMINAL_LOW_NOISE
03:45 Observing
    - 03:57 Out of Observing to adjust OPO temperature
04:08 Back into Observing

04:28 Lockloss
    - Took 15 minutes for IMC to relock
    - Started relocking with H1 Manager
    - ENGAGE_DRMI_ASC had the beam spot shaking and BS saturations again, sometimes leading to LL x 4
    - I started an IA
    - IA done, relocking