Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

detector.detectAndCompute()Why is it time-consuming to start?

detector = cv.ORB_create() norm = cv.NORM_HAMMING matcher = cv.BFMatcher(norm) kp1, desc1 = detector.detectAndCompute(img1, None) kp2, desc2 = detector.detectAndCompute(img2, None) matches = matcher.knnMatch(desc1, trainDescriptors=desc2, k=2)

detector.detectAndCompute()Time consuming? Why is the first matching time-consuming and the subsequent image matching time-consuming?

detector.detectAndCompute()Why is it time-consuming to start?

detector = cv.ORB_create() norm = cv.NORM_HAMMING matcher = cv.BFMatcher(norm) kp1, desc1 = detector.detectAndCompute(img1, None) kp2, desc2 = detector.detectAndCompute(img2, None) matches = matcher.knnMatch(desc1, trainDescriptors=desc2, k=2)

detector.detectAndCompute()Time consuming? Why is the first matching time-consuming and the subsequent image matching time-consuming?

detector.detectAndCompute()Why is it time-consuming to start?

detector = cv.ORB_create() norm = cv.NORM_HAMMING matcher = cv.BFMatcher(norm) kp1, desc1 = detector.detectAndCompute(img1, None) kp2, desc2 = detector.detectAndCompute(img2, None) matches = matcher.knnMatch(desc1, trainDescriptors=desc2, k=2)

detector.detectAndCompute()Time consuming? Why is the first matching time-consuming and the subsequent image matching time-consuming?

detector.detectAndCompute()Why is it time-consuming to start?

Here is snippet code:

detector = cv.ORB_create()
 norm = cv.NORM_HAMMING
 matcher = cv.BFMatcher(norm)
 kp1, desc1 = detector.detectAndCompute(img1, None)
 kp2, desc2 = detector.detectAndCompute(img2, None)
 matches = matcher.knnMatch(desc1, trainDescriptors=desc2, k=2)

k=2)

detector.detectAndCompute()Time consuming? Why is the first matching time-consuming and the subsequent image matching time-consuming?

detector.detectAndCompute()Why is it time-consuming to start?

Here is snippet code:

detector = cv.ORB_create()
norm = cv.NORM_HAMMING
matcher = cv.BFMatcher(norm)
kp1, desc1 = detector.detectAndCompute(img1, None)
kp2, desc2 = detector.detectAndCompute(img2, None)
matches = matcher.knnMatch(desc1, trainDescriptors=desc2, k=2)

detector.detectAndCompute()Time detector.detectAndCompute()Time consuming? Why is the first matching time-consuming and the subsequent image matching time-consuming?