« Return to Thread: What is optimized FOV really?

Re: What is optimized FOV really?

by Tom Sharpless :: Rate this Message:

Reply to Author | View in Thread


Thanks all for a useful discussion.

It is standard practice in lens calibration to compute a "corrected"
radius from the observed radius of an image point by means of a
polynomial.  However I think it is becoming clear that PanoTools and
its clients such as Hugin are almost alone in including odd-order
terms in the correction polynomial.  The even order terms correspond
to the assumed rotational symmetry of the lens, so are well behaved in
numerical optimization.  Odd terms beyond the first do not correspond
to any realistic physical property, and tend to destabilize numerical
optimization.

So PT would be better off also using an even-orders-only polynomial
for radius correction.  That may not just be a matter of defining  b
to be always 0, however, because, as Klaus points out, in the present
scheme the focal length (equivalently fov) is mixed into the
correction polynomial rather than being a separate parameter (as it
should be).

As I see it, the right way to normalize the correction is to divide
the measured radius by the focal length before applying the
polynomial:  let
   f = current estimate of focal length;
   u = r / f;
   R = u + p2 * u ^2 + p4 * u^4;
then R is the proper argument to the trigonometric function that
defines the ideal view angle (in radians), either
  Angle = atan( R ) for a rectilinear lens, or
  Angle = k * asin( R / k ) for an equal-area type fisheye (design
parameter k), or even
  Angle = R  for a true equal-angle fisheye.

I believe that using this scheme would improve the stability (and so
the average quality) of the numerical results delivered by the PT
optimizer.

Regards, Tom






On Jul 3, 12:22 pm, Aron H <aron.hel...@...> wrote:

> On Jul 3, 4:08 am, Klaus Foehl <k...@...> wrote:
>
>
>
> > Hello,
>
> > Quick addition and summary from my side.
>
> > 1) Barrel distortion correction: panotools uses r* = a*r^4 + b*r^3 +
> > c*r^2 + d*r,
> > with r being the normalised radius. If it were not for the condition a
> > +b+c+d=1
> > this parameter d would be fully collinear with the focal length.
> > focal_length_panotools * d = true_focal_length
>
> > 2)http://www.vision.caltech.edu/bouguetj/calib_doc/htmls/parameters.html
> > x_d=x_n * (1+kc(1)*r^2+kc(2)*r^4+kc(5)*r^6) +dx, dx=[...]
> > Looking at the distortion formulas the Bouguet model looks
> > mathematically
> > sound to me, as the parameters x_d and dx only use odd and even
> > powers,
> > respectively, of (r,x,y) polynomial expressions.
> > That respects the lense symmetry. Parameters a and c in panotools do
> > not.
>
> I've looked through Bouguet's site for an explanation of the symmetry
> issue, and I think he pushes it off to publications. I guess I don't
> know what the argument is, except perhaps that r^2 and r^4 distortion
> are expected from the lens design, and the r and r^3 are not. The
> formulas only deal with positive r values, and apply distortion
> totally in the radial direction, so they are 'symmetric' in that
> sense. Is there a good explanation of this somewhere?
>
>
>
> > 3) In the xd formula 1 is equivalent to d, kc(1)=b/d, kc(2) and kc(5)
> > are unaccounted for. (N.B. I suggested a few times to include
> > a kc(2) type parameter into hugin/panotools).
>
> Note, however, that the 'r' parameter is scaled differently in Hugin
> and Bouguet. I'll write up the derivation....
>
>
>
>
>
> > 4) Sheer parameters are available in panotools but are not shown
> > in the hugin GUI. There are two parameters, and combined with
> > the roll parameter I suspect that this set of three only spans
> > a two-dimensional configuration space, save for possibly a
> > higher order correction that results in non-square-like pixels.
>
> > 5) Tangential distortion vectors, kc(3) and kc(4) in Bouguet,
> > I have not seen such in hugin/panotools.
>
> > 6) Principal point cc in Bouguet are parameters e and f
> > in panotools, in the GUI labelled x and y.
>
> > 7) Rectangular non-square pixels, Bouguet using fc(1) and fc(2),
> > are not there in the hugin/panotools model.
>
> > Summary: models are reasonably similar, Bouguet is more powerful,
> > and parameters a and c of hugin/panotools, the only ones
> > I cannot find a match in Bougues, have a maths symmetry issue.
>
> > Cheers
> > Klaus
>
> I agree with the rest, thanks for the nice summary,
> Aron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

 « Return to Thread: What is optimized FOV really?