Displaying report 1-1 of 1.
Reports until 03:20, Tuesday 10 September 2019
H1 General
corey.gray@LIGO.ORG - posted 03:20, Tuesday 10 September 2019 - last comment - 16:44, Tuesday 10 September 2019(51837)
H1 Locking Status: Backing Out IM Move From Sunday Night, Initial Alignment Woes, & Remote Jenne Assistance!

Since we went about 3hrs with constant locklosses for both Niko & I (along with two Initial Alignments by Niko), I decided to back out the IM change from last night which had a data point of the one lock we had since last night in the hopes of returning to the input pointing we had been running will help with locking.

IM Alignments Restored To Sunday Night Values

IM1, IM2, IM3  restored to where they were before the last lock.  (settings restored from SDF list here).

Initial Alignment

With the new Input Pointing, I needed to run an Initial Alignment.  Took a little longer than usual, due to....

Operator (me) Errors:

Error #1) IM Slider Mistake:  Noticed Xarm in IR was not locking for INPUT_ALIGN.  Couldn't determine the issue, buuuuut.....

--I had a commissioner monitoring remotely (from Japan!).  Jenne let me know that one of the IMs was way off!  I errantly entered IM2's Yaw slider (I added an extra "0" for it's value).  After this I continued with alignment

Error #2) Green Y-arm Dead:  Green Y had no light flashing!  Probably due to me taking multiple Nodes to DOWN

--Once again Jenne helped me here, and she noticed my ITMy was waaaay off.  I had noticed ITMy was labled as MISALIGNED, so I tried taking it to ALIGNED, but it wouldn't work.  So I did a MANUAL to ALIGNED & then back to AUTO, but this misses steps.  So Jenne had me take it to MISALIGNED, and then to ALIGNED, and this finally gave us light flashing in the Y-arm.

Error #3)  Possible Sticky Slider:  During alignment, SRC was continually stuck at around PREP_FOR_SRY

--Jenne tracked this down to an optic not in state Guardian liked.  I believe this was ITMx & the issue was a "sticky slider".  Will make separate alog for this.

Current Status:  Just had my first lock attempt after restoring IMs and doing an alignment.  Had lockloss at ENGAGE SOFT LOOPS.  This was fairly early on this step & did not see any obvious reasons for the lockloss.

Additional NOTE:  IMC guardian node has flashes of a notification of "IMC WFS not centered".  This messages flashes quick, has been occurring fairly frequently, and is new to me.

Comments related to this report
corey.gray@LIGO.ORG - 04:43, Tuesday 10 September 2019 (51839)

ADDENDUM:  Did NOT Revert IMs to Sunday night values!

I thought I had reverted the IMs back, but when I finally made it back to OBSERVING I noticed that there were no SDF diffs for SUSIM for me to ACCEPT! 

I think the problem for my brain was that after I made the error in restoring IM2's Yaw slider (adding an extra "0" which Jenne caught), my mind had me sticking with all of the new IM slider values (vs the old slider values I wanted to revert to)!!!  So I ran an Initial Alignment thinking the input pointing was referted, but it really wasn't.  Grrrrr!  My Mistake!!  

Since it has taken roughly ~5hrs of locking to get us back to OBSERVING (+ 2hrs of my aligning), I'm still thinking we want to back out the IM pointing change from Sunday night since locking has been tough---IM values can be found here.

jeffrey.kissel@LIGO.ORG - 16:44, Tuesday 10 September 2019 (51871)IOO, ISC, SUS
The IM1-3 slider values were reverted today (2019-09-10). See LHO aLOG 51858.
Displaying report 1-1 of 1.