[email protected] schrieb am Dienstag, 25. Juni 2024 um 20:00:49 UTC+2:

The Python code that I have written can be found here [2]. 


Sorry, but this unnecessary complicated. I had to dig deep into your script 
to found the Hugin commands you use. It would be easier if you would have 
only cited your used commands.

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.

The best advice is to look at the intermediate project files in the GUI and 
see the result.

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.

Thomas

-- 
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/2ebc51be-22ae-4bea-bcb5-0ceb0025e94en%40googlegroups.com.
  • [hugin-ptx] Field o... Merlijn B.W. Wajer
    • [hugin-ptx] Re... 'T. Modes' via hugin and other free panoramic software
      • Re: [hugin... Merlijn B.W. Wajer
        • Re: [h... 'T. Modes' via hugin and other free panoramic software
          • Re... Merlijn B.W. Wajer
        • Re: [h... 'T. Modes' via hugin and other free panoramic software

Reply via email to