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

LoadNXSPE #12553

Closed
OwenArnold opened this issue May 7, 2015 · 2 comments
Closed

LoadNXSPE #12553

OwenArnold opened this issue May 7, 2015 · 2 comments
Assignees
@KarlPalmen
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Vates
Milestone
Release 3.5

Comments

@OwenArnold
Copy link
Contributor

This issue was originally TRAC 11715

For most load algorithms, the load offers to fill in the name of the output workspace from the filename. However for LoadNXSPE you have to fill it in yourself when opening the algorithm in MantidPlot. This should be fixed.

Keywords: vates
@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. GUI Vates labels Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 3.5 milestone Jun 3, 2015
@KarlPalmen
Copy link
Contributor

When I loaded (via load) the NXSPE file used to test LoadNXSPE in its unit test I found the output workspace filled in as with other algorithm.

However I've found that if one runs a load algorithm (such as LoadNexus) directly one does have to fill in the output workspace.

@KarlPalmen
Copy link
Contributor

Closed after chat with @OwenArnold .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KarlPalmen KarlPalmen

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

No branches or pull requests
2 participants
@OwenArnold @KarlPalmen