Reports until 14:00, Wednesday 08 May 2019
H1 SUS
jenne.driggers@LIGO.ORG - posted 14:00, Wednesday 08 May 2019 - last comment - 23:09, Tuesday 14 May 2019(49119)
Restored PR3 sliders to 24 hours ago

It looks like the PR3 sliders weren't restored after the Dolphin crash last night, so our IFO alignment has been a bit wonky all morning (one lock we saw some beam on AS AIR even with the beam diverter closed, which indicates something is definitely funky).

I restored the PR3 sliders, and now JeffB is doing an initial alignment starting with INPUT_ALIGN (the green arm alignment should still be fine from Corey's alignment last night).  Hopefully this will help things out a bit.

Comments related to this report
corey.gray@LIGO.ORG - 14:43, Wednesday 08 May 2019 (49121)

Oh wow!  And the PRC_ALIGN section of the INITIAL_ALIGNMENT I ran, ran completely on its own, so I didn't worry about it so I could focus on the other problems (hence, I didn't mention PRC ALIGN in my Alog....it and the Green Arms did not give me issues when I tried them). 

Sorry about that!  With SUS, I only looked at sliders for mirrors which were giving me grief, and since PRC was taken care of by Guardian I didn't even look at them.

Good Luck!!!  
P.S.  Not sure of best check for SUS after dolphin crash. Sounds like we should go through and restore ALL of them to a good time (instead of do them willy nilly like I did).  What's the best way to do this?

  •  Do we still do burt restores? 
  • Should operators Time Machine the whole IFO_ALIGN screen? 
  • Can we use SDF to help?
  • Conlog, dataviewer, or ndscope individual slider values?
jenne.driggers@LIGO.ORG - 15:11, Wednesday 08 May 2019 (49122)

I caught this by looking at a time machine of IFO_ALIGN_COMPACT for 24 hours ago.  So, I usually look at all of the slider values.  Ndscope is also fine, but I find this to be quicker.

Also, I have re-monitored all of the slider values for the optics in the safe.snap files that are loaded when the models reboot.  We don't accept values in the safes all that often, but we do sometimes.  For example, I cleared all of the safe.snaps a week or so ago, but didn't think to look at the not-monitored channels.  By re-monitoring them, we'll hopefully get a more recent value for all of the sliders when we have an unexpected reboot.

jenne.driggers@LIGO.ORG - 15:43, Wednesday 08 May 2019 (49123)

A consequence of this is that, for the suspensions whose observe.snaps are just links to their safe.snaps, we will have to accept any OPTICALIGN SDF diffs when we go to Observing.  However, the suspensions that have this situation are ones like IMs 1-3, the RMs and the OMs that really shouldn't be changing ever.  So, operators in general shouldn't see these as diffs every lock.  If you do see these as diffs when you are trying to get to Observe, let's continue to screenshot them so that we can understand why they are changing.

sheila.dwyer@LIGO.ORG - 23:09, Tuesday 14 May 2019 (49250)

Several other suspensions also have the safe.snap linked to the OBSERVE.snap, so each time we run inital alingment now we are having to accept sliders for many optics.  I think it makes sense to un-monitor these, and find a different way to keep track of the slider values.