Ticket #3501 (closed: fixed)
Algorithm to save python script from workspace's history
Reported by: | Peter Peterson | Owned by: | Peter Parker |
---|---|---|---|
Priority: | critical | Milestone: | Iteration 30 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Nick Draper |
Description
Create an algorithm that takes a workspace and an output file name and writes the python script for generating the workspace. This is already present in the gui by "Show History" and "Generate Script" then "To File".
Attachments
Change History
comment:1 Changed 9 years ago by Nick Draper
- Owner set to Anyone
- Status changed from new to assigned
comment:9 Changed 9 years ago by Peter Parker
- Status changed from accepted to verify
- Resolution set to fixed
comment:10 Changed 9 years ago by Nick Draper
- Status changed from verify to verifying
- Tester set to Nick Draper
comment:11 Changed 9 years ago by Nick Draper
- Status changed from verifying to reopened
- Resolution fixed deleted
This does not handle branched history records, look at the example image I've attached.
comment:12 Changed 9 years ago by Nick Draper
- Priority changed from minor to critical
No the code is changed it is critical we get this working
comment:14 Changed 9 years ago by Peter Parker
- Status changed from accepted to verify
- Resolution set to fixed
Have checked a previous build and branched history records were not implemented before the changes. Raised enhancement #3766 to cover this functionality.
comment:16 Changed 9 years ago by Nick Draper
- Status changed from verifying to closed
Passed with the limitation is does not handle branched records
comment:17 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4348