Ticket #2450 (closed: worksforme)
Crash while running EQSANS from the HFIR_Reduction GUI
Reported by: | Brett Tully | Owned by: | Mathieu Doucet |
---|---|---|---|
Priority: | major | Milestone: | Iteration 28 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Whitty |
Description
System crashes with the following errors when running EQSANS from the HFIR_Reduction GUI in 1.1.9517 RHEL 5. Both situations should throw an error, but I wouldn't expect them to crash the GUI; when run via the automatically generated script in each case, the error is handled as you would expect.
Crash 1: Error printed to Bash command line -> "An error occurred while running EQSANSTransmission. See results log for details."
- Scattering data file: "...Test/Data/EQSANS_1466_event.nxs"
- Click reduce
- SOLVED by: using beam finder with data file: "...Test/Data/EQSANS_1466_event.nxs"
Crash 2: Error printed to Bash command line -> "An error occurred while running LoadSNSEventNexus. See results log for details."
- Scattering data file: "...Test/Data/SANS2D/SANS2D00002500.nxs"
- Click reduce
- No solution found, but when the same process is run from a script, the error is handled and Mantid does not crash.
Change History
comment:2 Changed 10 years ago by Nick Draper
- Owner set to Mathieu Doucet
- Status changed from new to assigned
comment:3 Changed 10 years ago by Mathieu Doucet
- Status changed from assigned to accepted
This ticket was created a while ago. Please tell the user to try with the latest version of MantidPlot. Crash 1 it now fixed (leaving the beam center to 0,0 will NOT produce meaningful results, but the reduction won't crash). Crash 2 is clear from the log in MantidPlot. EQSANS reduction needs event data. I may add a message to that effect.
comment:5 Changed 10 years ago by Mathieu Doucet
- Status changed from accepted to verify
- Resolution set to worksforme
comment:7 Changed 9 years ago by Michael Whitty
- Status changed from verify to verifying
- Tester set to Michael Whitty
I understand that these are incorrect data files for this interface, but we should handle the errors without crashing