Hi, Am Samstag, 30. Mai 2020 16:19:56 UTC+2 schrieb LF Martins: > > This I can't reproduced. When only the variables of the second images are > marked for optimisation, then only the variables of second images are > modified. > > > No, I meant that even if only one image is set to be optimized using > pt_var, the values differ a lot. Especially if there are more than two > images. If you use my project you will see that if only the second (after > the anchor) is optimized using autooptimiser -n, and then only the third, > the resulted values are way different then doing this with the GUI. >
This is a side effect of optimising all images. Then also the control points of the disabled images are active. You have control points between all image pairs: 0-1, 1-2 and 0-2. So you have different constraints for image 1 (match to image 0 and to image 2). When you only optimise image 1, the optimiser have to find a solution with suits both constraints. This solution is different if only one constraint is active - like image 2 disabled and option "optimise only active images" active. > > I do appreciate the changes, thank you a lot. But is there any any to > reproduce the GUI behaviour (meaning the resulting optimized values are the > same) now? > > With the new switch the command line "autooptimiser -n --only-active-images" should behave the same way as the GUI with option "optimise only active images" active. 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/59131892-edb9-4860-82f3-9299d57f54f3%40googlegroups.com.
