Do not restart scan from scratch after re-configuration
Currently, the calibration scans (i.e. the latency scan) restart from stracth when the GEM system is re-configured (green recycled). Such operation can happen semi-regularly and shouldn't prevent very long scans to be taken.
What is the expected correct behavior?
After re-configuration, the scan restarts from the last scan point.
The current scan point is stored in the
scanCurrent could replace
scanMin) instead of a local variable reset at the configuration transition. Therefore, the workflow could be the following:
- The calibration suite sends data for the next scan to be taken;
- The managed applications store a copy of
xdata::Bagand update it when needed;
- No local variables are being used to track down the current state of the scan.
Particular attention must be paid to never skip a data point. Measuring twice a data point is a minor (or unavoidable issue).