range_width having no effect in FeatureMatcher?

Hi, I’m trying to stitch a sequence of images that I know are adjacent, and I thought I understood setting range_width to 1 when matching might improve results, but it doesn’t seem to have any effect. Perhaps I have misunderstood how this parameter works, but it doesn’t seem to be doing anything from what I can tell.

I tried taking a fresh copy of Stitching Tutorial.ipynb and changing the range_width parameter in the matching section, and I still get a full matrix of confidence values for every pair of images no matter what value I choose – I expected that setting it to 1 would force it to only consider adjacent pairs (e.g. pair 1-2 would have a confidence but pair 1-3 would not). That’s what the C++ code seems to be doing, but I admit I haven’t dug deeply enough into it.

Here’s my results:

You can see on the final block that under the hood the type is being set to cv2.detail.BestOf2NearestRangeMatcher correctly.

Do you have any suggestions, or have I misunderstood how this is supposed to work? If I manually set the confidence of non-adjacent images to zero then I get a better stitching result in later stages, but I was hoping for a significant performance increase of comparing fewer images too. Thanks!

[chinery]

(p.s. if you do run into any more issues with the C++ code or Python bindings feel free to message me, can’t promise anything but I can take a look!)

[lukasalexanderweber]

Thank you! This is something that has been bugging me for some time. Unfortunately I have zero C++ experience and am somewhat dependent on the Python wrappers and docs.