Posted by
Leonard Sitongia on
Aug 31, 2007; 7:35pm
URL: http://imagej.273.s1.nabble.com/dev-overriding-multiple-classes-tp3698479p3698482.html
Kenneth Sloan wrote:
> For many years, I have been teaching the philosophy that there are (at
> least) two separate coordinate systems for an image: the Real valued
> Cartesian coordinates <x,y> (I prefer <0.0, 0.0> to be at the center
> of the image - on the optic axis, in the absence of cropping) and the
> Integer valued Cartesian coordinates <column,row> (the pixel
> addresses). [I'm not always successful...]
>
I agree with your point, and your coordinate origin, too, especially for
astronomical telescope data.
>
> We'll just have to wait for ImageK.
I have found a couple of projects based on ImageJ (EH-HOU and SALSA-J),
but I would hate to go in that direction
>
> In the meantime, I don't think there's any realistic answer other than
> "copy and modify *every* method that uses <column,row> where you would
> like to use <rho,theta>. You may find that it will be nearly
> impossible to define a boundary around the <rho,theta>-safe methods -
> and you might eventually end up re-writing ALL of ImageJ.
>
> this is probably not a good plan.
There's something like this, in a sense, already in ImageJ. That is,
the handling of FFTs. I've discovered that a property is set on the FFT
image (which is in polar coordinates), and in places in the code a test
of that property is used to format output, analyze measurements, and the
other sorts of stuff that I want to do.
--
==Leonard E. Sitongia
High Altitude Observatory
National Center for Atmospheric Research
P.O. Box 3000 Boulder CO 80307 USA
[hidden email] voice: (303)497-2454 fax: (303)497-1589