Hi,
When stitching thousands of pano with my script, sometimes I have some
broken pano. The reasons for these failures vary, but It usually ends up
with totally wrong values for lens FOV or yaw/pitch/roll.
For example, if I indicate that the FOV of a lens is 125°, and Hugin
finds that the best solution is 50°, it can't be correct.
If I indicate a yaw of 90°, a final result of -30° is necessarily incorrect.
I can parse the final pto file to detect if the pano is wrong, but I was
wondering if Hugin could not integrate a function to limit the amplitude
of variations of a parameter which would reduce the number of failed pano.
Just an idea
Best,
Stéphane
--
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/5b86eb5f-f490-6421-1b26-a12df5984d92%40wanadoo.fr.
