Introducing the new LASER_PWR Guardian node! Use it to change the power by selecting one of the three requestable powers (2W, 10W, 22W) or open the "ALL" screen to select any 'POWER_#W'. I attached a shot of the graph if you're curious. This node is nominally manged by ISC_LOCK and then ALIGN_IFO during initial alignment (though this has created some usermsg issues that I am trying to work around, more on that later).
I have also changed around some of the management for initial alignment. If the user wants to run initial alignment:
1. From READY in ISC_LOCK, go to manual and select INITIAL_ALIGNMENT
2. Wait for ALIGN_IFO to run through its DOWN state. This will temporarily take control of the ALS's, LASER_PWR, and IMC_LOCK nodes.
3. Run the green alignment from ALIGN_IFO instead of each of the ALS nodes. Offload the green WFS at the same ti.
4. Continue as usual, during SRC the LASER_PWR node will bring the power up to 10W and then back down after.
6. When done with initial alignment, make sure to go to INIT on ISC_LOCK to take back control of the nodes. then continue as usual.
I added the LASER_PWR, as well as the SR3_CAGE_SERVO nodes to the Guardian Overview screen (shot attached).
I also slightly changed the ISC_GUARDIANS medm to show who the managers are of each node and placed the new node on the bottom. (shot also attached).
As I mentioned above, there are some user messages that will pop up on ALIGN_IFO and ISC_LOCK about the nodes being stolen by one another. This isn't a big deal for ISC_LOCK to report this whie we are in the middle of initial alignment, but it isn't good for ALIGN_IFO to be continuously notifying during normal locking. I have something that I want to try next opportunity I get, hopefully tomorrow. And if that doesn't work, Jamie seemed to have an idea of how to solve these types of situations that will be in the next Guardian release. Until then we can not manage the nodes during initial alignment just as before.
Quick update on Initial Alignment procedure.
After switching to the INITIAL_ALIGNMENT state in ISC_LOCK, the nodes usually used for IA will no longer be automatically managed. These will stay UNmanaged just like before all of this.
I tried to make a go around for the management by redefining the list of nodes that were control by the NodeManager object. This was plan B since I could not create a second object like I had originally hoped. Plan B also did not work though. While it did manage to get rid of the user notifications, it would regularly get confused and say something like "Node X was in state A, now state B" even though it was the one that had set state A and B. Seems like we will just have to keep it this way until the next grd release, but since this is basically like it was before it's not a big deal.