[Insight-users] DICOM Image spacing with GDCMImageIO

[Matthias Keil]

Hi Mathieu,

I had a similar bug reading a single file DICOM volume. Instead of 
reading the correct spacing from the DICOM header, it substituted the 
spacing by (1,1,1).

It's probably the best to upgrade the GDCM that is used in ITK.

Regards,
Matthias

Mathieu Malaterre schrieb:
> On Tue, Jan 20, 2009 at 1:25 PM, C. A. Cois <cacois.itk at gmail.com> wrote:
>   
>> Mathieu,
>>        Thanks for the info.  The output from gdcminfo is:
>> MediaStorage is 1.2.840.10008.5.1.4.1.1.4.1 [Enhanced MR Image Storage]
>> TransferSyntax is 1.2.840.10008.1.2.1 [Explicit VR Little Endian]
>> NumberOfDimensions: 3
>> Dimensions: (384,384,130)
>> Origin: (74.1753,-277.826,199.565)
>> Spacing: (0.9375,0.9375,0.940002)
>> DirectionCosines: (0,1,0,0,0,-1)
>> Rescale Intercept/Slope: (0,2.10842)
>> SamplesPerPixel    :1
>> BitsAllocated      :16
>> BitsStored         :12
>> HighBit            :11
>> PixelRepresentation:0
>> ScalarType found   :UINT16
>> PhotometricInterpretation: MONOCHROME2
>> PlanarConfiguration: 0
>> TransferSyntax: 1.2.840.10008.1.2.1
>> Orientation Label: SAGITTAL
>> IOD Verification: failed
>> Specifically, the spacing found is (0.9375,0.9375,0.940002), which looks
>> like 1/2 the z-plane spacing as ITK reads. The image is attached.
>>     
>
> thanks for the image. Indeed this is a bug in GDCM 1.2.x. Please log
> it in at http://itk.org/Bug
>
> Meanwhile you can recompile ITK and use a system installed GDCM. Take
> the latest : gdcm 2.0.10 which more robust and report the correct
> value.
>
> Thanks !
>
>   

-- 
| Dipl.-Ing. Matthias Keil
|
| Fraunhofer Institute for Computer Graphics (IGD)
| Cognitive Computing & Medical Imaging
| Fraunhoferstraße 5, 64283 Darmstadt, Germany
|
| phone  : +49 6151 155 212
| fax    : +49 6151 155 480
| mobile : +49 173 5709746
| e-mail : matthias.keil at igd.fraunhofer.de
| skype  : matthias.keil.office
| web    : http://www.igd.fraunhofer.de/~makeil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20090123/1f0693b9/attachment-0001.htm>