Currently the loaders for NXmonitor and NXdetector load also the source and sample. As we are loading each individually (and also intend to support chunking) this can become very inefficient. Aside from loading (and discarding) potentially large data in NXsample and NXsource (which could be avoided), there is also duplicate file navigation and access, which can be slow.
I think we should load source and sample positions when loading the non-monitor/detector data and merge them into the data later.
As with #109, I think we should consider doing this in ESSreduce.
Currently the loaders for NXmonitor and NXdetector load also the source and sample. As we are loading each individually (and also intend to support chunking) this can become very inefficient. Aside from loading (and discarding) potentially large data in NXsample and NXsource (which could be avoided), there is also duplicate file navigation and access, which can be slow.
I think we should load source and sample positions when loading the non-monitor/detector data and merge them into the data later.
As with #109, I think we should consider doing this in ESSreduce.