[Insight-users] slice based memory representation of itk volume

[Miller, James V (Research)]

Feng, 

ITK does not currently support slice based memory representations. It is
something that we have been considering.  We are trying to come up with 
a design whereby the existing set of iterators would work.  If the
iterators can handle this representation (in particular the neighborhood 
iterators), then I expect most filters will work without issue.

Jim

-----Original Message-----
From: insight-users-bounces+millerjv=crd.ge.com at itk.org
[mailto:insight-users-bounces+millerjv=crd.ge.com at itk.org]On Behalf Of
Feng Ma
Sent: Thursday, November 03, 2005 2:57 PM
To: insight-users at itk.org
Subject: [Insight-users] slice based memory representation of itk volume


Dear all:

  I searched the mail-list and didn't find answer to this problem: do we 
have slice-based memory allocation for itk volume? I think currently itk 
volume data is in a single 1-D array.

  The reason I ask this question is that on windows system, sometimes due to 
memory fragment, it is not possible to allocate a large 1-D array for itk 
volume, especially for large float volume. If the 3D volume memory is 
allocated slice by slice, it will have much larger chance of success in 
memory allocation. Certainly all filters have to be able to accommodate this 
change.

  Thanks.

-Feng


_______________________________________________
Insight-users mailing list
Insight-users at itk.org
http://www.itk.org/mailman/listinfo/insight-users