On 21 February 2019 14:10:41 CET, jim cullen wrote:
>
>I can't seem to make it fix the roll and pitch at zero successfully during
>optimization.
>
>I'm setting the fast preview mode to Mosaic plane - is that proper? I ask
>because the python script
>stitch-scanned-images.py which one can find on github constructs a .pto
>that seems to use Panosphere.
Hugin has so many options that you can do this scanned images thing in three
completely different ways. I'm wary of prescribing a particular method over
another, but you can't mix them. They are:
1. Using very narrow field of view, with roll, pitch, yaw optimisation.
Imagine that you have taken these images using a very long telescope, Hugin
will let you stitch them like a 'normal' panorama, as long as you set the field
of view to a small number (<1°).
The result won't be perfectly correct, and there will be odd curvatures, but
for most purposes you can get away with this.
2. Using the d,e lens shift parameters to move the images around a rectilinear
'canvas'.
These shift parameters are intended to let you work with photos created with a
shift lens, or photos where one or more sides have been cropped away (nearly
all historical/Victorian/magazine photos are uncentred like this).
So you can stitch scans by pretending that they are all the same photo, each
just cropped differently.
3. The 'mosaic' XYZ mode has been added to Hugin specifically for fitting
images to a rectilinear plane, so this is what we recommend, but it is a
powerful tool that can do lots more than stitching scans, so it is conceptually
a bit harder.
The mosaic mode assumes that your camera moves to different 3D locations for
reach shot, hence the XYZ positions.
It is possible to conceive of your scans as being taken by a camera from
different locations, but with the Z distance (the distance from the camera to
the object) never changing, and your 'camera' is always perfectly
perpendicular, so pitch and yaw are always zero.
>I'm now setting the first cols of the optimize panel to unchecked and zero
>for yaw and pitch and leaving
>the roll free (checked). The script (edit prior to optimize lets me look)
>seems to have sane vars viz
>Tx Ty and r for each image.
This is correct for method 3.
>I must be blundering some place else as it
>keeps saying Panorama must have positive height.
>I think this is from the "batch" side of things during optimization.
I've have no idea how this happens.
>I only get the option to set these things if I select Custom on the
>geometric optimization pull down. Is that
>the place to set the vars to participate in optimization?
Yes, I would set 'custom' geometric optimisation, and control everything from
the Optimiser tab (for methods 2 & 3).
--
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/7CF8818D-08E1-46CC-B919-320BA64FF7EE%40postle.net.
For more options, visit https://groups.google.com/d/optout.
