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.

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

Unexpected behaviour when using new-style syntax in live python script #8853

Closed
mantid-builder opened this issue Sep 23, 2013 · 2 comments
Closed
Labels
Framework Issues and pull requests related to components in the Framework

Comments

@mantid-builder
Copy link
Collaborator

This issue was originally TRAC 8008

Original Reporter: Russell Taylor

For example, if I use the following simple script as a Processing Step in StartLiveData (with no post-processing), I end up with 2 workspaces added to the ADS. One with the name I asked for in the Output Workspace property and also one called "output"

As an added bonus, if PreserveEvents is checked (and you have events in the first place) MantidPlot will crash on the second time around (inside the Plus algorithm).

This was found while testing http://trac.mantidproject.org/mantid/ticket/7019, but was a pre-existing problem.


Keywords: LiveData

@mantid-builder
Copy link
Collaborator Author

@NickDraper (2014-02-14T11:05:00):
Bulk move to assigned at the introduction of the triage step

@mantid-builder mantid-builder added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@NickDraper
Copy link
Contributor

archived

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

No branches or pull requests

2 participants