I originally posted this on the PanoToolsNG list, but it was suggested that 
I take it here instead:

I'm using autooptimiser to map pixel positions to azimuth and altitude. 
That is, I'm only using a single image plus a dummy 360x180 degree 
equirectangular image (which has a direct mapping between az, alt and x, 
y). I do this by tracking stars, plate solving (star identification) and 
use the results as control points.

The result is a .pto file like this: http://voksenlia.net/test/lens.pto

Running autooptimiser like this: autooptimiser -n lens.pto -o lens2.pto

gives me a reasonable result, which I've visualised here: 
http://voksenlia.net/test/grid.jpg

However, if I in the lens.pto file above comment out "v g0" and "v t0", the 
result is always very bad: http://voksenlia.net/test/grid2.jpg

The lens is a (full frame) fisheye lens. Do the g t parameters have a 
special meaning in this case, and must be included in the optimisation?

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ef28a252-9713-4cf3-98c8-96e58c043b05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to