Feature matching between images in Computer Vision - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a SIFT feature detector.

Computer Vision

import cv2
sift = cv2.[1]()

Drag options to blanks, or click blank then click option'

ABRISK_create

BFeatureDetector_create

CORB_create

DSIFT_create

Attempts:

3 left

💡 Hint

Common Mistakes

Using ORB or BRISK instead of SIFT.

Trying to use a generic FeatureDetector_create method.

The correct method to create a SIFT detector in OpenCV is SIFT_create().

2fill in blank

medium

Complete the code to detect keypoints and compute descriptors from an image using SIFT.

Computer Vision

keypoints, descriptors = sift.[1](image, None)

Drag options to blanks, or click blank then click option'

AdetectAndCompute

Bdetect

Ccompute

DfindKeypoints

Attempts:

3 left

💡 Hint

Common Mistakes

Using only detect or compute separately.

Using a non-existent method like findKeypoints.

The detectAndCompute method detects keypoints and computes descriptors in one step.

3fill in blank

hard

Fix the error in the code to create a BFMatcher with L2 norm for SIFT descriptors.

Computer Vision

bf = cv2.BFMatcher([1], crossCheck=True)

Drag options to blanks, or click blank then click option'

Acv2.NORM_INF

Bcv2.NORM_HAMMING

Ccv2.NORM_L2

Dcv2.NORM_MINMAX

Attempts:

3 left

💡 Hint

Common Mistakes

Using NORM_HAMMING which is for binary descriptors like ORB.

Using incorrect norm types.

SIFT descriptors are float vectors, so the correct norm type is cv2.NORM_L2.

4fill in blank

hard

Fill both blanks to filter matches using Lowe's ratio test.

Computer Vision

good_matches = []
for m, n in matches:
    if m.[1] < [2] * n.distance:
        good_matches.append(m)

Drag options to blanks, or click blank then click option'

Adistance

B0.75

C0.5

DqueryIdx

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong attributes like queryIdx.

Using incorrect ratio values.

Lowe's ratio test compares the distance of the best match to the second best match using the distance attribute and a ratio threshold like 0.75.

5fill in blank

hard

Fill all three blanks to draw matches between two images.

Computer Vision

img_matches = cv2.drawMatches(img1, kp1, img2, kp2, [1], None, flags=[2])
cv2.imshow('Matches', img_matches)
cv2.waitKey([3])

Drag options to blanks, or click blank then click option'

Agood_matches

Bcv2.DrawMatchesFlags_NOT_DRAW_SINGLE_POINTS

C0

Dmatches

Attempts:

3 left

💡 Hint

Common Mistakes

Using all matches instead of good matches.

Not using the correct flag.

Using a non-zero waitKey value.

To draw only good matches, pass good_matches. The flag cv2.DrawMatchesFlags_NOT_DRAW_SINGLE_POINTS hides unmatched keypoints. cv2.waitKey(0) waits indefinitely for a key press.

Practice

1. What is the main purpose of feature matching between two images?

easy

A. To find similar points or patterns between the images

B. To change the colors of the images

C. To increase the image resolution

D. To crop the images automatically

Solution

1. Step 1: Understand feature matching concept

   Feature matching is used to find points in two images that look alike, such as corners or edges.

2. Step 2: Identify the main goal

   The goal is to find these similar points to compare or align images, not to change colors or resolution.

3. Final Answer:

   To find similar points or patterns between the images -> Option A

4. Quick Check:

   Feature matching = find similar points [OK]

Hint: Feature matching finds points that look alike in two images [OK]

Common Mistakes:

• Confusing feature matching with image editing
• Thinking it changes image size or colors
• Mixing feature matching with image cropping

2. Which of the following is the correct way to detect keypoints using ORB in OpenCV (Python)?

easy

A. orb = cv2.ORB_create(); keypoints = orb.getKeypoints(image)

B. orb = cv2.ORB(); keypoints = orb.find(image)

C. orb = cv2.ORB_create(); keypoints = orb.detect(image, None)

D. orb = cv2.ORB_create(); keypoints = orb.findKeypoints(image)

Solution

1. Step 1: Recall ORB keypoint detection syntax

   In OpenCV, ORB keypoints are detected using orb = cv2.ORB_create() and orb.detect(image, None).

