All 3 electron analyser implementations, Mbs, Specs, and VGScienta, all now use StandardDetector after the 0.17 ophyd-async detector rewrite.
The idea behind StandardDetector is that small data, e.g config metadata is stored with the run documents. Large datasets are written to file via the HDF plugin in epics area detector and the run documents provide a link to this file. This is a departure from how these detectors currently operate within GDA as they handle all of the data writing directly in the nexus file.
The Mbs detector will be the simplest to add, as it will require only one hdf file plugin as it will only support one region.
Specs and VGScienta will be more complicated, as they require multiple regions per data point. The proposed solution is to assign a data writer per region. A custom data logic class will need to be created for these detectors to manage multiple HDF plugins.
All 3 electron analyser implementations, Mbs, Specs, and VGScienta, all now use
StandardDetectorafter the 0.17 ophyd-async detector rewrite.The idea behind StandardDetector is that small data, e.g config metadata is stored with the run documents. Large datasets are written to file via the HDF plugin in epics area detector and the run documents provide a link to this file. This is a departure from how these detectors currently operate within GDA as they handle all of the data writing directly in the nexus file.
The Mbs detector will be the simplest to add, as it will require only one hdf file plugin as it will only support one region.
Specs and VGScienta will be more complicated, as they require multiple regions per data point. The proposed solution is to assign a data writer per region. A custom data logic class will need to be created for these detectors to manage multiple HDF plugins.