Acquisition object for continuous acquisition

[sk1p]

• Two cases, one that repeats a 2D scan, and one that just runs the udf on whatever data currently hits the detector (represented as an infinite 1D nav), without pre-defined number of frames
• Repeated 2D:
  • Depends on the synchronization; in some setups it needs to re-trigger after each scan (per-dataset trigger), in others, it can just run continuously (pixel trigger)
  • For nav plots, allow both "fresh plot each scan" and "overwrite partial results" plotting
• Infinite 1d nav:
  • we can still support kind=nav results, but we need to handle the plotting and buffer allocation differently
  • maybe allow to use a ring buffer for this case?
  • plot nav results as a line? maybe limited in horizontal direction, to plot the last N points?
  • could also do custom plots, like quantities derives from CoM

[uellue]

This would be important for the Dectris setup at KIT, since the acquisition is started manually. Continuous processing would be important for live monitoring.

[sk1p]

This would be important for the Dectris setup at KIT, since the acquisition is started manually. Continuous processing would be important for live monitoring.

As DECTRIS doesn't have a real contrinuous mode, we can emulate this using a very high value (~2000000000?) for nimage / ntrigger and canceling when we are done.

Repeated 2D: (...)

Would be nice to have a history of results, too, as we had at our last experiment: for example, with a slider over the time axis (if possible, having the slider responsive even while the acquisition is running, and not just "doing events" once per scan)