NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #19 (closed feature: moved)

Opened 2010-02-17T15:07:04-06:00

Last modified 2014-06-08T22:48:29-05:00

Efficient support for very large image planes

Reported by: curtis Owned by: curtis
Priority: major Milestone: imagej-2.5.0
Component: ImgLib2 Version:
Severity: major Keywords:
Cc: Blocked By: #43, #444


The current version of ImageJ provides a mechanism, the virtual stack, for handling very large datasets one image plane at a time. But there is no mechanism for working with image planes larger than available memory (e.g., 40Kx40Kx16-bit = 2.98GB).

With imglib it should be possible in principle to handle such large data planes using a clever storage strategy, but it would be nice to have at least one concrete example in code demonstrating how this should work.

Change History

comment:1 Changed 2011-02-25T10:49:02-06:00 by aivar

  • Status changed from new to accepted

ImgLib has provision for a CellContainer which would lend itself to paging cells in/out. My Hackathon zoom viewer hanndles images of this size.

comment:2 Changed 2011-02-25T11:16:30-06:00 by aivar

  • Severity changed from non-issue to major
  • Milestone changed from progress-report to biweekly-2011: Mar-28 to Apr-08

comment:3 Changed 2011-04-25T11:34:22-05:00 by curtis

  • Milestone changed from biweekly-2011: Apr-11 to Apr-22 to biweekly-2011: Jun-06 to Jun-17

This sort of testing makes sense to do as part of the 2.0-beta1 development in June.

comment:4 Changed 2011-08-01T10:00:42-05:00 by curtis

  • Milestone changed from biweekly-2011: Jul-18 to Jul-29 to imagej-2.0-beta3

comment:5 Changed 2011-08-01T11:16:07-05:00 by aivar

  • Status changed from accepted to closed
  • Resolution set to fixed

comment:6 Changed 2011-08-01T12:36:41-05:00 by aivar

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:7 Changed 2011-08-12T16:23:55-05:00 by bdezonia

Note that as defined we rely on the mapping from Img data to ARGBScreenImage to be 1:1. This happens in Imglib's CompositeXYProjector. In the future the projector might need a scale such that large images can map to small screen images. And the map() routine would need to be modified accordingly. Also would want a tile manager.

comment:8 Changed 2012-02-23T11:11:25-06:00 by curtis

  • Type changed from task to story
  • Summary changed from Verify very large image planes can be handled efficiently to Efficient support for very large image planes

comment:9 Changed 2012-02-26T20:07:35-06:00 by curtis

  • Blocked By 43 added

comment:10 Changed 2012-02-26T22:54:33-06:00 by curtis

  • Blocked By 444 added

comment:11 Changed 2012-03-05T14:47:58-06:00 by curtis

  • Milestone changed from imagej-2.0-beta3 to imagej-2.5

comment:12 Changed 2013-12-06T17:51:20-06:00 by aivar

  • Owner changed from aivar to curtis
  • Status changed from reopened to assigned

comment:13 Changed 2014-06-08T22:48:29-05:00 by curtis

  • Status changed from assigned to closed
  • Resolution set to moved