Ticket #170 (closed task: fixed)
Opened 2007-08-30T15:58:18-05:00
Last modified 2007-10-10T13:52:08-05:00
Investigate ImageJ's VirtualStack objects
| Reported by: | curtis | Owned by: | melissa |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | bio-formats | Severity: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
ImageJ now has a VirtualStack class that encapsulates its virtualization logic. It would be worthwhile to study this implementation, see what its limitations are, and decide which parts of Bio-Formats (if any) could be integrated with it. In particular:
- How difficult would it be to integrate our caching logic with VirtualStack?
- Can we provide an option to use VirtualStacks with the Bio-Formats Importer plugin?
- Do any popular plugins (in particular, Image5D) use VirtualStacks at all; if so, how; and can we take advantage of that usage, or model ours after them?
Change History
comment:1 Changed 2007-10-10T13:52:08-05:00 by melissa
- Status changed from new to closed
- Resolution set to fixed
In order to create a VirtualStack, each plane of the dataset must be stored in a separate file. This seems like a fairly serious limitation, so I don't think there is any benefit to integrating our caching logic with VirtualStack. As far as I know, there aren't any other plugins that use this feature.