Open ambarb opened 8 years ago
This is expected, it should only roll back to the previous state when it is unstaged (which is not done when paused).
Sorry @tacaswell . I wasn't clear enough. It was paused and stopped/aborted. I will work out the details (now that I don't remember them) when the current users leave the beamline - ETA next Monday.
Oh, that is much worse. Put something on my calendar (~1 hr) to look at this.
@tacaswell The order of the unstaged signals may be key here - stop acquisition, then set continuous mode, etc.
I take it that it may be more sensitive to that order maybe more sensitive it it has not finished the acquisition?
IIRC unstage does run correctly in reverse order -- I think that's tested.
It should be tested and working - my comment was merely that stage_sigs
should be one of the first things to check when you sit at the beamline.
dif_beam
stats are plotted with vairous motor scans. If the scan is paused, the camera does not move back to continuous mode (mode prior to scan). It is stuck in multiple.PV parameters: