-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add standard handling for half-polarized beam #148
Comments
Apparently the folks at ISIS are also frequently loading + as ++ and - as -- |
Kirby pointed out that sometimes you'll want to do something more subtle, like an incoherent sum of SF and NSF, assuming that the SF channel is being measured correctly for that geometry (that Zeeman splitting < resolution). |
There are two SF channels. Which one is added will depend on whether the spin selector is before or after the sample. Maybe a mnemonic such as ?+ or +? to distinguish. |
But what would we do in load4 and PolarizedNeutronProbe with the |
Sure, we can do the same until we refactor the handling of polarized beam, which we need to do at some point. I'm suggesting that reduction should record whether the half-polarized beam is front or back polarized for those samples which exhibit splitting in the spin flip channel and those programs that can handle it. |
Leaving aside for the moment whether we should include more information from the reduction (I agree, this is a good idea), what should refl1d do with half-polarized data? That is the essence of the ticket. I think most people will want to treat it as |
This is the easier approach. I suspect most people want to treat it as I suggest treating it as Note that sasview lets you fit the measurement without polarization correction by having mixing terms as part of the model. I don't think we want to go there. |
There is an issue with adding in the SF channels - they don't line up on the NSF channels when the field is non-zero (Zeeman splitting). In this sense SANS has an easier time of it because they can mix spin channels all over the detector (nothing gets lost when it shifts in angle) |
I don't understand. If the Zeeman effect is captured in the model then it can be mixed before comparing with the data. If it is not captured in the model then it needs to be a correction in the reduction and I don't see it there. |
The Zeeman effect makes SF scatter at a different angle, so it might not make it into the detector if the shift is big enough compared to the acceptance. |
If we make the assumption that all the scattering is captured in half-polarized mode, it should be possible to polarization-correct the measured I+ and I-, extracting the sums Here is the result: this was calculated by taking inverses of the matrices defined in Eq. 4a from Wildes, setting |
On CANDOR we will be measuring without an analyzer for a while. Many files will have polarization =
+
or-
instead of++
and--
load4 does not work for these files (throws an exception) because it is expecting only pairs from the full 4 cross-sections.
We should work out what the standard handling for half-polarized files will be (up-convert to
++
and--
?), instead of forcing users to manually edit .refl files to change the polarization in the header.The text was updated successfully, but these errors were encountered: