Ticket #58 (closed: fixed)
Workspace history
Reported by: | Nick Draper | Owned by: | Dickon Champion |
---|---|---|---|
Priority: | minor | Milestone: | Iteration 5 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Create a History set of objects for a workspace (I have a uml diagram for ideas on the objects required).
You will have to extend the workspace factory to require a parent workspace to be provided when creating a new workspace (the data loading algorithms should pass null). This can be used to take references to the same sample and instrument objects and duplicate the History.
The end of the Execute party of an algorithm should append details of the Algorithm being run (not child algorithms) to the History.
Change History
comment:5 Changed 13 years ago by Dickon Champion
(In [663]) AlgorithmParameter, AlgorithmHistory, EnvironmentHistory all added Algorithm::store changed to allow multiple out and multiple inout workspaces to be saved in the ADS, instead of breaking after a true result the loop continues.
history structure is built up according to the plan, with a history for one object containing all the constituent history processes on other workspaces
re #58
comment:10 Changed 13 years ago by Dickon Champion
comment:11 Changed 13 years ago by Dickon Champion
(In [682])
4) executionDate and executionDuration are also now time_t and a double respectively
comment:12 Changed 13 years ago by Dickon Champion
comment:13 Changed 13 years ago by Dickon Champion
comment:14 Changed 13 years ago by Dickon Champion
comment:15 Changed 13 years ago by Dickon Champion
comment:16 Changed 13 years ago by Dickon Champion
comment:17 Changed 13 years ago by Dickon Champion
comment:18 Changed 13 years ago by Nick Draper
- Status changed from new to closed
- Resolution set to fixed
comment:19 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 906
From duplicate #37 The history needs to contain several sections.
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.
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