Closed callumforrester closed 3 months ago
how would this testing go then?
We would simply run the plan with appropriate parameters such that the panda will trigger the pilatus(es) as fast as they can go, according to their specifications (exact speed TBC with the beamline).
This has required us to correct ophyd-async's understanding of the pilatus' readout time: https://github.com/bluesky/ophyd-async/pull/359
So that change should be released and we should wait until the beamline is available again, then this work can go ahead.
Detector stalling issues should be fixed by: https://github.com/bluesky/ophyd-async/pull/401
As a user I would like assurance that the stopflow plan can reliably work at the max. framerate of the pilatuses.
This depends on https://github.com/bluesky/ophyd-async/issues/355
Exact test parameters to be defined:
Acceptance Criteria