Ticket #37 (closed: duplicate)
Add and maintain History for workspaces
Reported by: | Nick Draper | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Iteration 3 |
Component: | Keywords: | History | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Nick Draper) (diff)
The history needs to contain several sections.
- An environment sections containing
- The version of Mantid
- The OS name and version
- The user name
- The algorithm History of a workspace (i.e. for every algorithm that has been run on this workspace of it's parents).
- The name and version of the algorithm
- The date and time applied
- The values of every alogirthm property
- How long the algorithm took to run
The majority of the History data filling can take place in the Workspace Factory. If we change the main factory method to take (string workspaceType, Workspace parentWorkspace, algorithm currentAlgorithm) then the workspace would have all of the info required to.
- Copy all of the History from the parentWorkspace to the new one
- Create a new algorithm History record from the current Algorithm
We may need to think later about how we handle branched histories. eg. WS1 = LoadRaw("file1") WS2 = LoadRaw("Vanadium2") WS3 = WS1/WS2 At this point WS3 would need to contain the history of both WS1 and WS2
Change History
comment:2 Changed 13 years ago by Nick Draper
- Summary changed from Add and maintian History for workspaces to Add and maintain History for workspaces
comment:3 Changed 13 years ago by Nick Draper
- Status changed from new to closed
- Resolution set to duplicate
duplicate of #58
comment:4 Changed 9 years ago by Alex Buts
refs #37 Merge branch 'master'
Conflicts:
Code/Mantid/Framework/Kernel/inc/MantidKernel/ValidatorSignalChange.h
Changeset: 5c9639416a56b09180a6a4d4407132d69b3f0aa2