Latency scan failing some times
It has been reported that the latency scan fails sometimes even if the current version fo the code hads been tested and shown to work properly during the tests.
I wasn't able to reproduce the error, so please notify me in case it happens again.
Steps to reproduce
- get the latest version of the code
- start a latency scan with the desired parameters
- analyze the scan with the unpacker and the light dqm with this version
What is the expected correct behavior?
For example, the expected corrected behavior is for a scan between latency values of 10 and 30, step size of 1, pulse stretch for the singla of 7 (=8 bunch crossing).
- Version used: commit b6232b30