[Insight-developers] Problems with itkGDCMSeriesFileNames/GDCM

[Peter Cech]

On Mon, Jul 03, 2006 at 10:36:15 -0400, Mathieu Malaterre wrote:
> Peter Cech wrote:
> >Hi,
> >
> >I've got problems with itkGDCMSeriesFileNames - it does not recognise
> >my DICOM series (bug #3475) I have I put the series at
> >http://www.vision.ee.ethz.ch/~pcech/bugreports/ITK_GDCM-20060703/
> >You can use DicomSeriesReadImageWrite2 example to test it.
> >
> >After turning debugging on for GDCM, this message repeats for every
> >file:
> >
> >Warning: In /scratch/from_cvs/ITK/Insight/Utilities/gdcm/src/gdcmFile.cxx, 
> >line 307, function virtual bool gdcm::File::I
> >sReadable()
> >Pixel Dicom Element 7fe0|10not found
> 
> oh that's bad...it means there is no Pixel Data :-P
> I'll look into the problem, thanks for report and dataset.
> 
> >Using PrintFile from GDCM on the files worked without problems (in all
> >of CVS HEAD, CVS branch Version1_2 and Version1_3).
> 
> How about DicomImageReadPrintTags ?

No success, Pixel Data tag is not found, but the program tries to
continue anyway and soon terminates with "Floating point exception".
Here is the full log:
http://www.vision.ee.ethz.ch/~pcech/bugreports/ITK_GDCM-20060703/DicomImageReadPrintTags.log

One thing I did not notice before. GDCM complains about missing DICOM
dictionaries:

Warning: In /scratch/from_cvs/ITK/Insight/Utilities/gdcm/src/gdcmDict.cxx, line 54, function gdcm::Dict::Dict(const std::string&)
Can't open dictionary /scratch/installed/ITK-CVS-20060628/share/gdcm/gdcm.dic

and similarly for dicomVR.dic, dicomTS.dic, DictGroupName.dic and
DicomDir.dic.

No wonder, the dictionaries got installed into
.../include/InsightToolkit/gdcm/Dicts

Putting dictionaries into expected place does not help, see
http://www.vision.ee.ethz.ch/~pcech/bugreports/ITK_GDCM-20060703/DicomImageReadPrintTags2.log


> >I tried to compile ITK with USE_SYSTEM_GDCM=ON, but the compilation
> >failed with both cvs checkouts of Version1_2 and Version1_3. What GDCM
> >version can be used as "system" one with current ITK?
> 
> We are internally using this new feature. Version1_3 will definitely not 
> work since the API was changed in a non-backward compatible way. But 
> Version1_2 should work, could you send the error log ?

I'll try both with Version1_2 and gdcm 1.2.1 I found on sourceforge and
send you the exact error message.

Regards,
Peter