The current scan path extractor is broken for the current version of the HDF5 (core/hdf5_export_version: 9). Instead of a single scan path array, the different features of the array are broken up into different layer-wise datasets (scans/<parameter>/<layer>) that need to be merged and post-processed to be in a Myna-compatible format.
The Peregrine-generated HDF5 files should have a core/hdf5_export_version attributes (attrs) that could be used to govern which scan path extraction tool is used. This is something that could be considered moving forward, but probably not needed to support backwards compatibility for all versions unless requested.
The current scan path extractor is broken for the current version of the HDF5 (
core/hdf5_export_version: 9). Instead of a single scan path array, the different features of the array are broken up into different layer-wise datasets (scans/<parameter>/<layer>) that need to be merged and post-processed to be in a Myna-compatible format.The Peregrine-generated HDF5 files should have a
core/hdf5_export_versionattributes (attrs) that could be used to govern which scan path extraction tool is used. This is something that could be considered moving forward, but probably not needed to support backwards compatibility for all versions unless requested.