At the request of local commissioners, I have modified the SUS guardian code to go back to handling the setting of alignment offset values for the ALIGNED state, and have re-introduced the MISALIGNED state which sets the alignment offset to saved misaligned values.  This all was originally in the SUS guardian code, but was removed at LLO due to precieved problems with the SUS guardians handling the offsets.  The LHO commissioners, on the other hand, prefer the SUS guardians to have separate ALIGNED and MISALIGNED states.

SUS guardians have not been restarted yet.  Only SR2 for testing.  We're waiting until after the arm alignment tests are done.

NOTE: ALIGNED and MISALIGNED offset values MUST BE SAVED in order for the SUS guardians to restore to them! This is the big change by going back to this configuration.  When the SUS guardians were not touching the offsets, there was no worry that they would accidentally be reset.  Now that they are being set by guardian, we have to remember to always save the offsets appropriately after tweaking them.  Forgetting to save them could result in the current alignment being lost if the suspension trips or the alignment state is cycled.

As a bonus, the SUS guardians will use the notification USERMSG to notify you if the alignment has been changed and not saved.

Here's the current SUS state graph:

This is all just a stop-gap until we get a better comprehensive solution to the alignment offset problem.  This will likely be discussed in the next SYS meeting, on 9/9/2014.