Tr: Re: [ptx] Re: [PanoTools] About the FOV compute

[marc.torz at voila.fr]

Oups, seems like i have only answered to Pablo... That's why i transfered it...

/****************************/
 Hi !
 Thanks for answering...
 
 I want to know that because I have made a project which consists in auto-assembling photos taken by a drone (it is a common project with Mathieu Tobie which is a member too)... But when I launch the script for PTOptimizer and PTStitcher, I have to put an output FOV, width and height... 
 We have seen that if you put bad dimensions, the stitch can be totally incorrect...
 That's why auto-calculating the FOV could be a very great improvement...
 For the moment, we arbitrary add 150 for width anf heigth for each image stitched,and 3 for FOV for each image (found empirically)...
 
 
> 
> > Hi Marc,
> > 
> > > Hi !
> > > I am new on your forum, and I'm trying to understand
> > > how Hugin is done...
> > > I wonder how is computed the automatic FOV when you
> > > push "Calculate Field of View"...
> > > But the function Panorama::calcFOV() in Panorama.cpp
> > > is quite not clear ...
> > > 
> > > I don't understand how you proceed ... Is there any
> > > documentation about the automatic field of view
> > > compute ?
> > 
> > Not really.. It simply traces the borders of each image in a spherical
> > coordiante system and uses the bounding box as a measure for H/VFOV.
> > 
> > It's got some bug, which leads to a 180 deg VFOV sometime.. have to fix
> > that..
> > 
> > BTW. why are you interested in it?
> > 
> > ciao
> >   Pablo
> > 
> ------------------------------------------
> 
> Faites un voeu et puis Voila ! www.voila.fr 
> 
> 
------------------------------------------

Faites un voeu et puis Voila ! www.voila.fr