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
Algorithm required to calculate the efficiency of the ISIS SANS spin flipper #36144
Comments
There is only one algorithm to determine the efficiency of a flipper on the incoming instrument site. We will take care that we expose a variable that shows if the instrument is in a flipper on/off state via a block in IBEX. The efficiency is calculated by simple linear combination and ratios of worksheets. The function takes 4 (monitor) worksheets normalised to incidence flux, nfs1/2 and sf1/2 are the for spin-resolved measurements. def calculate_beam_polarisation(strname): |
Windows' compiler doesn't seem to want to automatically do the conversion from std::filesystem::path to string the way that mac and linux do. So just do it explicitly. RE mantidproject#36144
Windows' compiler doesn't seem to want to automatically do the conversion from std::filesystem::path to string the way that mac and linux do. So just do it explicitly. RE mantidproject#36144
An algorithm is required to calculate the efficiency of the two spin flippers. This is required for the Polarised SANS reduction at ISIS. Calculating the efficiency of just one of the spin flippers is required for the epic MVP, as SANS are currently only using a single flipper in their setup. They would like the flexibility to support two in the future, though, so the full scope implementation will calculate the efficiency of two flippers.
The algorithm will be used in advance as part of commissioning, rather than calculating the flipper efficiency during the normal polarised SANS reduction workflow. A calibration measurement will be taken and the algorithm will be used to calculate the flipper efficiency and save the result as a Nexus file. This is not expected to vary between experiments, so the file can ultimately be read into the reduction workflow from the user file.
Math
Ixx
represents the configuration of the flipper.Polarisation:
Efficiency:
This applies if there is only one flipper, according to Wildes 2006.
Workflow
Requirements for this still need to be gathered.
The text was updated successfully, but these errors were encountered: