Storage of inverse-beam / interleaved data sets in NXmx format #1
Description
At the moment most data sets recorded from an Eiger in HDF5 / NeXus format take the form of a single scan - one arm, one trigger, one master and one or more data files, which is fine. For inverse beam data sets would want to have one arm but multiple triggers (one per wedge) but then also need to record additional metadata to allow the analysis software to know that this is what happened.
This would give data of the structure:
[A0-A199][B0-B199][A200-A399][B200-399]
etc.
Clearly one could use virtual data sets where the logical frames are indexed from within a larger block to give /data/A and /data/B or similar but would need to be something which works gracefully with xia2 / DIALS / XDS / autoPROC / fast_dp etc.
Discussion topic: how best to address this? Here at Diamond VDS seems like a straightforward solution but I can see this being difficult for others.