Ticket #1809 (closed: duplicate)
ConjoinWorkspaces not working with one group and one single WS
| Reported by: | Nick Draper | Owned by: | Peter Peterson |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 27 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Nick Draper |
Description
Conjoinworkspaces is not working when one of the inputs is a group workspace and the second input is a single workspace.Also it's not functioning properly when we join two group workspaces with member workspaces of overlapping spectrum numbers though this prints error message.
Change History
comment:1 Changed 10 years ago by Russell Taylor
- Summary changed from ConjionWorkspacees not working with one group and one single WS to ConjoinWorkspaces not working with one group and one single WS
comment:2 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 26 to Iteration 27
Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.
comment:3 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 27 to Iteration 28
Bulk move of tickets at the end of iteration 27
comment:4 Changed 10 years ago by Peter Peterson
- Status changed from new to verify
- Owner changed from Sofia Antony to Peter Peterson
- Resolution set to duplicate
This was fixed in #2421.
Note: See
TracTickets for help on using
tickets.
ConjoinWorkspaces was written for the specific purpose of 'gluing together' the parts of what is essentially one workspace that were loaded in more than one part to reduce memory usage. Thus passing a group and a single workspace is not a valid use case (and as noted doesn't work because the single workspace will be deleted after the first pass), so we should block this by overloading processGroups in that algorithm.
This intended use is also why the algorithm checks for overlapping spectrum numbers and fails in that case. This is intentional - MergeRuns is the algorithm for a more general combination.