Ticket #1868 (new enhancement)
Opened 2013-05-14T13:44:29-05:00
Last modified 2013-09-24T15:25:10-05:00
Take advantage of cell iteration order
| Reported by: | hinerm | Owned by: | hinerm |
|---|---|---|---|
| Priority: | major | Milestone: | imagej2-b10-compatibility |
| Component: | SCIFIO | Version: | |
| Severity: | serious | Keywords: | Cells |
| Cc: | Blocked By: | ||
| Blocking: | #1968 |
Description
Currently, the DefaultDatasetView's use of an ARGBScreenImage (which is an ArrayImage) forces a flat iteration order, which may cause
(image height) * (image width / cell width)
cell loading events, as the CellIterationOrder is not being used.
To properly leverage the CellIterationOrder, I believe a new ScreenImageType that uses a CellImage instead of ArrayImage will need to be created and accepted by the DefaultDatasetView.
It could probably just use the default CellImg in imglib2, and should not extend SCIFIOCellImg due to its use of a Reader to dynamically load requested areas, as this ScreenImage is more of a blank canvas that will be populated by a SCIFIOCellImg.
If the cells are of the same size, then the CellSreenImage should be able to just use its cursor's "next()" method to efficiently iterate over its cells, localizing and reading a cursor from a SCIFIOCellImg at each step.