The workflows ess.reduce.nexus use providers that setup, e.g., NeXusMonitorLocationSpec with a PulseSelection. This is however only needed when loading the nested event data. As both, loading the monitor and loading the event data` use the same location spec the former depends on the latter.
This causes several problems, such as re-loading static monitor- and detector-info when PulseSelection is changed.
The workflows
ess.reduce.nexus
use providers that setup, e.g.,NeXusMonitorLocationSpec
with aPulseSelection
. This is however only needed when loading the nested event data. As both, loading the monitor and loading the event data` use the same location spec the former depends on the latter.This causes several problems, such as re-loading static monitor- and detector-info when
PulseSelection
is changed.