Testing stack stability after large piston moves
This procedure is intended to test how well M1 retains its alignment after a series of large piston moves. It should leave the mirror in good shape, but be warned that in the worst case scenario a second stack may be required.
Here's the procedure:
- Do a stack
- Note that the s1 iterations are saving their corrections to these files:
wave: E:/CorrectionsPlotting/YYYYMMDD/YYYYMMDDThhmmss.ttp
- Note that the s1 iterations are saving their corrections to these files:
- Do the normal stack measurement (HEFI + extra-focal)
- Let SAMS "settle down" to stabilize, 2-3 min? TO use their intuition
- Hand over to Chris for him to do the piston moves. He will:
- disengage SAMS (stop SCS from listening, no move authority)
- execute piston step-through motion script on ~20-24 segments, moving in 100um steps for a 500um range
- return all segments to their nominal/zero piston positions
- engage SAMS
- hand back to the TO for the next steps
- Let SAMS "settle down" to stabilize, 2-3 min? TO use their intuition
- Do a normal stack measurement (HEFI + extra-focal)
- Do an s1 iteration (corrections automatically saved)
- Consider saving another reference here if there was a big change (TO use their judgement)
If the stack looks good, continue with your night. If it looks bad, a re-stack may be required before resuming science operations.
Last modified 3 years ago
Last modified on Aug 20, 2021 10:13:49 PM