On Thu 30-Sep-2010 at 12:09 +0200, Simon Oosthoek wrote:
I also have a question: what is the default optimisation that
hugin does when you first load images, generate CPs and then
presto it presents the first preview. I was unable to improve on
that (apart from adding a mask), so I'm wondering what it is that
makes this a good optimisation?
It's SmartOptimise::smartOptimize in
src/hugin_base/algorithms/optimizer/PTOptimizer.cpp
There are some heuristics and at least two passes:
First it optimises just positions, if the final panorama is 360°
then it will optimise field of view of the photos in the next step.
It looks at the spread of control points and either optimises just
'b' or 'a,b,c' lens parameters depending on this spread.
If the photos are wider than 60° then d,e will be optimised too.
It does some checks with the result of this second step, if the
v,a,b,c,d,e parameters are not credible then it backs out and
optimises the project again but with less parameters.
Looking at this code, some of the default thresholds could be
better, e.g. I think it is safe to optimise field of view if the
panorama is greater than about 150°, the a,b,c thresholds are too
high, and the d,e threshold should be a proportion of the photo
width rather than a pixel value.
A lot of this could be made into user preferences, not because users
should be continually tinkering with these settings, but there is no
other way I can think of of determining a good set of defaults.
--
Bruno
--
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
