[ITK] Reading old Philips DICOM

Bradley Lowekamp blowekamp at mail.nih.gov
Wed Mar 19 08:51:33 EDT 2014


Hello,

Are you able to get a stack trace to determine where the issue is? Perhaps compiled in debug mode.

Also there is the ITK Module IOPhilipsREC which may need to be turn on for this type of file. This module is not on by default. During your cmake configuration you need to turn on Module_ITKIOPhilipsREC.

If turning on this module solves your problem, then there is still a bug in ITK/GDCM that is causing this segmentation fault.

Brad

On Mar 19, 2014, at 8:31 AM, Pölönen Harri <Harri.Polonen at vtt.fi> wrote:

> Hi all,
>  
> I came across some pretty old DICOM data from Philips Panorama 0.6 T magnetic resonance scanner. The DICOM files can be loaded on ITK 3.20 with GDCM 1.2.4 without any problems. However, the most recent ITK 4.5.1 with GDCM 2.0.17 crashes while trying to read any of those DICOM files. My best guess is that the output from the old Panorama scanner violates modern DICOM standards, and GDCM crashes because it tries to follow the current standard.
>  
> Any suggestions on how to read that old DICOM data into ITK 4.5.1?
>  
> Going back to using GDCM 1.2x is not an option, because I need the support for the modern DICOM data as well. Should I report this as a bug to GDCM developers?
>  
> The crash occurs even with the simple “DicomSeriesReadImageWrite” example while running “reader->update()” line, i.e. probably inside some GDCM function. The error cannot be caught into itk::ExceptionObject.
>  
> Thanks!
>  
> /Harri Pölönen
> Finland
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20140319/c5e8ea09/attachment-0002.html>


More information about the Community mailing list