Since every control point connects only two images, it's normal and reasonable that you have more CPs in the intersection of 4 images. Every CP generates constraints on the relative position of two images.
In Hugin++ you could set weights for control points. However, this should in most cases only be necessary when you have "good" CPs and "bad" CPs (e.g. due to moving objects) and you have no other choice but keeping some of the "bad" CPs. Then you can assign higher weights for good CPs and/or lower weights for bad CPs. michae...@mac.com schrieb am Freitag, 29. April 2022 um 14:54:49 UTC+2: > Is there not a bias in the way Hugin optimises; that control points at the > intersection of four images will be weighted three more times than those at > the intersection of the pair of images above or below? The larger error in > control points always tend to be the furthest from the centre. > > Without manually adding control points away from the 4-way intersection > (or removing those in the centre), is there some way to compensate for this > with cpfind or autooptimiser? > > (Hoping the attached image posts) > -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/f7a77ff3-5d14-4620-ad57-2806ad7967fcn%40googlegroups.com.
