sleep_time in scans
At the moment, there is a sleep_time
argument for standard scans (step by step).
The sleep time happens after motor moves, before counting, in the SoftwareTimerMaster
code. All standard scans have a SoftwareTimerMaster
.
Questions:
- what do you use
sleep_time
for ?-
- is it to define an acquisition period ?
-
- is it to provide "stabilization" time for some motors ?
-
Case 1: I guess it is only valid for time scans only ?
Case 2: in this case, I think it is better if we provide a StabilizationHook
for motors => could be configured in yml file, with a distinguish between "stabilization time in a scan" or not
Would it be ok to remove sleep_time
from all scans except timescan
, loopscan
?
For scans requiring stabilization we can do better with the proposed StabilizationHook
.
Should we change sleep_time
to period
?