[Insight-developers] Crash parsing DICOM tag / GDCM plans

[Iván Macía]

Hi Mathieu,

Thank you very much for the quick response ;)

Ahhhh vendors, the problem with the standard is that every vendor uses its
own "standard" and, following Murphy's Law, this usually makes your
application crash miserably in the middle of a meeting/demo when they give
you fresh new data to load :S

Regards

Iván

-----Mensaje original-----
De: Mathieu Malaterre [mailto:mathieu.malaterre at gmail.com] 
Enviado el: martes, 16 de marzo de 2010 17:45
Para: Iván Macía
CC: Insight Developers
Asunto: Re: [Insight-developers] Crash parsing DICOM tag / GDCM plans

Iván

2010/3/16 Iván Macía <imacia at vicomtech.org>:
> Hi,
>
> We had recently a problem while trying to read some DICOM MR images that
> make the GDCM 1.x library crash in ITK-3.16. The problem is described here
> with corresponding DICOM file attached and a possible solution (maybe does
> not work in other cases though):
>
> http://public.kitware.com/Bug/view.php?id=10423

The file at this URL is invalid AFAIK. You have a mixture of Implicit
and Explicit Data Element.

You can use GDCM 2.x as it properly handle this known issue from this
private vendor:

   gdcmconv IM_0001 IM_0001-clean

Once converted you can check that the file is now readable by most
implementation: DCMTK, GDCM 1.x ...

> Regarding GDCM 2.x, we didn't make the move yet since in our code we make
a
> lot of low level calls to GDCM 1.x and it will take us some time to port.
I
> just wanted to know if there were any plans to make GDCM 2.x to be the
> default library in ITK (in ITK 4.x maybe???). I know that GDCM 2.x can be
> used as an external dependency, but if the library is more stable and more
> advanced, I think it would be a good idea to make it the default.
Moreover,
> this would be a good reason for us to definitely move to GDCM 2.x :)

Stay tuned ;)

-- 
Mathieu