Ticket #8353 (closed: fixed)
LoadNexus doesn't handle group names properly
Reported by: | Samuel Jackson | Owned by: | Samuel Jackson |
---|---|---|---|
Priority: | critical | Milestone: | Release 3.1 |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Jay Rainey |
Description
Change History
comment:2 Changed 7 years ago by Samuel Jackson
- Status changed from inprogress to verify
- Resolution set to fixed
To Tester
Check that when using LoadNexus to open a workspace group, the names for each of the child workspaces are set properly.
Currently LoadNexus simply renames whatever child workspaces are called to be ParentWorkspace_1, ParentWorkspace_2 etc. With this fix it will simply use whatever the child algorithm called the workspace. A good example file to use would be irs26173_graphite002_ResNorm_Paras.nxs in the system tests as this is a saved workspace group where each of the child workspaces have unique names.
comment:4 Changed 7 years ago by Jay Rainey
- Status changed from verify to verifying
- Tester set to Jay Rainey
comment:5 Changed 7 years ago by Jay Rainey
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/bugfix/8353_LoadNexus_group_names'
Full changeset: f1e29728de0093aaa73e090733aa5933a9a65c1f
Refs #8353 Changed LoadNexus to simply pass up output properties.
Changeset: 40393a7a98b31fe00c52133149c258e71dc003a4