Enable changing of wildes flipper config via the ISIS Reflectometry GUI#41353
Enable changing of wildes flipper config via the ISIS Reflectometry GUI#41353MialLewis wants to merge 6 commits into
Conversation
System test results810 tests 792 ✅ 2h 13m 52s ⏱️ Results for commit 0572532. |
|
👋 Hi, @MialLewis, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
0572532 to
4bb2aba
Compare
|
👋 Hi, @MialLewis, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
Unit test results (Linux)2 870 tests 2 869 ✅ 13h 41m 25s ⏱️ Results for commit 3c6cc3a. |
| </property> | ||
| <property name="text"> | ||
| <string>Fredrikze Input SpinState Order</string> | ||
| <string>Input SpinState Order</string> |
There was a problem hiding this comment.
I plan to change this to Input Flipper/SpinState order, I'll make the change when addressing review comments.
cailafinn
left a comment
There was a problem hiding this comment.
Functionally tested according to instructions, getting good error messages for wrong correction alg type (p,a vs 0, 1) and for numbers of spin states. But there is a slightly unexpected one for if the wrong form is used. E.g Wildes PNR & (00, 11):
Error in execution of algorithm ReflectometryISISLoadAndProcess:
Add Data Object with empty name
at line 111 in '/Users/caila.finn/repos/mantid-r/Framework/PythonInterface/plugins/algorithms/WorkflowAlgorithms/ReflectometryISISLoadAndProcess.py'
caused by line 656 in '/Users/caila.finn/repos/mantid-r/Framework/PythonInterface/plugins/algorithms/WorkflowAlgorithms/ReflectometryISISLoadAndProcess.py'
Just one note on the release note and the GUI change that you'd already spotted.
| - The ISIS Reflectometry GUI polarization input spin state order field can now be used to specify the Wildes flipper | ||
| configuration as well as the Fredrikze input spin state order. Leaving the field empty continues to use the defaults | ||
| from the instrument parameter file or correction algorithm. | ||
| - The reduction now reports when a Fredrikze spin state order is supplied for a Wildes correction, or a Wildes flipper | ||
| configuration is supplied for a Fredrikze correction. |
There was a problem hiding this comment.
Are there docs links we could be including here?
Good spot, I didn't consider this case |
3c6cc3a to
9966697
Compare
|
👋 Hi, @MialLewis, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
a8cc46f to
1473807
Compare
|
👋 Hi, @MialLewis, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
Improve polarization spin state validation refactor to utilise existing spin state validation Improve Fredrikze spin state count validation Refactor reflectometry polarization correction handling Address reflectometry polarization review comments
remove accidentally included test
1473807 to
b40613d
Compare
I didn't make a change with regards to this. It turns out that It has always been possible to encounter this error so it's not a regression, though one would have had to previously edit the parameters file. I'll need to discuss how this should behave in the context of the Polarised Reflectivity workflow with the Reflectometry scientists. Issue: #41469 |
db9333d to
aab892a
Compare
|
👋 Hi, @MialLewis, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
Description of work
SpinStateValidatorfor spin-state family validation. This is used to check if Wildes flipper config is being used for a Fredrikze correction and vice-versa.ReflectometryReductionOneAutoto a helper classReflectometryPolarizationCorrectionISISto aid readability.Closes #41041
To test:
Follow test instructions on this PR:
#38783
Ensure to test the different errors expected when you use Wildes correction for Fredriekze, 2 spin states inputs when 4 is expected etc.
Also test changing the defaults in the instrument parameter files, ensure those values are pulled through correctly.
To test a realistic polarised reduction:
Reviewer
Your comments will be used as part of the gatekeeper process. Comment clearly on what you have checked and tested during your review. Provide an audit trail for any changes requested.
As per the review guidelines:
mantid-developersormantid-contributorsteams, add a review commentrerun cito authorize/rerun the CIGatekeeper
As per the gatekeeping guidelines: