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
It should be easy to loop daq.begin to do simple data collection, then ctrl+c to exit the loop.
Current Behavior
ctrl+c is caught by daq.begin and then then loop enters the next phase too quickly to be stopped
Possible Solution
Add an option to begin for doing N runs or infinite runs and handle the interrupts all together within the class. So this would look something like "daq.begin(duration=600, wait=True, num_runs='inf')". The rationale is that this is a common enough thing to want to do, so maybe it should just be a built-in. We wouldn't need a separate "daq_repeat" function in the beamline file.
Add an option to begin for disabling the ctrl+c handling. E.g. "daq.begin(duration=600, wait=True, handle_interrupts=False)". This would let you handle interrupts yourself if doing something more complicated than a daq.begin loop.
The text was updated successfully, but these errors were encountered:
Expected Behavior
It should be easy to loop
daq.begin
to do simple data collection, then ctrl+c to exit the loop.Current Behavior
ctrl+c is caught by
daq.begin
and then then loop enters the next phase too quickly to be stoppedPossible Solution
The text was updated successfully, but these errors were encountered: