hugin-devs team mailing list archive

[rew <936836@xxxxxxxxxxxxxxxxxx>]

On Wed, Feb 22, 2012 at 10:46:51PM -0000, Bruno Postle wrote:
> This is what the 'auto estimate' option in the Control Points tab is
> supposed to do, but it doesn't appear to be functional in
> 2011.3.0.426bd4721b14 here.

Bruno,

As the "auto exstimate" only works after you've added at least one
controlpoint on the image pair, I always thought the estimate was
based on the previous controlpoints, and did not take into account
lens distortion or projection.

That's what this is about: generate a controlpoint that (currently)
has a zero "penalty". 

        Roger.

-- 
** R.E.Wolff@xxxxxxxxxxxx ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/936836

Title:
  Controlpoint punching.

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  I'm shooting "big" panos now. I'm also shooting images that contain
  nothing but sky. Controlpoints in that area are lowsy at best.

  When I've got things lined up reasonably, I would like to be able to
  say: Get me a controlpoint HERE.

  i.e. I click on the left image, and using the current transformations,
  it automatically creates a controlpoint with distance 0 with the right
  image (in the controlpoint editor).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/936836/+subscriptions