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

Apply Corrections fails with old OSIRIS files #10562

Closed
mantid-builder opened this issue Jun 20, 2014 · 1 comment
Closed

Apply Corrections fails with old OSIRIS files #10562

mantid-builder opened this issue Jun 20, 2014 · 1 comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Milestone

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Samuel Jackson

Reported by Sanghamitra:

Today morning I tried to use ‘Use Can’ option available in IDA Apply Correction on Run 110041 (sample) and 103358 (can) (OSIRIS, Analyser: graphite, 002, mapping:All), but receive the following error:

Error in execution of algorithm Minus:

X arrays must match when performing this operation on a 2D workspaces.
ValueError: X arrays must match when performing this operation on a 2D workspaces.
at line 16 in '`<Interface>`'
caused by line 1302 in 'C:/MantidInstall/scripts/Inelastic\IndirectDataAnalysis.py'
caused by line 567 in 'C:/MantidInstall/bin\mantid\simpleapi.py'

This is because 103358 is an old run with a shorter range. Her suggestion is to rebin the can to the sample if the bins don't match and spit out a warning that it is doing so.

@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 9720

@mantid-builder mantid-builder added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.2 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Projects
None yet
Development

No branches or pull requests

1 participant