[Insight-developers] Image::DirectionType should be Nx3 rather
than NxN?
Luis Ibanez
luis.ibanez at kitware.com
Mon Sep 17 08:54:28 EDT 2007
Hi Steve,
We are following up on the bug report:
"5573: Image::DirectionType should be Nx3 rather than NxN"
http://public.kitware.com/Bug/view.php?id=5573
We are tempted to mark this as a "will not fix" item.
The reason being that when you read a 2D DICOM slice that
actually has 3D orientation information, such image should
be read into an ITK image type instantiated for 3D, not an
image type instantiated for 2D.
When instantiating the type as a 3D image, the 2D DICOM slice,
once it is read into memory, will be seen as a 3D image composed
of a single slice. This image will have a 3D position and 3D
orientation.
Please let us know if you still consider that this bug
should be kept open.
Thanks
Luis
----------------------
Steve M. Robbins wrote:
> On Wed, Jul 04, 2007 at 03:06:16PM +0000, Mathieu Malaterre wrote:
>
>>On 7/4/07, Steve M. Robbins <steve at sumost.ca> wrote:
>
>
>>>As it stands now, the GDCM ImageIO class effectively throws away
>>>information when you read a 2D image: you get only the first two
>>>components of the 3-vectors.
>>
>>
>>This issue rings a bell and I am pretty sure this was fixed. In the
>>cstor of GDCMImageIO I made sure to alawys use 3D:
>>
>> this->SetNumberOfDimensions(3); //needed for getting the 3 coordinates of
>> // the origin, even if it is a 2D slice.
>>
>>Are you using an itk::OrientedImage ?
>
>
> I stand corrected on this point. I'm not writing any code at this
> point, just reading the ITK sources. I missed this line in the
> constructor.
>
> However, this is arguably a different bug: if I load a 2D image, I'd
> be very surprised to find out it is 3D in ITK! ;-)
>
> -Steve
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
More information about the Insight-developers
mailing list