Ticket #5788 (closed: wontfix)

Opened 8 years ago

Last modified 5 years ago

WorkspaceHistory not specific to children of GroupWorkspaces

Reported by: Peter Parker Owned by: Nick Draper
Priority: major Milestone: Release 2.4
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Alex Buts

Description

This ticket is raised out of #5212, but addresses a more general issue.

To reproduce:

  • Load multiple files via the multifile syntax of Load. This will load the data of each file into a single GroupWorkspace.
  • Copy the history script of one of the child workspaces to the clipboard.
  • Run the script in a Python Console window.

All files loaded in the original call to Load will now be present, even though you only asked for the history of a single workspace.

This is more than just a multifile loading issue, since loading multiple period data using LoadRaw, LoadNexus or similar and getting the history of a single period is also not possible. All periods would be reloaded in such a case.

Finally, solving this issue would also require some thought about how a user would then be able to use the functionality currently seen; i.e. how would it then be possible to load all periods or all files using python history scripts?

Change History

comment:1 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:2 Changed 8 years ago by Nick Draper

  • Owner set to Nick Draper
  • Status changed from new to verify
  • Resolution set to wontfix

This is accepted as normal behaviour, it is a true representation of the history of that workspace.

comment:3 Changed 8 years ago by Alex Buts

  • Status changed from verify to verifying
  • Tester set to Alex Buts

comment:4 Changed 8 years ago by Alex Buts

  • Status changed from verifying to closed

Would agree with this conclusion though unrelated bugs were identified during the testing.

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 6634

Note: See TracTickets for help on using tickets.