Hi Henk,

Am Donnerstag, 1. Oktober 2020 16:33:02 UTC+2 schrieb Henk Tijdink:
>
>
> In PTGUI is the lens in te database.
> It gives the following values for the Meike lens. This for the Jpeg files 
> from the camera
> F  theoretic          6,5 mm                     After optimizing are the 
> lens parameters
> Practical              6,66 mm                   a= -0,093           and 
> sensor shift.
> Fov degrees         181,01                       b=  0,18              d= 
> -0,18%
> Fisheye factor    -0,824152                 c= -0,11               e= 
> -0,17%
>
 

>
> Is it possible to "translate" the lens parameters of this from the PTGUI 
> database to hugin? 
>

This is not so easy. PTGUI fisheye factor does not translate 1:1 to a 
projection of libpano. The fisheye factor of -0.824 would result in 
something between orthographic and equisolid projection (see 
https://wiki.panotools.org/Fisheye_Projection).
The next pitfall is the fov: PTGUI calculates the fov to the cropped 
circle, libpano/Hugin is using the horizontal dimension of the full image 
(see https://wiki.panotools.org/Panotools_internals#Cropping ). 

I had a look at your pto file. If I remove the control points in the nadir 
area it optimizes nicely. Without the images it is difficult to give 
further advices, but I would check the control points in the nadir area 
(maybe some repetitive pattern has confused the control point finder) and 
then try again.

Thomas

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/37ce77a9-40f9-4f2e-b10b-0d988dd88271o%40googlegroups.com.

Reply via email to