Ticket #7592 (closed: duplicate)

Opened 7 years ago

Last modified 5 years ago

SANS: Exception in automatic search

Reported by: Samuel Jackson Owned by: Gesner Passos
Priority: blocker Milestone: Release 3.0
Component: SANS Keywords:
Cc: Blocked By:
Blocking: Tester: Russell Taylor

Description (last modified by Samuel Jackson) (diff)

Running an automatic search causes a high level exception to the thrown:

Sorry, MantidPlot has caught an unexpected exception:

m_run is empty! for workspace Right_tmp

Reproduced using these configuration settings http://www.mantidproject.org/SANS_Data_Analysis_at_ISIS running a 1D reduction, then going to geometry > Run automatic search.

Could possibly be related to the change in Python API.

Change History

comment:1 Changed 7 years ago by Samuel Jackson

  • Description modified (diff)

comment:2 Changed 7 years ago by Gesner Passos

  • Keywords PatchCandidate added
  • Owner set to Gesner Passos
  • Milestone changed from Backlog to Release 3.0

comment:3 Changed 7 years ago by Gesner Passos

  • Priority changed from major to blocker

comment:4 Changed 7 years ago by Gesner Passos

Reported also by Stephen:

Mantid 2.5.1627-g2b4792b, Wed 24 Jul

Whilst running beam centre search on LOQ main detector data:

‘m_run is empty for workspace_right’ ‘Do you wish to terminate or continue’

Choose continue and Mantid continues.

It eventually found what appeared to be a good solution, but what is this message about?

Sample runs: 79650 79652 79654 Can runs: 79651 79653 79654

(I perhaps should add that these runs are the first to use the new live display on LOQ, so they have more spectra and time regimes than the data we have hitherto been reducing… though the detector to spectra mapping SHOULD be the same).

Steve

comment:5 Changed 7 years ago by Gesner Passos

  • Status changed from new to inprogress

comment:6 Changed 7 years ago by Gesner Passos

  • Keywords PatchCandidate removed
  • Status changed from inprogress to verify
  • Resolution set to duplicate

It turned out that it was a more generic problem which has been fixed inside #7583

comment:7 Changed 7 years ago by Russell Taylor

  • Status changed from verify to verifying
  • Tester set to Russell Taylor

comment:8 Changed 7 years ago by Russell Taylor

  • Status changed from verifying to closed

Yes, that has been fixed.

Last edited 7 years ago by Russell Taylor (previous) (diff)

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 8437

Note: See TracTickets for help on using tickets.