The SUS Guardians will now read from the susconst.py file (in the h1 area), when going to the MISALIGNED state. This state will turn on the top stage TEST bank offsets to misalign the optic (conception of misalign state in alog17259), but previously it assumed that we have the correct values in that field already. This has bit us a handful of times because we also use the TEST bank for, well, tests. So, we will now have all of our misaligned values saved in the susconst.py to verify that we are  going to a consistent misaligned offset.

I also added a decorator in the idle ALIGNED and MISALIGNED states to check that the TEST Offsets are turned on/off when they should/shouldn't be. If there is a discrepancy, it will make a notification saying so. Our TMSs are an exception to this because we use them to move our spot around the point absorbers (only a local change). Since this is common code, I have already been in contact with LLO.

To sum up my changes:

(userapps)/sus/common/guardian/SUS3.py - Added a reference to a dictionary in susconst.py of misaligned values. Also added a decorator to check the state of the TEST Offset.

(userapps)/sus/h1/guardian/susconst.py - Added dictionary of misalignment offsets for every optic.

(userapps)/sus/h1/guardian/SUS_TMS.py - Changed to not use the decorator to check on the TEST offset.

(userapps)/isc/h1/guardian/ISC_LOCK.py - In the PREP_FOR_LOCKING state, it will reset the TMS TEST offsets to their misalignment values. It now imports susconst to get these values.