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

LOCK#1:

• Green arms looked bad (not surprising after the long lock), so I decided to tweak manually.  However, instead of going to the GREEN_ARMS_MANUAL state, I went to the MANUAL _INITIAL_ALIGNMENT.  At any rate, I tweaked their alignment up, ran a down and then proceeded with locking, but directly to Acquire PRMI.  PRMI flashes looked dead and the video showed an obvious pitch misalignment.  Started by taking BS negative for Pit, but this didn't help, so I went positive, and this quickly locked PRMI.  Continued going taking BS positive and then optimized POP18/90 by tweaking PRM in pitch.  Then, I let ISC LOCK take over by quickly locking DRMI and continuing on.  Lockloss at ENGAGE DRMI ASC.  And on ASC signals, PRC2_P_INMON & PRC2_Y_INMON became noisy, as well as MICH_P_OUT16 & PRC2_Y_OUT16.  Verbal also mentioned BS saturations.

LOCK#2:

• Once again had a lockloss at ENGAGE DRMI ASC.  And on ASC signals, PRC2_P_INMON & PRC2_Y_INMON became noisy, as well as MICH_P_OUT16 & PRC2_Y_OUT16.  Verbal also mentioned BS saturations.  Attempted a few more locks all to end the same way (no surveys submitted for these repeat locklosses)
• Going for an Initial Alignment

LOCKs Post Alignment & with Laser Noise Suppression issue

• DRMI post-alignment looked noticeably better (POP18 was double what I had for the lockloss locks)---so H1 was just misaligned after the long lock.  Locking was fine until I encountered the LASER NOISE SUPPRESSION issue.
• Earlier there was DIAG MAIN message stating PSL Low Diffracted Power.
• IMC LOCK message:  "Second loop AC Coupling out of range, waiting 1 second to try again"
• LASER POWER message:  "Power not the same as requested"
• This was fixed by addressing diffracted power & iss 2nd loop ac coupling offset....but range does look a little lower.

LOG:

• 0751 LOCKLOSS (Lock Clock:  26hrs51min)
• 0852-0913 Initial Alignment
  • NOTE:  PRC Align had repeated IFO_OUT saturations.  Ryan S taught me this is due to saturations for the OMs.  I saw that OM1 & OM2 had Yaw saturations, so I cleared histories for this path and this cleared the saturations.
• 1358 Back to OBSERVING!  (and handed off to Ryan C)