Processing-friendly HDF5 master file structure #1130
Replies: 1 comment
-
An example of the problems with multi-trigger mode is seen with a dataset collected in June 2024 at id30b:
The omega angles in the metadata are as follows:
There are two things wrong with this:
IIUC the metadata should be as follows:
At Soleil, the omega angles are fixed up after collection using an h5py script: https://github.com/MartinSavko/experimental_methods/blob/8b9e9a9d38baad413ee5306f2ed9a74987f9277e/reference_images.py#L273 Other workarounds are of course possible, but in an ideal world the metadata would be correct in the HDF5 metadata as first written. @marcus-oscarsson has confirmed verbally that at the time of writing it is not known what the omega angles would be if this data collection were to be repeated at id30b now. Max Burian at DECTRIS is aware in general terms that there are issues in this area with HDF5, and we at GPhL plan to raise them with him and Sofia Trampari in the follow-up initiative to HDRMX started by Graeme Winter. |
Beta Was this translation helpful? Give feedback.
-
Updating this with some comments from @pkeller (thanks :) ), who suggested:
Discussions about HDF5 master file structure and metadata for complex data collections. Examples include:
characterisation data collected in multi-trigger mode
wavelength-interleaved and inverse beam data collections
Beta Was this translation helpful? Give feedback.
All reactions