[Insight-developers] Need sample Input files: InsightData CVS module ?

[Bill Lorensen]

Luis,
I agree that the data in Testing/Data should be in a separate checkout. However, we will still want to limit the size of data files we keep under cvs.

Also, I want to delay moving the Testing/Data tree until I complete the regression testing update.

Bill

At 05:43 PM 3/5/03 -0500, Luis Ibanez wrote:

>George,
>
>Using the real file size is great as
>far as testing IO is concerned, but
>the problem is that this image data
>is going in a directory of the source
>tree.
>
>The bare C++ in the toolkit makes now
>about 48Mb, but with the images we added
>for the base line, the size is growing
>rapidly.
>
>A normal user doesn't really cares about
>the images in the baseline, so it is hard
>to justify for them that the ITK repository
>contains 50% to 70% of image data that they
>do not need.
>
>Maybe the Data shouldn't be in the main
>source tree but in something like an "InsightData"
>cvs module as it is done in VTK...
>
>Note that we also have some images in
>Examples/Data, those could also be moved
>to a InsightData cvs module.
>
>We already have a CMake variable that will
>allow to indicate where the data has been
>installed.
>
>
>   Luis
>
>
>-------------------------------------------
>
>George Stetten wrote:
>>Bill,
>>I'm not sure what option we have for the .vol files, which are Real Time 3D ultrasound data.  Each volume takes up 2 meg, and to test the "moving" pictures, you need at least 2 frames.  There are going to be many imaging modalities that have more than 4 megs in them.
>>I suppose we could make a function to generate a test file, but in the long run isn't the solution to be able to handle larger files?
>>Thanks.
>>George
>
>
>
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers