Algorithm required for interpolating the efficiency wavelength dependence

[rbauststfc]

An algorithm is required that can interpolate the wavelength dependence for the analyser, flipper and polariser efficiencies. This is needed because the wavelength range of the experiment measurement may be different to the calibration measurements that were used to calculate the efficiencies.

Dirk has commented on this as follows:

It is necessary to make polarisation-analysis on TOF practically feasible without wasting too much time on calibration runs. It helps to reduce propagating excessive noise throughout the data correction. One could interpolate the data to reduce uncertainties. Using the known analytical equation gives an extra layer for checking if results are sensible just looking on the extracted parameters.

We believe that the existing InterpolatingRebin algorithm may be sufficient (and is acceptable for the MVP), however it may not be appropriate long-term because it uses cubic splines. It may be necessary for us to create a more sophisticated interpolation algorithm to use instead.

This interpolation step should be a standalone step at appropriate places in the wrapper workflow algorithm.

This is required for the Polarised SANS reduction at ISIS. Requirements still need to be gathered.

[dehoni]

The efficiency of the incoming optical components polarizer and flipper will be known from tabulated values. An algorithm is needed to get these values from calibration measurements (straightforward linear combination and ratios of spin-resolved transmission measurements).
The only particular part is the 3He cell. As part of characterising its performance, calculate the “mean gas length” based on two transmission measurements (depolarisedcell, directbeam). In contrast to opacity=gas_length*wavelength the gas length is an intrinsic quantity independent of wavelength, such that one can extract an averaged quantity over the considered wavelength band to improve statistical significance.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.