[Insight-developers] orientation

[kent williams]

In looking back through this thread I think I'm beginning to see where the
problem is: SpatialObject is using methods that are not implemented
consistently between itk::Image and itk::OrientedImage.

It seems that OrientedImage performs as expected, and that Image does not,
which suggests a possible solution -- rename itk::OrientedImage as
itk::Image, and make itk::OrientedImage simply a derived class of itk::Image
with no new behavior, for backwards compatibility.

Would this break any existing code -- more to the point, is there code that
depends on itk::Image behaving in an apparently incorrect manner?


On 8/6/08 12:47 PM, "Rupert Brooks" <rupe.brooks at gmail.com> wrote:

> Hi Simon,
> 
> I would be very interested in the test you mention.   Maybe the wiki
> is the right place to post it?
> 
> Due to the problems with gradients on non-axis-aligned Oriented
> images, i created my own class, FastOrientedImage.  Its in the insight
> Journal somewhere.   I was not aware of oriented images having
> problems in 2D and I thought I had used them successfully in the past.
>  I've been planning to switch back to the more mainstream ITK approach
> and retire my custom classes - thus - I'd be very interested in this
> bug.
> 
> Thanks
> Rupert
>