corey.gray@LIGO.ORG - posted 03:41, Sunday 15 October 2023 - last comment - 04:35, Sunday 15 October 2023(73471)
H1 Stuck At FIND_IR and My Computer Monumentally Slow
After a 1hr59min lock, H1 had a lockloss and H1 was stuck at FIND_IR with ALS DIFF needing "Search for IR Resonance by hand" at 947utc/247amPT.
Unfortunately, my computer has been monumentally slow so. I have rebooted my computer and it is a little bit easier, but still very hard to work on H1 because of the slow NoMachine interface. I was able to FIND IR (very slowly due to my computer) by moving the DIFF OFFSET only a few clicks.
ISC LOCK continued.
- My computer/NoMachine slowly was able to open other screens (i.e. AS AIR video, ndscope to look at POP18 & 90).
- DRMI did not lock, so ISC LOCK (I am guessing went to only ACQUIRE_PRMI) and stayed in this state for quite a few minutes...
- Was able to (slowly) determine PRMI locked, but was misaligned.
- I (eventually) took ISC_LOCK to PRMI_ASC. Once it made it there, I requested the NLN state.
- H1 locked DRMI, but it has been stuck at ACQUIRE_DRMI_1F for about 8min so far. I don't know now it's not proceeding. ISC LOCK's log says that 10:36utc it wants to "try_PRMI".... but I'm confused if this is an old notification....because my computer is slow.
- This. Is. Frustrating!!
- Going to give this a few more minutes and then consider driving to site because this set-up is not optimal.
Although I had requested NLN for ISC_LOCK, on my (slow) computer it was "stuck" at the ACQUIRE_DRMI_1F state (it was hard for me to tell why it was stuck here....it should continue on to DRMI_LOCKED_PREP_ASC, etc. etc., but ISC_LOCK was stuck at ACQUIRE_DRMI_1F.
QUES/NOTE: --Could this be due to GRD_IFO being in the Automatic Operation state?
I then requested ISC_LOCK to go to the next step: DRMI_LOCKED_PREP_ASC
It immediately went there with no problem. I then selcted one-step-at-a-time on ISC_LOCK & it proceed fine to each step.
On ISC_LOCK, I then requested a bigger step of going to PREP_ASC_FOR_FULL_IFO, and ISC_LOCK continued on its own to PREP_ASC (as normal!). (around this time, since I had time to NOT babysit, ISC_LOCK, I took GRD_IFO to MANUAL operation...in case that could be an issue.)
While waiting at the ENGAGE ASC state....I requested ISC_LOCK to go to CHECK_VIOLINS_BEFORE_POWERUP.
ADDENDUM: It his hard for me to determine if there was an actual problem here, because my computer has been very slow....so all troubleshooting has been painful to perform. But since ISC_LOCK appears to be returning to normalcy (as seen from my SLOW computer), I am going to take GRD_IFO to AUTOMATIC operation and let H1 continue as it has done (from what I'm told, has been 3+ weeks with no issues...up until this morning's issue....which is either (1) a legit problem with H1, (2) a problem with my extremely slow computer, or (3) a combination of 1 & 2.
It is 1058utc (358amPT), and ISC_LOCK is at Check VIOLINS (just made it to this state), so I then requested NLN on ISC_LOCK. I am hoping ISC_LOCK can continue on its way, as normal.
At 1101utc/401amPT, I am taking GRD_IFO to AUTOMATIC operation....the hope is H1 will be back up to OBSERVING within the next 30-45min.
[Crossing fingers]
After taking GRD_IFO to AUTOMATIC operation (via OPS_Overview medm), I returned to the H1_MANAGER guardian node, because it had been having a notification from the beginning about requesting an INIT to clear it's notification (I remember trying an INIT several times, but this notification would NOT clear.).
However this time (about an hour later), I was able to clear this notification when requesting an INIT.
As of 1107utc/407amPT, ISC_LOCK is at MOVE_SPOTS.
Additional Notes:
NoMachine interface & my computer appear to be much better, although still not great/normal. I do have a new wireless mouse that I'm using and it's operation is dodgy, so I only use it as a last resort.
Another note with my laptop is that in the evening, I log into NoMachine and leave it logged in overnight (so if action is needed, I can jump into my session and start working on H1.) Perhaps this is a bad procedure? I noticed that although my laptop is plugged into power, it's battery was very low when I first logged in to work on H1 this morning. (not sure why this is the case since it is plugged into power) After working on H1 the last 90+min, my laptop battery has increased from a low percentage to 52%. Maybe I should not keep my laptop logged into NoMachine overnight? (I only did this so I could save time and could hit the ground running....but maybe my computer (and I!) can not handle this.)
1114utc/411amPT & ISC_LOCK is at TRANSITION FROM ETMX.
Will NOW let H1 continue on its way.
1126utc: Will continue to baby sit H1 until it is back to OBSERVING. Currently waiting for CAMERA SERVO.
1134utc/434amPT: H1 Back To Observing AUTOMATICALLY
In the hopes I do not have an issue with my computer/NoMachine, I am going to completely log out of NoMachine, close my laptop for the night, and keep it plugged into power tonight/this morning.....just....in ....case.