[Insight-developers] Test for large image buffer convert

Luis Ibanez luis.ibanez at kitware.com
Tue Aug 11 18:15:53 EDT 2009


Yeap, that makes sense then.

I would follow Sean's suggestion and set

     ITK_COMPUTER_MEMORY_SIZE  to  4

in the 32 bits machines.

... and probably 3 (3Gb) is more realistic..


This has to be done manually, by running CMake
(or setting it in the ctest script). There is no attempt
to discover the amount of RAM at configuration time.


       Luis


--------------------------------------------------------------------
2009/8/11 Gaëtan Lehmann <gaetan.lehmann at jouy.inra.fr>

>
> Le 12 août 09 à 00:09, Luis Ibanez a écrit :
>
>  Hi Gaetan,
>>
>> What value you have set for ITK_COMPUTER_MEMORY_SIZE
>> in this machine ?
>>
>
> 24 for both 32 and 64 bit builds.
> Only 32 bit tests are failing.
>
> Gaëtan
>
>
>
>
>>
>>    Luis
>>
>>
>> -----------------------------------------------------
>> 2009/8/11 Gaëtan Lehmann <gaetan.lehmann at jouy.inra.fr>
>>
>> Le 11 août 09 à 22:07, Gaëtan Lehmann a écrit :
>>
>>
>>
>> Le 11 août 09 à 17:23, Sean McBride a écrit :
>>
>> Should ITK_COMPUTER_MEMORY_SIZE state the amount of physical RAM in the
>> machine?  What if my machine has 8 GB of physical RAM but my OS is only
>> 32 bit (and thus a process is limited to max 4 GB RAM)?  Would that
>> cause the test to run, but then crash?
>>
>> That would be unfortunate. If that's the case, it would be better to run
>> the tests only if CMAKE_SIZEOF_VOID_P is (at least) 8.
>>
>>
>> That's what is happening here... on my test system (opensolaris 24 GB of
>> RAM), I get that:
>>
>> 927/1659 Testing itkLargeImageWriteReadTest1      Passed
>> 928/1659 Testing itkLargeImageWriteReadTest2   ***Failed
>> 929/1659 Testing itkLargeImageWriteReadTest3      Passed
>>
>> The surprising result is the one for itkLargeImageWriteReadTest3 which is
>> not failing. The test seems to not even see the right image size, and
>> allocates only 1154 MB instead of the 9346 MB that it should (try to)
>> allocate.
>>
>> I guess we should rather receive an exception there...
>>
>>
>> 929/1659 Testing itkLargeImageWriteReadTest3
>> Test command:
>> /export/home/glehmann/tests/Insight/build-sse32/bin/itkIOTests
>> itkLargeImageWriteReadTest
>> /export/home/glehmann/tests/Insight/build-sse32/Testing/Temporary/LargeImage03.mhd
>> 70000L
>> Test timeout computed to be: 1500
>> Trying to allocate an image of size 1154 Mb
>> Initializing pixel values
>> Trying to write the image to disk
>> Trying to read the image back from disk
>> Comparing the pixel values.. :
>>         Probe Tag    Starts    Stops             Time (s)
>>           Allocate           1            1       2.88486e-05
>>            Compare           1            1           2.55108
>>       Initializing           1            1           3.26561
>>               Read           1            1           8.00332
>>              Write           1            1           2.31333
>>
>> Test PASSED !
>>
>>
>> Gaëtan
>>
>>
>> --
>> Gaëtan Lehmann
>> Biologie du Développement et de la Reproduction
>> INRA de Jouy-en-Josas (France)
>> tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
>> http://voxel.jouy.inra.fr  http://www.itk.org
>> http://www.mandriva.org  http://www.bepo.fr
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.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-developers
>>
>>
>>
> --
> Gaëtan Lehmann
> Biologie du Développement et de la Reproduction
> INRA de Jouy-en-Josas (France)
> tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
> http://voxel.jouy.inra.fr  http://www.itk.org
> http://www.mandriva.org  http://www.bepo.fr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20090811/ee0dfe7d/attachment.htm>


More information about the Insight-developers mailing list