(Corey, Kiwamu)

After no obvious headway, Jim and I both were thinking another Initial Alignment was looking inevitable.  After he left around 1am, I went about starting an Initial Alignment. 

During the alignment, while in ALS, I noticed one of the control signals not converging (ETMX M0 LOCK Y OUT 16).  Is this normal?  I went ahead and offloaded Green WFS.

Problems locking the Xarm for Input Align

Then when starting Input Align, the Xarm simply would not lock.  Would get fringes which would give powers up to 1.0, but they were less than a second.  The Mode Cleaner would drop out every few minutes as well.  When there were fringes in the Xarm, one could see the ASAIR spot shift in yaw a little.  These were the symptoms.  I waited for about 20min.  Then I woke up Kiwamu at about 1:45am PST.

PR2 Tweaked In Yaw

Since the IMC kept dropping, we addressed input pointing by tweaking PR2 in yaw.  I moved 1.0 units (from 4313.6 to 4312.6)

Dark Offsets

Kiwamu suspected bad dark offsets, so we pitched MC2 to prevent IMC locking, and then ran the dark offset script (/opt/rtcds/userapps/release/asc/common/scripts/setQPDoffsets)

After running this the offsets were not zero (more like 4!).  Found offsets in the SUM filter banks (which are at sitemap/LSC/Photodetectors overview/X_TR_ {A & B} /SUM {full}.  We took these to zero & were now happy with offsets.

At this point, I went to get water while Kiwamu watched X-arm locking.

LSC XARM Gain

We tried to give Xarm a kick by enabling the ETMX M0 LOCK L OFFSET (& also disabled the BOOST [FM4]), but this didn't have much of an effect....

While I was getting water, Kiwamu changed a gain for XARM (located at sitemap/LSC/Overview/XARM).  The gain is usually at 0.05 during INPUT_ALIGN, but Kiwamu took it to 0.1 & this finally locked XARM.  So to get the XARM to lock one doubles the gain, waits for it to lock up, and then drops it back down (i.e. to 0.05).  

At this point we decided I should start over with the alignment, and that Kiwamu would go back to sleep...I think we were on the phone for about 1-1.5hrs.

Back to Initial Alignment & Locking

Ran through an Initial Alignment with no noticeable issues.  (Dark Mich took a while to settle down; that seemed new to me, and Jim noticed this, too when I saw him aligning).

Finally went for locking.  Had issues at various points.  For ALS, there were VCO/PDH Errors popping up on Guardian.  Going to the Yarm VCO showed errors on that screen (ALS_CUST_LOWNOISEVCO.adl).  So, from Sheila's Training powerpoint file, I saw that I should take the Tune Ofs slider to zero, and that took care of that.

ASC Soft FM1 -20dB filters:  OFF!

Since useism has been trending down over the last 12 hrs, and since the BSC-ISI blends are back to the 90mHz ones, I opted to let Guardian Turn OFF the ASC SOFT filters.  This is different from previous lock segments!

Made it to NOMINAL_LOW_NOISE!

After over 4.5hrs H1 was finally back to NLN!  SDF had a few Diffs, so I went through them:

• SUSETMX:  ETMX M0 LOCK L  FM4 (boost) was left OFF, so I re-enabled it.
• ASC:  ASC {D & C} SOFTs for {P & Y}:  These filters had been kept enabled (giving us -20dB) for the last few days, but since useism is lower, I did not enable these & let Guardian do its thing.  I ACCEPTED these.
• OMC:  the LSC OMC matrix element was 0 again (as I noted), so I REVERTED it to 14 & hit LOAD MATRIX.  Why is this slipping through the cracks??  Is Guardian supposed to handle this?  (Kiwamu says we should ACCEPT the 0 value next time we get the chance, since this matrix element is irrelevant, it's an OMCDC to CARM element.)
• ISCEX:  Dark Offset stuff!  I ACCEPTED all of this stuff.
• ISCEY:  Dark Offset stuff!  I ACCEPTED all of this stuff.

O1 CDS Overview RED TIMING ERROR

Before going to Observation Mode, I noticed SUSETMY had a TIMING RED box.  Clicked "Diag Reset" to clear.

Went to Observation Mode at 11:32UTC

[Time for lunch]