Ask Your Question

Revision history [back]

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

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?