You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would cover the cases in the time-parameter report by @g5t and it would make a simple interface for downstream code using values from the log.
This would probably not need much changes, we already have the lookup method, and some wrappers around scipy.interpolate. It's mainly a question of putting it behind a uniform interface.
Executive summary
Instrument parameters are time dependent, this needs to be processed before, e.g., associating neutron events with parameter values
Context and background knowledge
Version 0.1 of summary written by @g5t:
time_parameter_report.pdf
Inputs
1-D
DataArray
, typically loaded from anNXlog
in a NeXus file.Methodology
To be determined for individual cases. See also attached PDF.
Outputs
Processed
DataArray
that can be used, e.g., with Scipp's event filtering.Which interfaces are required?
Python module / function
Test cases
Creating synthetic data is easy and a good start, but we should consider testing robustness on real data.
Comments
This is likely very generic functionality and may result in addition of basic tools in Scipp as well as ScippNeutron.
The text was updated successfully, but these errors were encountered: