Ticket #4079 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Bad alloc when trying to open instrument view

Reported by: Owen Arnold Owned by: Roman Tolchenov
Priority: blocker Milestone: Release 2.0
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Peter Parker

Description

It's absolutely essential to recover this functionality.

Workspace is at
olympic\BABYLON5\Public\Owen Arnold\problem_workspace. When trying to open the instrument view, I get a bad alloc unexpected exception.

Change History

comment:1 Changed 9 years ago by Russell Taylor

Here's another way to get this problem (from Janik)....

Run this script:

LoadEventNexus(Filename=r'CNCS_7860_event.nxs',OutputWorkspace='cncs')
ConvertToMatrixWorkspace(InputWorkspace='cncs',OutputWorkspace='a')
Power('a', 'am1', -1)

Right-click on am1 workspace, select instrument view. You will get at bad_alloc error. I think it is related to the fact that there are "inf" values in the Y data.

comment:2 Changed 9 years ago by Owen Arnold

Following Russell/Janik's suggestion, I ran ReplaceSpecialValues algorithm prior to running the instrument view. After doing this, I was able to view the workspace in the instrument view. Roman, should try this out too.

If this is the cause of the problem, we would still need to fix the bad_alloc error and gracefully suggest to the user the course of action to follow to correct for special values.

comment:3 Changed 9 years ago by Roman Tolchenov

  • Status changed from new to accepted

comment:4 Changed 9 years ago by Roman Tolchenov

  • Status changed from accepted to verify
  • Resolution set to fixed

comment:5 Changed 9 years ago by Roman Tolchenov

Re #4079. Added some protection against infinites and NaNs

Changeset: 2be0df9b3c8cbb8790024268afa99b6419bd7ea3

comment:6 Changed 9 years ago by Peter Parker

  • Status changed from verify to verifying
  • Tester set to Peter Parker

comment:7 Changed 9 years ago by Peter Parker

  • Status changed from verifying to closed

Bad alloc no longer occurs when the script above is used - the user is now prompted to run ReplaceSpecialValues instead.

comment:8 Changed 9 years ago by Karl Palmen

This may have re-emerged in ticket #4440

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 4926

Note: See TracTickets for help on using tickets.