[Insight-users] Image index limits

[Luis Ibanez]

Hi Oleksandr,


The components of the itk::Index are of type "long",
while the components of the itk::Size are of type
"unsigned long".

Therefore, On Linux 64 bits, you can manage
images up to the size of your memory.

With your small machine of 16 CPUs and
only 128 Gb of RAM you should do fine.

... and yes, I'm saying that with envy   :-)


On Windows 64 bits, on the other hand
we are working on fixing a problem with
the integer representation used in Windows.


Back to your report on Linux:

In the directory Insight/Testing/Code/IO
we have a test for large memory that
will attempt to create, write and read back
and image of large size (above 2 Gb).
Let's try running it in your computer.

Please do the following:

1) go to the binary directory where you
    built ITK and do

        make    edit_cache


2) Turn BUILD_TESTING   ON


3) Go to the Advanced mode,
    search for

ITK_COMPUTER_MEMORY_SIZE

    and set it to 128

 (yes, the units are in Gb).



4) Do, "c" for configure

5) Do, "g" to generate


6)  make -j32

     (that shouldn't take long)    :-)


7) Run the LargeImage test with
    the command:

      ctest -R LargeImageWrite -V

    and see if they pass.

8)  Now you can take it further,
     by looking at the command
     that is used to run the tests,
     The last numeric argument is
     the number of pixels along each
     dimension, of the image that is
     created by the test.

      You could force this number
      until the total size of this 2D
      image is comparable to your 3D
      image.

      For example, by 70,000 the
      image will be of size 1,2 Gb.



Please let us know what you find
after running these tests.


    Thanks


          Luis


--------------------------------------------------------------
On Fri, Dec 11, 2009 at 4:37 PM, Oleksandr Dzyubak <adzyubak at gmail.com> wrote:
>
> Dear users,
>
> I tried to process the 1340x1300x720 pixel image and after the slice #104 I
> am getting all zeros.
> I checked the original image and it's good. It's full of info.
> So I first decided to split that file using the
> itkRegionOfInterestImageFilter class.
> What I found is that all the chunks after the slice #104 are zeros
> thus it's not the image processing filter that causes the problem.
>
> Here is my question.
> Is there any limitation on an image index range?
> Or in other words, what is the largest pixel volume that ITK still can
> handle?
>
> Thanks,
>
> Alex
>
> PS.
> I am using 64 bit Debian Linux.
> 16 CPUs and 128 GB.
>
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://www.kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-users
>
>