Lockloss at 8:16 (lockloss file)
Reverted to 35W per Sheila's alog and noted in my earlier "Back to Observing" alog. Here is the "Operator Play By Play" for locking.
NOTE: This is after two new states:
- Higher Power (37W) lockloss
- New Operational changes to ALS & DRMI from Tuesday. (Sheila requested operators to give a play by play for how handling these new changes affects locking.)
Play By Play Notes:
- Locking Arms Green started out fine with both X/Y looking good and WFS engaged...but within seconds, they both nose-dived. (! See 1st Attachment) (Maybe this was due to being hotter than normal due to 37W?)
- Operational Oddity (to me atleast): ALS_YARM & XARM were both already selected for "UNLOCKED"! (I was about to select UNLOCKED something we usually do to touch up alignment, but it was already selected & this didn't look right.)
- in the ALL-screen for both, they were NOT in UNLOCKED state. They were in the OFFLOAD_ETM_TMS_WFS state! Something is up here...maybe this is due to the recent work on Tues? (see 2nd Attachement)
- Operator Manual Adjustments Begin: I selected UNLOCKED, & node went to UNLOCKED (for xarm). Touched up alignment via ETMx & TMSx & then went to the usual LOCKED_SLOW_W_GR_WFS_PUM. (was a moment when arm power was driven off a little, but it came back to a nice 1.1).
- [note: I now think, the new thing is we should take these guys to OFFLOAD_ETM_TMS_WFS!]
- Did above for Yarm next.
- Unfortunately, noticed Xarm alignment drifting low (down to 0.8) while working on Yarm. Ugly. (NOTE: survived this)
- Both X & Y looked fine according to ALS X/Y guardian nodes, but ISC_LOCK appeared to be stuck at LOCKING_ARMS_GREEN (!)
- [note: This was due to the new ALS change from Tues....figured this out during next lock]
- Went to DOWN
- Looks like my mistake above was going to the usual LOCKED_SLOW_W_GR_WFS_PUM, because LOCKING_ARMS_GREEN completed on its own (when it made it to the new OFFLOAD_ETM_TMS_WFS. (This is new to me).
- 9:07 Waiting for DRMI.
- Operator Manual Adjustments: No DRMI after 10min. Went for PRMI.
- Operator Manual Adjustments: PRMI locked fine. Only able to get POP18 to about 56.
- 9:22 - 9:25 Time for DRMI to lock.
- 9:30 Reached OFFLOAD_DRMI_ASC....decided to stay here a few minutes...just in case.
- 9:34 Moved on from OFFLOAD_DRMI_ASC since all signals looked nice & selected NLN.
- NOTE: Notice ALSx is at 29 (via DIAG_MAIN) while H1 running through ISC_LOCK.
Additional NOTE: I wasn't sure whether to mark downtime as "locking" or "commissioning". I did a little bit of both, but mostly "commissioning", because I had to undo some high power stuff and then had to deal with new procedure for ISC_LOCK from Tues work.
10:04 Back to OBSERVING
In regards to the ALS_X/YARM in UNLOCKED, on the main guardian screen for a node, there is a Request area below State and Target. This area has 2 fields, an EPICS readout and a state selector. The state that the state selector reads is not an accurate way to judge what state we are in, hence the EPICS readout right above it. There are only so many states that can fit on the state selector, so if a state is requested from a manager that is not in the selector, it will not be able to show it there. Recent changes have added new states to this node, most likely pushing Unlocked off of the state selector.
Hopefully this clears it up a bit.
Thanks for the explanation, TJ!
I really wanted to note/document what I saw because it was different from what I had been used to & so it had me scratching my head a little. But I do remember there were changes made on Tuesday. Anyway, I've had experience with the new way it works now and think I have it down. THANKS!