Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RenameWorkspace/GroupWorkspace not working #6848

Closed
Anders-Markvardsen opened this issue Oct 24, 2012 · 1 comment
Closed

RenameWorkspace/GroupWorkspace not working #6848

Anders-Markvardsen opened this issue Oct 24, 2012 · 1 comment
Assignees
@mantid-roman
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Release 2.3

Comments

@Anders-Markvardsen
Copy link
Member

This ticket is blocks : TRAC5666

Update code to include http://trac.mantidproject.org/mantid/ticket/5666 commit just pushed

  1. Open MuonAnalysis interface

  2. Hit browse button and load AutoTestData/MUSR00015189.nxs

  3. Optionally close down MuonAnalysis interface + plot it created

  4. Note that the WorkspaceGroup MUSR00015189 contain two workspaces:

MUSR00015189; Group=long; Asym; http://trac.mantidproject.org/mantid/ticket/1_1

MUSR00015189; Group=long; Asym; http://trac.mantidproject.org/mantid/ticket/1_2

  1. Try to rename one of these workspaces. Excute RenameWorkspace, where e.g. use

InputWorkspace: MUSR00015189; Group=long; Asym; http://trac.mantidproject.org/mantid/ticket/1_1

OutputWorkspace: pain

  1. Note that wrongly the new 'pain' workspace is placed OUTSIDE the WorkspaceGroup MUSR00015189.

  2. The correct behaviour of RenameWorkspace is not to move a workspace out of a WorkspaceGroup. For sanity you can test this by running RenameWorkspace with

InputWorkspace: MuoneAnalysis_1

OutputWorkspace: pain2

  1. This bug may be the reason why I can't subsequently get GroupWorkspace to work at all subsequently
@Anders-Markvardsen
Copy link
Member Author

This issue was originally trac ticket 6002

@Anders-Markvardsen Anders-Markvardsen added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@Anders-Markvardsen Anders-Markvardsen added this to the Release 2.3 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mantid-roman mantid-roman

Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Milestone
Release 2.3
Development

No branches or pull requests
2 participants
@mantid-roman @Anders-Markvardsen