Generic Image
Registered by
Tom Dimiduk
Should we have a model for image data that is not holograms? I (tgd) at least sometimes end up using hp.Hologram as a generic image container and sometimes feel a little bad about it. Also, truthfully, scatterpy.
I think a solution to this may be to have a parent class that is a thinner wrapper around np.ndimage that implements our image model and metadata on top of the basic ndarray. Reconstruction and hologram can then inherit from that parent.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Tom Dimiduk
- Completed by
- Tom Dimiduk
Related branches
Related bugs
Sprints
Whiteboard
(?)