Roger -
On Oct 17, 11:40 pm, Rogier Wolff <rew-googlegro...@bitwizard.nl>
wrote:
> The problem is more complex. The normal mode-of-operation of enblend
> is: that images are added incrementally. So such an "almost
> overlapping" image could very well be completely inside the "already
> assembled pixels", which enblend detects, but also, as is probably now
> the case, only just outside the currently being-stitched area.
Enblend always works on pairs of images,
which simplifies the algorithm considerably. ;)
I have added an experimental "almost complete
overlap" check to Enblend in rev5c2c0a81fcb3:
http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/rev/5c2c0a81fcb3
Please let me know, how it performs.
We have one free parameter, the ratio of
non-overlapping pixels over the total number of
pixels in the overlap region. We could use it
to tune this check.
If you think my approach is a bad idea, I'll not
hesitate to kick it out of the trunk.
Thanks,
Chris
--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
