Hi Thomas,
Thank you for the quick response - I have replied inline.
On 11/04/2025 16:13, 'T. Modes' via hugin and other free panoramic
software wrote:
[email protected] schrieb am Freitag, 11. April 2025 um 12:59:45 UTC+2:
Which brings me to my two questions:
1. Is there a way to naively define an offset for an image with respect
to another image when there are no control points? I suppose I could
write an estimated TrX and TrY in the 'image lines' portion of the
pto -
but without any control points, I suspect the images will still be seen
as 'not connected'. Should I insert some synthetic (but hopefully semi
accurate) control points? Will that work, or will those get
discarded by
say cpclean?
Hugin has already the geocpset tool https://wiki.panotools.org/Geocpset
to set some kind of dummy control points to keep these featureless
images in connection to its surrounding images during optimisation.
It needs some rough positions of the images. This should be possible in
your use case with the 4x4 grid. See also https://wiki.panotools.org/
Hugin_Panorama_Workflow for another example.
But don't run cpclean afterwards. (First run cpclean and then geocpset,
not vice versa.)
This was exactly what I was looking for, thank you!
It took me a bit of time to integrate this in my workflow, but now that
I got it working I am quite happy with it. I ended up using pto_template
with cpfind --prealigned, falling back geocpset if I was sure the
template was good enough (sometimes I stitch items in batches that go
through more or less the exact same motions, and the first item having
enough control points makes me confident enough that the rest will have
gone through similar motions, so I can use the first item as template).
One thing that I did run into with the above approach was that geocpset
wouldn't set points for an image if it is already linked to any image -
even if there are multiple image groups. Say there are two groups:
[0,1,2,3,4,5,6,7,8,9,11] and [12,13,14,15] - then geocpset doesn't link
the two groups.
All of that makes sense from geocpset's point of view, but I wanted
geocpset to supplement the regular control points. So to work around
this I ended up writing some custom code that removes control points of
all images in groups (except for the latest group), and then run
geocpset. This way images that are connected by regular control points
are untouched, but the images that have no control points that connect
them to main group get synthetic control points set. (And of course this
approach is only used if regular cpfind runs into trouble)
(I went with the pto_template approach because I couldn't easily figure
out how to map the pto_var set formula options to the 'real world'
movements (in millimeter) that my XY stage makes.)
Thanks again,
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 visit
https://groups.google.com/d/msgid/hugin-ptx/e8fe19ab-888e-4888-b86e-8c5e70142085%40archive.org.
