For screening images from EIGER detectors this may not be the case, as a single .h5 file may contain e.g. 3 images as 0, 45, 90, which should be interpreted as 3 scans separated by 45 degrees, i.e. 1 file -> 3 scan objects.
E.g. /dls/i04/data/2018/cm19645-5/Eiger/screening/SeThaumatin_8_1_hacked_master.h5
As far as I can tell there is a fundamental assumption in dxtbx of no more than one scan per input file:
https://github.com/cctbx/cctbx_project/blob/cc0cfc8ea0d3a8b1a230feac88b2226163695f62/dxtbx/datablock.py#L520-L533
For screening images from EIGER detectors this may not be the case, as a single .h5 file may contain e.g. 3 images as 0, 45, 90, which should be interpreted as 3 scans separated by 45 degrees, i.e. 1 file -> 3 scan objects.
E.g. /dls/i04/data/2018/cm19645-5/Eiger/screening/SeThaumatin_8_1_hacked_master.h5