On Tue, Dec 28, 2010 at 12:08:36PM -0500, Yuval Levy wrote:
> On December 28, 2010 09:36:59 am kfj wrote:
> > I'm glad you appreciate my contribution
> 
> not only me
> 
> https://bugs.launchpad.net/hugin/+bug/685489

Allow me to add that I really don't think that removing all the "far" 
points is the best way to do this. 

Often hugin will find control points in the grass near my
feet. Sometimes one or two near the horizon where it actualy matters.

Now the 5 or 10 control points in the grass will "twist" the images so
that the one or two good ones are some of the furthest from their
proper mapping. But in fact they are the ones that matter most.

Throwing them away (well ok, commenting them out) isn't going to help
the pano.

You know what I'd like to do? I'd like to assign weights to the
control points. For example, all control points would start with
weight 10. But then I can set the weight of those in the distance to
100 to increase their weight. Or I can set the weight of those closeby
to 1 to reduce it. (for an identical effect). 

One step further we'd find different ways to set the weights
automatically. For example the similarity index might come into
play. Or I might be able, as a user, to indicate: the further up an
image the higher the weight. 

When I shoot panos, I take portrait pictures. These overlap in a
narrow region with the next image. So I think I'd like about 

  --sieve2width 2 --sieve2height 5 --sieve1size 3

To have points near both edges let and right, and a uniform
distribution along the height of the image. If in all ten areas 3
control points are found, 30 is a bit much. On the other hand, it
doesn't always find control points. Hmm. cpfind can't know the
overlapping area, right? So I would need say a 5x5 grid to guarantee
some points in the overlapping area. Oh well. Then we might have
even more control points if things match up well.... 

        Roger. 

-- 
** [email protected] ** 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! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

-- 
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 [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to