2. Step 2: Check each option

   orb = cv2.ORB_create(); keypoints = orb.detect(image, None) matches the correct syntax; others use incorrect method names or constructors.

3. Final Answer:

   orb = cv2.ORB_create(); keypoints = orb.detect(image, None) -> Option C

4. Quick Check:

   Correct ORB syntax = orb = cv2.ORB_create(); keypoints = orb.detect(image, None) [OK]

Hint: Use ORB_create() and detect() to find keypoints [OK]

Common Mistakes:

• Using wrong method names like findKeypoints
• Calling ORB() instead of ORB_create()
• Passing wrong arguments to detect()

3. Given the following code snippet, what will be the output length of good_matches?

import cv2
orb = cv2.ORB_create()
kp1, des1 = orb.detectAndCompute(img1, None)
kp2, des2 = orb.detectAndCompute(img2, None)
matcher = cv2.BFMatcher(cv2.NORM_HAMMING)
matches = matcher.knnMatch(des1, des2, k=2)
good_matches = []
for m, n in matches:
    if m.distance < 0.75 * n.distance:
        good_matches.append(m)
print(len(good_matches))

medium

A. Total number of keypoints in img2

B. Number of matches passing the ratio test

C. Total number of keypoints in img1

D. Total number of all matches found

Solution

1. Step 1: Understand knnMatch and ratio test

   knnMatch finds the two best matches for each descriptor. The ratio test keeps matches where the best is significantly better than the second best.

2. Step 2: Analyze the code logic

   The loop filters matches by distance ratio, so good_matches contains only those passing the test, not all matches or keypoints.

3. Final Answer:

   Number of matches passing the ratio test -> Option B

4. Quick Check:

   good_matches length = matches passing ratio test [OK]

Hint: Ratio test filters matches; good_matches count = filtered matches [OK]

Common Mistakes:

• Confusing matches with keypoints count
• Thinking good_matches includes all matches
• Ignoring the ratio test condition

4. Identify the error in this feature matching code snippet:

import cv2
orb = cv2.ORB_create()
kp1, des1 = orb.detectAndCompute(img1, None)
kp2, des2 = orb.detectAndCompute(img2, None)
matcher = cv2.BFMatcher(cv2.NORM_L2)
matches = matcher.match(des1, des2)
print(len(matches))

medium

A. Using cv2.NORM_L2 with ORB descriptors is incorrect

B. Missing call to detect() before detectAndCompute()

C. BFMatcher should be replaced with FlannBasedMatcher

D. match() requires k parameter for ORB descriptors

Solution

1. Step 1: Check descriptor type and matcher norm

   ORB descriptors are binary, so BFMatcher should use cv2.NORM_HAMMING, not NORM_L2.

2. Step 2: Identify the error

   Using NORM_L2 causes incorrect distance calculation and poor matching for ORB.

3. Final Answer:

   Using cv2.NORM_L2 with ORB descriptors is incorrect -> Option A

4. Quick Check:

   ORB needs NORM_HAMMING, not NORM_L2 [OK]

Hint: Use NORM_HAMMING with ORB descriptors [OK]

Common Mistakes:

• Using wrong norm type for binary descriptors
• Thinking detect() is needed before detectAndCompute()
• Confusing BFMatcher with FlannBasedMatcher

5. You want to match features between two images taken from different angles. Which approach improves matching accuracy the most?

hard

A. Use ORB detector without any filtering on matches

B. Resize images to very small size before matching

C. Use random keypoints and brute force matching

D. Use SIFT detector and apply Lowe's ratio test on matches

Solution

1. Step 1: Consider feature detector choice

   SIFT is robust to scale and rotation changes, better for different angles than ORB or random points.

2. Step 2: Apply filtering for accuracy

   Lowe's ratio test filters out weak matches, improving accuracy significantly.

3. Step 3: Evaluate other options

   Using ORB without filtering or random points reduces accuracy; resizing too small loses details.

4. Final Answer:

   Use SIFT detector and apply Lowe's ratio test on matches -> Option D

5. Quick Check:

   SIFT + ratio test = best accuracy [OK]

Hint: SIFT + Lowe's ratio test improves matching accuracy [OK]

Common Mistakes:

• Skipping ratio test filtering
• Using random or weak keypoints
• Reducing image size too much