DAQControlMainz issueshttps://gitlab.rlp.net/alaudrai/DAQControlMainz/-/issues2021-02-09T19:41:22+01:00https://gitlab.rlp.net/alaudrai/DAQControlMainz/-/issues/7MSO DAQ: sequence acquisition stuck at 0 events2021-02-09T19:41:22+01:00Laudrain, AntoineMSO DAQ: sequence acquisition stuck at 0 eventsAfter a few runs, the sequence acquisition is stuck and does not record events anymore.
- [0s]: 0 events recorded
- [5s]: 0 events recorded
- [10s]: 0 events recorded
- ...After a few runs, the sequence acquisition is stuck and does not record events anymore.
- [0s]: 0 events recorded
- [5s]: 0 events recorded
- [10s]: 0 events recorded
- ...Laudrain, AntoineLaudrain, Antoinehttps://gitlab.rlp.net/alaudrai/DAQControlMainz/-/issues/6MSO DAQ: event memory resets after first polling2021-02-09T19:38:30+01:00Laudrain, AntoineMSO DAQ: event memory resets after first pollingWhen running in sequenced acquisition, the code regularly polls the scope to know how many events have been recorded yet (when complete, the segmented memory is readout and transferred to the computer).
Issue: after the first poll actio...When running in sequenced acquisition, the code regularly polls the scope to know how many events have been recorded yet (when complete, the segmented memory is readout and transferred to the computer).
Issue: after the first poll action, the segmented memory resets and the acquisition starts again normally.
For example, if the number of requested events per run is 5000, the trigger rate is about 100 Hz and the polling period is 5 seconds, the following occurs:
- [0s]: 0 events recorded
- [5s]: 500 events recorded (here immediately after it resets)
- [10s]: 500 events recorded (again! we expected 1000 here)
- [15s]: 1000 events recorded
- [20s]: 1500 events recorded
- [25s]: ...Laudrain, AntoineLaudrain, Antoinehttps://gitlab.rlp.net/alaudrai/DAQControlMainz/-/issues/2Check status code for each command / throw exceptions2020-08-26T22:54:03+02:00Laudrain, AntoineCheck status code for each command / throw exceptionsCurrently the read commands return a struct with return status code + value.
The code does not currently checks for these status codes before retrieving the value.
Another possibility would be to throw exceptions.Currently the read commands return a struct with return status code + value.
The code does not currently checks for these status codes before retrieving the value.
Another possibility would be to throw exceptions.