Ticket #6223 (closed: invalid)
PeaksWorkspace should save/load any additional columns
| Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 2.4 |
| Component: | Mantid | Keywords: | |
| Cc: | owen.arnold@… | Blocked By: | #5729 |
| Blocking: | Tester: | Owen Arnold |
Description
Currently, the PeaksWorkspace saves only those columns that were created by itself. However, a public API exists for adding new columns but they will not get saved/loaded from a NeXus file.
Change History
comment:3 Changed 8 years ago by Martyn Gigg
Test refactoring before starting real work. Refs #6223
Changeset: 31db1a52db89abf3a329435d91a0a58bfd6d503d
comment:4 Changed 8 years ago by Martyn Gigg
- Status changed from accepted to verify
- Resolution set to invalid
It has been decided that the PeaksWorkspace format is not really as flexible as it first looks so it won't be made dynamic.
comment:5 Changed 8 years ago by Martyn Gigg
Test refactoring before starting real work. Refs #6223
Changeset: 31db1a52db89abf3a329435d91a0a58bfd6d503d
comment:6 Changed 8 years ago by Owen Arnold
- Status changed from verify to verifying
- Tester set to Owen Arnold
comment:7 Changed 8 years ago by Owen Arnold
Agreed. We might end up revisiting this in the future if additional information is required on a peak-by-peak basis. For example, Dennis has been working on an integration algorithm, for which we might end up needing to record the 'shape' of the peak integration peak-by-peak.
