You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SSX scripts currently use me14e_gp9 as a PV for whether we want to abort or not. The bluesky way of doing this is calling abort on the RE, this can be done through blueAPI using blueapi abort. We need to make sure that when the plan is aborted it correctly tidies up, we should do this with the contingency wrapper. We need to make sure the wrapper covers as much of the plan as possible so that if we get an abort when shutter is opening we properly close it. i.e. the chip collect will look something like:
defrun_fixed_target_plan(...):
yieldfrombpp.contingency_wrapper(
_run_fixed_target_plan(...), except_plan=run_aborted_plan(...), final_plan=tidy_up_plan(...)
)
deftidy_up_plan(..):
# Everything after the wait for the collection to finishdef_run_fixed_target_plan(...):
# Same as current plan up to when the collection is running then we just have the wait for it to finish
The text was updated successfully, but these errors were encountered:
The SSX scripts currently use
me14e_gp9
as a PV for whether we want to abort or not. The bluesky way of doing this is calling abort on the RE, this can be done through blueAPI usingblueapi abort
. We need to make sure that when the plan is aborted it correctly tidies up, we should do this with the contingency wrapper. We need to make sure the wrapper covers as much of the plan as possible so that if we get an abort when shutter is opening we properly close it. i.e. the chip collect will look something like:The text was updated successfully, but these errors were encountered: