This morning, Stuart and I used the SDF front end to take new SAFE.SNAP snapshots of the balance of the suspensions - recall, he had done the BS previously, see alog 16896.
Repeating his alog instructions on how to perform this:
- Transition the Suspension to a SAFE state via Guardian - On the SDF_RESTORE MEDM screen available via the Suspension GDS_TP screen select FILE TYPE as "EPICS DB AS SDF" & FILE OPTIONS as "OVERWRITE" then click "SDF SAVE FILE" button to push a SDF snap shot to the target area (which is soft-linked to userapps). - This safe SDF snapshot was then checked into the userapps svn: /opt/rtcds/userapps/release/sus/h1/burtfiles/ M h1susbs_safe.snap
Note, please don't use the BURT interface to take SAFE.SNAP snapshots anymore, as the SDF monitoring will become disabled. All other snapshots are free to be taken via BURT, however.
Also, we found many alignment values not saved on IFO_ALIGN which, after confirming with commiss, we saved.
To be clear, the IM2/3 guardian nodes hadn't crashed, they had just gone into ERROR because of the snap file parsing issue.
Also to be clear, there is a bug in the ezca.burtwb() method, which is being used to restore the alignment offsets, such that it doesn't properly ignore blank lines. This will be fixed.
Unclear why these alignment snap files had these extra blanklines. My guess is that they were hand edited at some point.
Above, when I said "Note, please don't use the BURT interface to take SAFE.SNAP snapshots anymore, as the SDF monitoring will become disabled. All other snapshots are free to be taken via BURT, however."
I was just speaking to SUS safe.snaps. Sorry for the confusion.