YOLO architecture concept in Computer Vision - Model Metrics & Evaluation

Metrics & Evaluation - YOLO architecture concept

Which metric matters for YOLO and WHY

YOLO is used for object detection. It finds objects and draws boxes around them. The key metrics are Precision, Recall, and Mean Average Precision (mAP).

Precision tells us how many detected boxes are correct. High precision means few false alarms.

Recall tells us how many real objects were found. High recall means few missed objects.

mAP combines precision and recall over all object classes and detection thresholds. It shows overall detection quality.

We want a balance: find most objects (high recall) and be accurate (high precision).

Confusion matrix for object detection (simplified)

          | Detected Object | No Object Detected
    ------|-----------------|------------------
    Object Present | True Positive (TP) | False Negative (FN)
    No Object     | False Positive (FP) | True Negative (TN)
    

For YOLO, TP means correctly detected objects. FP means boxes where no object exists. FN means missed objects. TN is less used because background is large.

Precision vs Recall tradeoff with examples

If YOLO is set to be very strict, it detects fewer boxes but most are correct. This means high precision but low recall. It misses some objects but has few false alarms.

If YOLO is set to detect many boxes, it finds most objects (high recall) but also many wrong boxes (low precision).

Example: In self-driving cars, missing a pedestrian (low recall) is dangerous, so recall is more important. In a photo app tagging objects, false alarms (low precision) annoy users more.

What good vs bad metric values look like for YOLO

Good: Precision and recall above 0.8, mAP above 0.7 means YOLO detects most objects correctly.

Bad: Precision or recall below 0.5 means many false alarms or many missed objects. mAP below 0.4 shows poor detection.

Very high precision but very low recall means many objects are missed. Very high recall but low precision means many false boxes.

Common pitfalls in YOLO metrics

• Accuracy paradox: High accuracy can be misleading if most images have no objects.
• Data leakage: Testing on images similar to training can inflate metrics.
• Overfitting: Very high training mAP but low test mAP means model memorizes training data.
• Ignoring IoU threshold: Detection counts only if box overlaps enough with true object (IoU). Wrong threshold skews metrics.

Self-check question

Your YOLO model has 98% accuracy but only 12% recall on detecting pedestrians. Is it good for safety?

Answer: No. The model misses 88% of pedestrians (low recall). This is dangerous for safety. High accuracy is misleading because most image parts have no pedestrians.

Key Result

For YOLO, balancing precision and recall with a high mAP is key to good object detection.

Practice

1. What is the main idea behind the YOLO architecture in object detection?

easy

A. It looks at the whole image once to find objects quickly.

B. It scans the image pixel by pixel for objects.

C. It uses multiple passes over the image to improve accuracy.

D. It only detects one object per image.

Solution

1. Step 1: Understand YOLO's detection approach

   YOLO processes the entire image in one go instead of scanning parts multiple times.

2. Step 2: Compare options with YOLO's method

   Only It looks at the whole image once to find objects quickly. correctly states that YOLO looks at the whole image once for fast detection.

3. Final Answer:

   It looks at the whole image once to find objects quickly. -> Option A

4. Quick Check:

   YOLO = single pass detection [OK]

Hint: YOLO means one look at the image for all objects [OK]

Common Mistakes:

• Thinking YOLO scans pixel by pixel slowly
• Believing YOLO needs multiple passes
• Assuming YOLO detects only one object

2. Which of the following correctly describes how YOLO divides the input image?

easy

A. It splits the image into a grid of cells.

B. It divides the image into overlapping circles.

C. It processes the image as a single pixel vector.

D. It uses random patches of the image.

Solution

1. Step 1: Recall YOLO's image division method

   YOLO splits the image into a grid of cells to predict bounding boxes and classes per cell.

2. Step 2: Match options with this method

   Only It splits the image into a grid of cells. correctly states the grid division; others describe incorrect or unrelated methods.

3. Final Answer:

   It splits the image into a grid of cells. -> Option A

4. Quick Check:

   YOLO grid division = grid cells [OK]

Hint: YOLO uses grid cells, not random or circular parts [OK]

Common Mistakes:

• Confusing grid cells with overlapping circles
• Thinking YOLO processes pixels individually
• Believing YOLO uses random image patches

3. Given a YOLO model that divides an image into a 7x7 grid and predicts 2 boxes per cell, how many total bounding boxes does it predict?

medium

A. 14

B. 98

C. 49

D. 7

Solution

1. Step 1: Calculate total grid cells

   The grid is 7x7, so total cells = 7 * 7 = 49.

2. Step 2: Multiply by boxes per cell

   Each cell predicts 2 boxes, so total boxes = 49 * 2 = 98.

3. Final Answer:

   98 -> Option B

4. Quick Check:

   7x7x2 = 98 boxes [OK]

Hint: Multiply grid cells by boxes per cell [OK]

Common Mistakes:

• Multiplying grid size by 2 incorrectly
• Using 7 or 14 instead of total boxes
• Confusing grid cells with boxes

4. You wrote code to split an image into a 3x3 grid for YOLO, but your model predicts only 3 boxes total instead of 18. What is the likely error?

medium

A. You predicted 6 boxes per cell instead of 2.

B. You used a 1x3 grid instead of 3x3.

C. You predicted only 1 box per cell instead of 2.

D. You forgot to multiply grid cells by boxes per cell.

Solution

1. Step 1: Calculate expected boxes

   3x3 grid = 9 cells; with 2 boxes per cell, expected boxes = 9 * 2 = 18.

2. Step 2: Identify cause of only 3 boxes predicted

   Getting 3 boxes means only 1 box per cell was predicted instead of 2.

3. Final Answer:

   You predicted only 1 box per cell instead of 2. -> Option C

4. Quick Check:

   Grid cells x boxes per cell = total boxes [OK]

Hint: Check boxes predicted per cell [OK]

Common Mistakes:

• Assuming wrong grid size
• Confusing boxes per cell count
• Ignoring multiplication step

5. In a real-time traffic camera system using YOLO, why is YOLO preferred over other detection methods?

hard

A. Because YOLO ignores small objects, reducing processing time.

B. Because YOLO requires multiple passes for higher accuracy, which is faster.

C. Because YOLO only detects one object type at a time, simplifying output.

D. Because YOLO processes the entire image quickly in one pass, enabling fast detection.

Solution

1. Step 1: Understand YOLO's speed advantage

   YOLO looks at the whole image once, making it very fast for real-time detection.

2. Step 2: Compare with other methods

   Other methods often scan multiple times or use slower region proposals, making YOLO better for live video.

3. Final Answer:

   Because YOLO processes the entire image quickly in one pass, enabling fast detection. -> Option D

4. Quick Check:

   YOLO = fast single pass detection [OK]

Hint: YOLO's one-pass speed suits real-time needs [OK]

Common Mistakes:

• Thinking multiple passes are faster
• Believing YOLO ignores small objects
• Assuming YOLO detects only one object type