Create mfx_RE to wrap the daq.configure for scanning. #262
Description
Current Behavior
Currently we need to configure the daq, identify the scan motor, set the number of step, shots per step, bit mask before running a RE bluesky plan. Sometimes operators forget tod o this on sequential scans and the saved scan motor is incorrect.
Expected Behavior
The call to the new feature mfx_RE() should look identical to RE(but wrap the first daq.configure step with the correct parameters passed in the method.
Context / environment
In scenarios where we couldn't get an epics pv into the epics arch file and the scan had the wrong motor configured then we can never obtain the scanned motor values for that scan.
Suggested Solution
Def mfx_RE(bluesky_plan):
daq=bluesky_plan's daq object that is passed?
daq.configure(the stuff)
RE(bluesky_plan)
Usage:
mfx_RE(bp.daq_scan([daq],lxt,-1E-12,1E-12,21,120,record=True)