You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a useTimeSlice flag designed for BioSANS, when it is turned on the results will be sliced based on the number specified by the timeSliceInterval keyword. But when the useTimeSlice flag is off, and both scattering and empty transmission samples are specified independently, the transmission calculation is way off.
This useTimeSlice feature are only available in QA branch.
Steps to Reproduce:
In BioSANS data reduction scripts, when the scattering and transmission are collected separately, the final results are way off in QA compared to production. As can be seen in this picture
This result can be reproduced in Jupyter notebook. The differences with QA kernel can be viewed by comparing QA and production runs RC490_IPTS24666_15m
Transmission and Scattering are measured as separate exposures.
Scattering (called samples) list and transmission (called samples_trans) list are different.
Reduced data from Production and QA (and Dev) are very different.
Transmission co-efficients for 18Å neutrons calculated in Production and QA environments are very different. It seems scattering data is also used to calculate transmission.
Transmission Co-efficients are ~0.000122% for sample (AgBeh 2mm) and ~97% for empty cell (background).
Data obtained from SANS environment is correct and expected result including the transmission value (RC490_IPTS24666_15m18A_Prod.ipynb) – (red curve in figure).
Data from QA environment has the issue- Transmission values are off! (RC490_IPTS24666_15m18A_QA.ipynb) – (blue curve in figure).
Data from switched lists between scattering and transmission because it seemed like transmission was being calculated using scattering data gave correct transmission values but the curve did not sit correctly on absolute scale with data from SANS environment (RC490_IPTS24666_15m18A_QA_ScatTransSwitched.ipynb) – (green curve in figure).
Data by making scattering and transmission to be identical lists gave the same result as if we have two different lists but the scattering list is used to calculate transmission and scattering!
It can be seen from the code that when scattering and empty transmission are measured independently and the userTimeSlice option is off, the function _prepare_sample_transmission_ws will be executed twice.
The text was updated successfully, but these errors were encountered:
Problem Description:
There is a useTimeSlice flag designed for BioSANS, when it is turned on the results will be sliced based on the number specified by the timeSliceInterval keyword. But when the useTimeSlice flag is off, and both scattering and empty transmission samples are specified independently, the transmission calculation is way off.
This useTimeSlice feature are only available in QA branch.
Steps to Reproduce:
In BioSANS data reduction scripts, when the scattering and transmission are collected separately, the final results are way off in QA compared to production. As can be seen in this picture
This result can be reproduced in Jupyter notebook. The differences with QA kernel can be viewed by comparing QA and production runs
RC490_IPTS24666_15m
(RC490_IPTS24666_15m18A_QA_ScatTransMadeSame.ipynb)
Investigation/Analysis Results:
The code that caused this error is in sans-backend/drtsans/mono/biosans/api.py from line 947 to 974
drtsans.mono.biosans.api
It can be seen from the code that when scattering and empty transmission are measured independently and the userTimeSlice option is off, the function
_prepare_sample_transmission_ws
will be executed twice.The text was updated successfully, but these errors were encountered: