Ticket #7589 (assigned)
SANS: Throws bad alloc when running 2D reduce
Reported by: | Samuel Jackson | Owned by: | Peter Parker |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | SANS | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Samuel Jackson) (diff)
SANS throws a bad alloc error when running a 2D reduce on a call to the Fit algorithm.
The following output is displayed:
Error in execution of algorithm Fit: std::bad_alloc MemoryError: at line 35 in '<Interface>' caused by line 440 in '/opt/Mantid/scripts/SANS/ISISCommandInterface.py' caused by line 570 in '/opt/Mantid/scripts/SANS/ISISCommandInterface.py' caused by line 206 in '/opt/Mantid/bin/mantid/simpleapi.py'
Can be reproduced by following instructions at http://www.mantidproject.org/SANS_Data_Analysis_at_ISIS
Attachments
Change History
Changed 7 years ago by Gesner Passos
- Attachment MaskFile.txt added
Input that cause the exception to be seen.
comment:3 Changed 7 years ago by Gesner Passos
- Priority changed from blocker to major
- Milestone changed from Release 2.6 to Backlog
In reality, looking more into the details, the inputs were wrong. The range when performing REDUCE2D is from -0.1 to 0.1. So, when it tries to ask Fit to fit against an interval from 0.13 till 0.25 it fails.
The exception could be more graciously presented from Fit algorithm (checking that the limits are valid is a good sanity check), and could be avoided from the SANS interface as well.
But, the good news is that this but was not introduced in this release (reason for asking to be configure as blocking for release 2.6). We can deal with it later.
comment:4 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step