Hi Thomas,
On 26/06/2024 19:21, 'T. Modes' via hugin and other free panoramic
software wrote:
Hi
[email protected] schrieb am Mittwoch, 26. Juni 2024 um 18:16:34 UTC+2:
> The main problem is that you optimize yaw of all images:
> pto_var -o project2 --opt y0,r,y,..
> Because you have not other constraints like vertical control
point the
> optimizer result is ambiguous and the pano can easily slide to
left or
> right.
I see, that makes sense then. The material that is being photographed
moves around ever so slightly, and because one pixel is about 3.76 μm I
found that I had to also adjust for the roll and yaw. Would there be a
way to tell it to not change/optimise the yaw by more than (say) a few
degrees? That could prove to be quite helpful.
No, there are no such constraints possible.
Maybe drop the optimization of y0 and call pano_modify --center after
the optimization to bring the pano back to the center.
Understood, thanks.
> PS: Hugin has also possibilities to handle such use cases.
> First assign rough image positions according to your layout.
Either with
> a template (pto_template) or with numbers/expressions (pto_var).
> Then run cpfind --prealigned ... on this project file. Then
cpfind looks
> only at overlapping images. So no need to reinvent the wheel twice.
The reasons I made a custom control pointer finder is that (1) cpfind
wouldn't find control points in cases where I really expected it to
find
control points (also with different sieve1/sieve2 sizes) and
You are using very high number for sieve1width/height. This could also
slow down the processing.
That is right -- I added that at some point to try to get a higher
success rate, but given that the template approach is working for me now
I might be able to get rid of that.
(2) because
cpfind is relatively slow for the images (151 megapixel times 16)
that I
am working with, even if things are prealigned (as I understand it).
After automatically stitching 10000+ images I'm very close to a 100%
success rate, but I couldn't quite get there with just cpfind.
I didn't figure out how to use pto_template make a template with
pre-aligned images. Is there any documentation available on how to
do this?
Take a project file of a finished pano with the same layout. Then use
this project file as template for another project file with the same
layout (and same number of images).
And then use cpfind --prealigned on this project.
With the above advice I got this to work. If only I understood
previously that templates were this simple. I ended up making four
templates for the four different setups that I have and now I've been
able to stitch all the remaining images by falling back to cpfind
--prealigned when my ORB stitching doesn't work.
Really appreciate the help!
Regards,
Merlijn
--
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/86b80449-ec82-480e-903a-1a49b2a99246%40archive.org.
