PanoTools mailing list archive

Mailinglist:PanoTools NG
Sender:John Houghton
Date/Time:16-Dec-2008 22:11:52 +0100
Subject:Re: Awful time stitching square suspended ceiling tiles :-(

Thread:


--- In #removed#, "pedro_silva58" 
<pedro_silva58@...> wrote:
>
> sorry for being so late to join the party, but i don't understand
> the purpose of one cp per seam.  what parameters did you optimize,
> and why?

I was merely making the point that by intelligent optimization and 
making use of parameter values already known (applied by a template), 
you can manage with far fewer control points than is the case if you 
expect PTGui to evaluate everything automatically from scratch.  My 
example was an extreme case, showing that only one point per seam 
actually enabled a perfectly good stitch to be performed.  I already 
knew the lens parameters (from calibration) and approximate yaw 
values, and I knew that the pitch of all 4 images was the same and 
the roll was also the same (since a spherical pano head was used).  
So I optimised fov, yaw (of 3 images) together with linked pitch and 
roll of all 4 images.  Of course I am not suggesting that you would 
use only one point per seam in a general workflow.

John



------------------------------------

-- 
<*> Wiki: http://wiki.panotools.org
<*> User Guidelines: http://wiki.panotools.org/User_Guidelines
<*> Nabble (Web) http://www.nabble.com/PanoToolsNG-f15658.html
<*> NG Member Map http://www.panomaps.com/ng
<*> Moderators/List Admins: #removed# 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/PanoToolsNG/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/PanoToolsNG/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:#removed# 
    mailto:#removed#

<*> To unsubscribe from this group, send an email to:
    #removed#

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/


Next message:

Previous message: