ReflectometryReductionOne should correct positions #10027
Labels
High Priority
An issue or pull request that if not addressed is severe enough to postponse a release.
Reflectometry
Issues and pull requests related to reflectometry
Milestone
This ticket is blocked by :
This is a simple principle: If you have known incident theta angle, and a reflection condition, i.e. theta_in == theta_out, then you can correct the detector positions accordingly.
I've avoided this problem so far, because for the multi-detector case you may have a number of 'masked' pixels, in which case there is no easily identifiable vertical centre position.
Having had a chat with Tim about this, we've agreed that if you have a range of pixels in the processing instructions, you should find the centre location and use that, along with the theta position to correct location. Corrections should still be optional.
Changes should apply to ReflectometryReductionOne, ReflectometryReductionOneAuto, CreateTransmissionWorkspace and CreateTransmissionWorkspaceAuto.
As part of this. We should also update ReflectometryReductionOne (following http://trac.mantidproject.org/mantid/ticket/9401) to calculate The OuptutTheta value if Multiple Spectrum numbers are given instead of component names.
The text was updated successfully, but these errors were encountered: