[Insight-users] Memory issue with GDCMImageIO versus DICOMImageIO2

[Karthik Krishnan]

Robert Maroon wrote:

>Hi,
>
>I'm attempting to read the header from a DICOM file
>containing a series of 1800 8-bit images (each
>384x384). DicomPrintPatientInformation.cxx is
>successful at this, requiring "only" 200mb of RAM
>before finishing. However, DicomImageReadPrintTags
>immediately consumes over 1gb of RAM, keeps grabbing
>more until it's taken about 1.8gb, and then crashes a
>minute or so later.
>
>DicomPrintPatientInformation uses DICOMImageIO2,
>whereas DicomImageReadPrintTags uses GDCMImageIO,
>which seems to be the critical difference. However, it
>was mentioned elsewhere
>(http://public.kitware.com/pipermail/vtkusers/2005-March/078916.html)
>that GDCMImageIO supercedes the DICOMImageIOx readers
>and so is preferred. This leads to a couple questions:
>
>(1) Is it possible to read the DICOM headers *without*
>(like the examples do) immediately reading all the
>image data as well?
>  
>

Try replacing
reader->Update() with reader->GenerateOutputInformation()
in DicomImageReadPrintTags.cxx

>(2) Is it possible to read a single frame (or set of
>frames) individually from a DICOM file, in the case
>that the entire DICOM is too large to fit in RAM? The
>Update() method seems to collect all image information
>immediately, so (at least in the case of GDCMImageIO)
>the program crashes before it even starts.
>
>Thanks,
>
>Robert
>
>
>
>	
>		
>__________________________________ 
>Yahoo! Mail - PC Magazine Editors' Choice 2005 
>http://mail.yahoo.com
>_______________________________________________
>Insight-users mailing list
>Insight-users at itk.org
>http://www.itk.org/mailman/listinfo/insight-users
>
>  
>