[Insight-users] Problem reading 4D Dicom datasets

[Antoine DUCHAMPS]

This is the output of gdcminfo* for the first volume of the sequence. 

Hope this helps,

antoine.

* I've used gdcminfo of gdcm 2.0.10 since I didn't find it for gdcm
1.2.x


MediaStorage is 1.2.840.10008.5.1.4.1.1.4 [MR Image Storage]
TransferSyntax is 1.2.840.10008.1.2.1 [Explicit VR Little Endian]
NumberOfDimensions: 2
Dimensions: (896,896,1)
Origin: (-802.466,-841.681,-57.2297)
Spacing: (1.79688,1.79688,3.5)
DirectionCosines:
(0.999681,0.000181557,-0.0252438,4.09574e-09,0.999974,0.00719211)
Rescale Intercept/Slope: (0,1)
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: AXIAL
IOD Verification: succeed


Le mercredi 22 avril 2009 à 12:33 +0200, Mathieu Malaterre a écrit :
> On Tue, Apr 21, 2009 at 12:49 PM, Antoine DUCHAMPS
> <antoine.duchamps at gmail.com> wrote:
> > Hi Mathieu,
> >
> > Thanks for responding. I think the problem is not the 4th dimension
> > ordering in this case, but a problem with voxel ordering of the
> > individual 3D files. I did the following test: I took the example
> > Examples/IO/DicomImagesReadWrite.cxx and changed InputDimension to 3.
> > Then I tried to read just one volume and the resulting image is [896 896
> > 1] instead of [128 128 41]. Do you know if the class  GDCMImageIO can be
> > used to read 3D datasets?  Is this the expected behaviour?
> 
> Do you have the 'gdcminfo' command line output ? Could you send me output of:
> 
>  $ gdcminfo /path/to/your/3D/image
> 
> GDCM 1.2.x was released ~2005, but it had support for Enhanced MR
> Image Storage AFAIK... I do not understand what could be going on
> wrong. Columns/Rows/Number of Frames should use the same Attribute.
> 
> Ref:
> http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=GDCM_Release_2.0#GDCM_2.0.10_.282008.2F11.2F18.29
>