More Flexible PeakWorkspaces

[OwenArnold]

This issue was originally TRAC 4235

Need to be able to add additional columns onto a peak workspace to hold information such as

• Number of pixels contributing to the peak
• Peak integrated value

These items (and others) will need to be stored on the PeakObject. Nick suggests putting a property manager on the peak object.

Will also need to ensure that all peaks have the the same information set. Do not want differences in the schemas for different peaks in the same PeaksWorkspace!

Loading and Saving should be handled in a separate ticket.

[OwenArnold]

@NickDraper (2012-01-09T09:43:16):
Moved to iteration 33 at iteration 32 code freeze

---

@NickDraper (2012-04-30T14:12:40):
Moved at end of release 2.1

---

@NickDraper (2012-08-10T12:43:32):
Moved at the end of release 2.2

---

@NickDraper (2012-10-28T11:38:45):
Moved to milestone 2.4

---

@NickDraper (2013-01-28T09:22:58):
Moved at the code freeze for release 2.4

---

@NickDraper (2013-04-29T09:49:36):
Moved to r2.6 at the end of r2.5

---

@NickDraper (2013-07-26T13:54:58):
Moved to backlog at the code freeze for R2.6

---

@NickDraper (2014-02-14T11:04:55):
Bulk move to assigned at the introduction of the triage step

[OwenArnold]

For samuel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.