match() & knnMatch(): same trainIdx for different queryIdx

asked 2020-03-09 13:30:44 -0600

Is it possible that match() & knnMatch() have the same trainIdx for different different queryIdx? If so, do we need to handle such a situation? And how?

edit retag flag offensive close merge delete