-
Notifications
You must be signed in to change notification settings - Fork 128
Stop hidden workspaces leaking to ADS during LoadAndMerge
algorithm if run as child
#39214
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
Conversation
LoadAndMerge
algorithmLoadAndMerge
algorithm if run as child
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is working fine, temporary workspaces are not stuck in the ads anymore.
Just found a typo otherwise looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a quick couple of things to ask before merging:
docs/source/release/v6.13.0/Framework/Algorithms/Bugfixes/39041.rst
Outdated
Show resolved
Hide resolved
3b9f363
to
a2bde87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This now looks good to me. Nice fix
… if run as child (#39214) * remove output workspaces from ads if child alg * expose getAlwaysStoreInADS to fix PolDiffILLReduction * add unit tests for LoadAndMerge ADS behaviour * respond to review comments
Description of work
Summary of work
This PR ensures that the
LoadAndMerge
algorithm does not output workspaces to the ADS if run as a child algorithm, or theStoreInADS
keyword set to equalFalse
.This behaviour was causing issues in algorithms down the line where hidden workspaces were being created in the ADS unexpectedly, contrary to specification.
To do this, I have exposed
getAlwaysStoreInADS
to python, and simply remove output workspaces from the ADS at the end of the algorithm. In the short term this is preferable to making changes toMergeRuns
which would in all likelihood require more widespread changes to other algorithms. See: https://github.com/mantidproject/mantid/pull/39214/files#diff-a2152741e27e12b0ffd8a303849c522241c235238d6a500aef925ec3871b436cR117Fixes #39041
To test:
From
File
>Settings
> Turn onShow Invisible Workspaces
Run the following script (that uses
LoadAndMerge
internally:Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.