Closed ulrikpedersen closed 1 year ago
This is implemented in the current version of the plans due to the use of the checkpoint() Bluesky plan stub. This works as expected for the Bluesky driven step-scan. In the case of the "hardware-triggered" scan the motor will pause but the detector will continue capturing frames.
Closing for now as there is no specific work here ATM.
Do keep scan pausing in mind when implementing future hardware triggered scans and also when performing demos.
BlueSky does have a mechanism to support pausing (and resuming) scans. This is another important feature for end-users that we should enable.
Implement the pause functionality first in the BlueSky driven step-scan (the easier one, presumably). This would be a nice-to-have for the first Demo.
Consider how this could be implemented also for the "hardware-triggered" scan scenario.