Ticket #7836 (closed: fixed)

Opened 7 years ago

Last modified 5 years ago

[IDA] SofQW workspace output name update

Reported by: Samuel Jackson Owned by: Samuel Jackson
Priority: major Milestone: Release 3.0
Component: Indirect Inelastic Keywords:
Cc: spencer.howells@… Blocked By:
Blocking: Tester: Jay Rainey

Description

New ticket from Spencer: 

To be consistent with usage in ApplyCorr, the *_red_q WS should be changed to *_rqw.
rwq signifying that it is reduced converted from (hist-number,w) to (q-elastic,w)  which is different to sqw.

Should be as simple as swapping what it's output as in the GUI/py code.

Change History

comment:1 Changed 7 years ago by Samuel Jackson

  • Summary changed from [IDA] ApplyCorrections workspace output name update to [IDA] SofQW workspace output name update

comment:2 Changed 7 years ago by Samuel Jackson

  • Status changed from new to inprogress

Refs #7836 Change output workspace name.

Changeset: 53a33dd39c8fa4caa958ab7b56f1149526d064bd

comment:3 Changed 7 years ago by Samuel Jackson

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

To Tester

Open up the C2E interface, select an indirect instrument and navigate to the S(Q,w) tab. Open any appropriate file (e.g. irs26173_graphite002_red.nxs in system tests). Click plot input. The generated workspace should be called *_rqw.nxs instead of *_red_q.nxs

comment:4 Changed 7 years ago by Samuel Jackson

  • Milestone changed from Backlog to Release 3.0

comment:5 Changed 7 years ago by Jay Rainey

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

comment:6 Changed 7 years ago by Jay Rainey

  • Status changed from verifying to closed

Merge remote-tracking branch 'origin/feature/7836_sofq_workspace_output'

Full changeset: ​06ea0804829ce5b7a4944c3e5c8effeb5dad2037

comment:7 Changed 7 years ago by Jay Rainey

Workspace name is now consistent with usage in ApplyCorr.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​8681

Note: See TracTickets for help on using tickets.