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

Output workspace group created when an algorithm failed #11570

Closed
raquelalvarezbanos opened this issue Dec 9, 2014 · 3 comments
Closed

Output workspace group created when an algorithm failed #11570

raquelalvarezbanos opened this issue Dec 9, 2014 · 3 comments
Labels
Framework Issues and pull requests related to components in the Framework
Milestone
Release 3.7

Comments

@raquelalvarezbanos
Copy link
Contributor

This issue was originally TRAC 10728

When an algorithm fails to run on a workspace group, the output workspace group is created. It is empty and you cannot delete it. If you go to "Details" the algorithm is still running, and when you try to close mantid, it does not respond.

I tried the following:

  • Load MUSR00015189
  • Run ApplyDeadTimeCorr providing an empty table workspace as DeadTimeTable

Also tried:

  • Load MUSR00015189
  • Run PhaseQuad providing only InputWorkspace and OutputWorkspace
@raquelalvarezbanos
Copy link
Contributor Author

@NickDraper (2015-04-27T08:10:35):
Moved to R3.5 at the R3.4 code freeze

@raquelalvarezbanos raquelalvarezbanos added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@raquelalvarezbanos raquelalvarezbanos added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper
Copy link
Contributor

Neither of the two examples cause a failure in R3.6

@NickDraper
Copy link
Contributor

works4me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework Issues and pull requests related to components in the Framework
Projects
None yet
Milestone
Release 3.7
Development

No branches or pull requests
2 participants
@NickDraper @raquelalvarezbanos