Why processing prepares images for analysis in Computer Vision - Why Metrics Matter

Metrics & Evaluation - Why processing prepares images for analysis

Which metric matters for this concept and WHY

When preparing images for analysis, the key metric to watch is model accuracy. This shows how well the model understands the processed images. Proper image processing helps improve accuracy by making images clearer and more consistent for the model.

Confusion matrix or equivalent visualization (ASCII)

      +---------------------+
      |       Confusion      |
      |       Matrix        |
      +---------+-----------+
      |         | Predicted |
      | Actual  |  Cat | Dog |
      +---------+------+-----+
      | Cat     |  45  |  5  |
      | Dog     |  3   | 47  |
      +---------+------+-----+
    

This matrix shows how well the model classifies images after processing. Better processing usually means fewer mistakes (off-diagonal numbers).

Precision vs Recall tradeoff with concrete examples

Precision means when the model says an image is a cat, how often it is really a cat. Recall means how many of all cat images the model correctly finds.

Good image processing helps both precision and recall by reducing noise and highlighting important features.

Example: If images are blurry, recall might drop because the model misses cats. If images have distracting backgrounds, precision might drop because the model confuses dogs for cats.

What "good" vs "bad" metric values look like for this use case

Good: Accuracy above 90%, precision and recall both above 85%. This means the model correctly identifies most images and makes few mistakes.

Bad: Accuracy below 70%, or precision and recall below 60%. This suggests poor image processing or noisy data causing confusion.

Metrics pitfalls

• Accuracy paradox: High accuracy can be misleading if classes are unbalanced (e.g., mostly dog images).
• Data leakage: Using test images in training can falsely boost metrics.
• Overfitting indicators: Very high training accuracy but low test accuracy means the model memorizes images instead of learning features.
• Poor preprocessing: Not resizing or normalizing images can confuse the model and lower metrics.

Self-check question

Your image classification model has 98% accuracy but only 12% recall on the cat class. Is it good for production? Why or why not?

Answer: No, it is not good. The model misses most cat images (low recall), even if overall accuracy is high. This means it fails to find many cats, which is a serious problem if cats are important to detect.

Key Result

Proper image processing improves model accuracy by making images clearer and more consistent, leading to better precision and recall.

Practice

1. Why do we convert images to grayscale before analysis in many computer vision tasks?

easy

A. To reduce the amount of data and simplify processing

B. To add color information for better accuracy

C. To increase the image size for detailed analysis

D. To make the image brighter and easier to see

Solution

1. Step 1: Understand grayscale conversion

   Converting to grayscale reduces the image from three color channels (RGB) to one channel, lowering data size.

2. Step 2: Recognize impact on processing

   Less data means faster and simpler analysis without losing important shape or texture information.

3. Final Answer:

   To reduce the amount of data and simplify processing -> Option A

4. Quick Check:

   Grayscale reduces data size = A [OK]

Hint: Grayscale means less data, easier analysis [OK]

Common Mistakes:

• Thinking grayscale adds color details
• Believing grayscale increases image size
• Confusing brightness adjustment with grayscale

2. Which of the following Python code snippets correctly resizes an image using OpenCV?

easy

A. resized = cv2.resize(image, (100))

B. resized = cv2.resize(image, 100, 100)

C. resized = cv2.resize(image, size=(100, 100))

D. resized = cv2.resize(image, (100, 100))

Solution

1. Step 1: Check OpenCV resize syntax

   The correct syntax requires the second argument as a tuple for size: (width, height).

2. Step 2: Validate each option

   resized = cv2.resize(image, (100, 100)) uses cv2.resize(image, (100, 100)) which is correct. Others have wrong argument formats.

3. Final Answer:

   resized = cv2.resize(image, (100, 100)) -> Option D

4. Quick Check:

   Resize needs tuple size = D [OK]

Hint: Resize needs size as (width, height) tuple [OK]

Common Mistakes:

• Passing size as separate arguments
• Using keyword 'size' which is invalid
• Passing a single integer instead of tuple

3. What will be the output shape of the image after this code runs?

import cv2
image = cv2.imread('photo.jpg')
resized = cv2.resize(image, (64, 64))
gray = cv2.cvtColor(resized, cv2.COLOR_BGR2GRAY)
print(gray.shape)

medium

A. (64, 64, 3)

B. (3, 64, 64)

C. (64, 64)

D. (128, 128)

Solution

1. Step 1: Analyze resizing step

   The image is resized to 64x64 pixels with 3 color channels initially.

2. Step 2: Analyze grayscale conversion

   Converting to grayscale removes color channels, leaving a 2D array of shape (64, 64).

3. Final Answer:

   (64, 64) -> Option C

4. Quick Check:

   Grayscale image shape = (height, width) = B [OK]

Hint: Grayscale images have 2D shape, no color channels [OK]

Common Mistakes:

• Assuming grayscale keeps 3 channels
• Confusing shape order (channels first vs last)
• Ignoring resize effect on dimensions

4. The following code is intended to normalize an image's pixel values to the range 0 to 1. What is the error?

normalized = image / 255

medium

A. Division by 255 is correct; no error

B. Image must be converted to float before division

C. Should multiply by 255 instead of dividing

D. Normalization requires subtracting mean, not dividing

Solution

1. Step 1: Understand data type impact

   If image is integer type, dividing by 255 does integer division, resulting in zeros.

2. Step 2: Fix with float conversion

   Convert image to float type before division to get decimal normalized values.

3. Final Answer:

   Image must be converted to float before division -> Option B

4. Quick Check:

   Integer division causes zero values = A [OK]

Hint: Convert to float before dividing pixel values [OK]

Common Mistakes:

• Ignoring data type before division
• Thinking multiplying normalizes pixels
• Confusing normalization with mean subtraction

5. You have a dataset of images with different sizes and color formats. Which sequence of processing steps best prepares them for a neural network model expecting 64x64 grayscale inputs normalized between 0 and 1?

hard

A. Resize to 64x64, convert to grayscale, convert to float, divide by 255

B. Convert to grayscale, resize to 64x64, divide by 255, convert to float

C. Divide by 255, resize to 64x64, convert to grayscale, convert to float

D. Convert to grayscale, divide by 255, resize to 64x64, convert to float

Solution

1. Step 1: Resize before color conversion

   Resizing first ensures consistent image size for the model input.

2. Step 2: Convert to grayscale and normalize

   Convert to grayscale to reduce channels, then convert to float and divide by 255 to normalize pixel values between 0 and 1.

3. Final Answer:

   Resize to 64x64, convert to grayscale, convert to float, divide by 255 -> Option A

4. Quick Check:

   Resize -> Grayscale -> Float -> Normalize = C [OK]

Hint: Resize first, then grayscale, then float and normalize [OK]

Common Mistakes:

• Normalizing before float conversion
• Changing order of resize and grayscale incorrectly
• Skipping float conversion before normalization