On Sun 17-May-2015 at 12:53 -0700, Steinar Midtskogen wrote:

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

This results in g=-749 t=999 which are extremely/improbably large values for any normal situation.

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?

Usually g & t are not optimised at the same time because they tend to cancel each other out - you end up with some rotation and asymmetrical scaling. Have you tried optimising 'v' angle of view instead?

--
Bruno

--
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/20150518221409.GC27263%40postle.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to