...

• make sure to return correct "status" objects from appropriate methods
• try not to block: start a start a subprocess, and return a "future" status
• if we return correct status, then don't have to do future stuff: gets handled by bluesky
• obscure: not clear exactly what configure should do

Interaction with DAQ

Results of a conversation with Chris F. and Matt on 12 Jun 2020 

4 ways for scans to interact with the daq:

• tell the daq to take, e.g., 1000 events with readout group 4 (not counting events with dead time)
• launch a sequence (more complex than the above but, in some sense, a special case)
• free-run until a user-defined drp trigger count (from the teb) is met
• free-run until a user-defined ami condition is met.  only suitable for low-rate expts where all events can be monitored, but easier and more flexible than the drp-trigger-count method above

All 4 mechanisms will indicate completion via EPICS variables.  We will try to get the EPICS variables to behave in the same fashion to make it more uniform for the BlueSky script.