Skip to content
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

[defect] using erroneous mantid instrument information when generating sensitivity file with legacy data #23

Open
glass-ships opened this issue Dec 17, 2024 · 1 comment

Comments

@glass-ships
Copy link
Member

Problem Description:

When generating the sensitivity file the instrument xml in Mantid will be used erroneously.

Steps to Reproduce:

BioSANS_MainSens_XMLtoNXS_Template_Edited.ipynb

When generate the sensitivity file with this notebook script the generated file has different instrument geometry (pixel positions) to the original nexus file. This wrong geometry is imported from the default file in Mantid without confirming with the instrument scientist. This is an issue when the using legacy files for reduction or generating sensitivity files.

Investigation/Analysis Results:

In https://code.ornl.gov/sns-hfir-scse/sans/sans-backend/-/blob/next/drtsans/load.py#L148

If the option LoadNexusInstrumentXML is missing then the code will automatically load the Mantid default instrument xml.

While generating sensitivity correction files, this option is not specified so the nexus instrument xml will be omitted

https://code.ornl.gov/sns-hfir-scse/sans/sans-backend/-/blob/next/drtsans/prepare_sensivities_correction.py#L763

Which produces incompatible detector geometries (pixel positions) in resulting files.

An explicit option has to be added to this function call to enforce to copy the nexus instrument xml

@glass-ships
Copy link
Member Author

This issue was migrated from code.ornl.gov.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant