Ticket #4154 (closed: invalid)
New algorithm to copy the geometry from one workspace to another
Reported by: | Janik Zikovsky | Owned by: | Peter Peterson |
---|---|---|---|
Priority: | major | Milestone: | Release 2.6 |
Component: | Framework | Keywords: | |
Cc: | pf9@… | Blocked By: | |
Blocking: | Tester: | Mathieu Doucet |
Description
Change History
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:3 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:4 Changed 8 years ago by Janik Zikovsky
- Status changed from new to assigned
- Owner changed from Janik Zikovsky to Peter Peterson
Hi Pete,
I don't entirely remember what this ticket was going to be for - I think Vickie needed something like this after calibration?
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:10 Changed 7 years ago by Peter Peterson
- Status changed from accepted to verify
- Resolution set to invalid
This is done in CopyInstrumentParameters, at least that is what the help page says.
comment:11 Changed 7 years ago by Mathieu Doucet
- Status changed from verify to verifying
- Tester set to Mathieu Doucet
See help page here: http://www.mantidproject.org/CopyInstrumentParameters
comment:14 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5001
Note: See
TracTickets for help on using
tickets.
Probably this means copying the parameter map from one workspace to another (with the same instrument). E.g. calibrate on one workspace and copy to the other?
Using the save/read methods for parameter maps should make sense.