Ticket #7828 (closed: fixed)

Opened 7 years ago

Last modified 5 years ago

EQSANS: issue with running reduction twice

Reported by: Mathieu Doucet Owned by: Mathieu Doucet
Priority: major Milestone: Release 3.0
Component: SANS Keywords: PatchCandidate
Cc: Blocked By:
Blocking: Tester: Russell Taylor

Description

A recent feature added to the EQSANS reduction is the ability to use an event workspace as the input of the reduction instead of a file. This causes a problem when a run number is used as the data input. The reduction then loads the file and calls the workspace by the run number. If you hit reduce a second time it will try to reload that workspace, which will make the reduction fail.

The logic that looks for a workspace should be updated to check that the given workspace not only exists but is an event workspace that was not already reduced.

Change History

comment:1 Changed 7 years ago by Mathieu Doucet

  • Status changed from new to inprogress

Re #7828 Add event workspace check

Changeset: 0ea89b1efefee0db73033566ed7f2d8f71c38d1f

comment:2 Changed 7 years ago by Mathieu Doucet

  • Status changed from inprogress to verify
  • Resolution set to fixed
  • Milestone changed from Backlog to Release 3.0

To test:

  • In the MantidPlot options, set SNS/EQSANS as your default instrument.
  • Make sure the systemtests Data directory is in the list of your Mantid data directories.
  • From MantidPlot's Interfaces menu, start the ORNL SANS UI.
  • If the EQSANS reduction UI doesn't start, go under Tools of the UI that just popped up and pick Change instrument: then pick EQSANS.
  • Under Tools of the EQSANS UI, make sure to turn on debug mode.
  • Fill in reduction options:
    • Enter only a run number (use 3293) in the scattering data file field of the Data tab.
    • Under the Transmission section of the same tab, click the Fix transmission box and enter 1 for the transmission value.
  • Hit reduce, the reduction should complete and a workspace with the run number as a name should appear.
  • Hit reduce again. The reduction should run again to completion, without error. The results should be the same.
Last edited 7 years ago by Mathieu Doucet (previous) (diff)

comment:3 Changed 7 years ago by Jay Rainey

  • Status changed from verify to verifying
  • Tester set to Jay Rainey

comment:4 Changed 7 years ago by Jay Rainey

  • Status changed from verifying to reopened
  • Resolution fixed deleted

I wasn't exactly sure which files to use in order to test. If possible could one of the SNS guys write a short guide on how to use the EQSANS reduction interface?

comment:5 Changed 7 years ago by Mathieu Doucet

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

I've updated the testing instructions above (comment:2).

comment:6 Changed 7 years ago by Mathieu Doucet

  • Tester Jay Rainey deleted

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

Merge remote branch 'origin/feature/7828_fix_repeated_eqsans_reduction'

comment:9 Changed 7 years ago by Nick Draper

  • Component changed from Framework to SANS

comment:10 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 8673

Note: See TracTickets for help on using tickets.