[Insight-users] Bug in TransformPhysicalPointToIndex ??

[Bill Lorensen]

David,

I'm looking at your problem again. Can you provide me with the list of
points you are using as input and getting as output? I want to
reproduce your exact situation. I already have your meta image
headers.

Bill

On Fri, Mar 6, 2009 at 4:57 AM, David Pastor <david.pastor at die.upm.es> wrote:
> Hello,
>
> I'm having a weird lack of accuracy while using this method.
>
> From a list of physical positions y create a set of points and then i use
> this function to set an index on the image. I do it in 2 ways:
>
> -one as a 3d image
> -the other as a frame in a 4d image
>
> I set the spacing and sizes equally (the output mhd headers are consistent)
> and the elements of the point objetc are THE SAME but after calling this
> method the index has different values for the Z component. In other words,
> when computing the same index for 3D and 4D the result is different (one
> pixel difference in Z component) from the same coordinates (only changes the
> dimension of the image). It is also weird it does affect only the z
> component and not the X/Y plane
>
> Any idea why the index is not computed equally?
>
> Cheers
> David
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-users
>
>