Bird
Raised Fist0
Computer Visionml~8 mins

Morphological operations (erosion, dilation, opening, closing) in Computer Vision - Model Metrics & Evaluation

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Metrics & Evaluation - Morphological operations (erosion, dilation, opening, closing)
Which metric matters for Morphological Operations and WHY

Morphological operations change image shapes to clean or highlight features. The key metrics measure how well these operations improve image quality for tasks like object detection or segmentation.

Common metrics include Intersection over Union (IoU) and Dice coefficient. They show how closely the processed image matches the true object shapes.

IoU and Dice help us know if erosion or dilation removed noise or filled gaps correctly without losing important details.

Confusion Matrix or Equivalent Visualization

For morphological operations, we compare pixels in the processed image to the ground truth:

      | Predicted Foreground | Predicted Background |
      |----------------------|----------------------|
      | True Positive (TP)    | False Negative (FN)   |
      | False Positive (FP)   | True Negative (TN)    |
    

Example: After dilation, some background pixels may become foreground (FP), or erosion may remove true foreground pixels (FN).

Precision vs Recall Tradeoff with Examples

Precision measures how many detected pixels are truly part of the object. High precision means few false positives.

Recall measures how many true object pixels were detected. High recall means few false negatives.

Example: Using erosion aggressively may remove noise (increasing precision) but also remove parts of the object (lower recall).

Example: Using dilation may fill gaps (increasing recall) but also add false pixels (lower precision).

Choosing the right operation depends on whether missing object parts (low recall) or adding noise (low precision) is worse for your task.

What "Good" vs "Bad" Metric Values Look Like

Good: IoU or Dice scores above 0.8 usually mean morphological operations improved the image well, preserving object shapes and removing noise.

Bad: Scores below 0.5 suggest the operations distorted the objects too much or left too much noise.

High precision but very low recall means the operation removed too much of the object.

High recall but very low precision means the operation added too much noise.

Common Pitfalls in Metrics for Morphological Operations
  • Ignoring context: Metrics alone don't show if shape changes hurt downstream tasks.
  • Over-smoothing: Too much erosion or opening can erase small but important features.
  • Over-expansion: Too much dilation or closing can merge separate objects incorrectly.
  • Data leakage: Using test images to tune operations can give overly optimistic metrics.
  • Accuracy paradox: High pixel accuracy can be misleading if background dominates the image.
Self-Check Question

Your morphological operation results show 98% pixel accuracy but only 12% recall on the object pixels. Is this good?

Answer: No, this means most object pixels were missed (low recall), even if background pixels are mostly correct. The operation likely removed too much of the object, which is bad for tasks needing full object detection.

Key Result
IoU and Dice scores best show how well morphological operations preserve object shapes while removing noise.

Practice

(1/5)
1. What does the erosion operation do to the white parts of a binary image?
easy
A. It grows the white parts by adding pixels at the edges.
B. It removes noise by smoothing the edges.
C. It fills small holes inside the white parts.
D. It shrinks the white parts by removing pixels at the edges.

Solution

  1. Step 1: Understand erosion effect on white pixels

    Erosion removes pixels from the boundaries of white regions, making them smaller.
  2. Step 2: Compare with other operations

    Dilation grows white parts, opening removes noise, closing fills holes, so erosion must shrink white parts.
  3. Final Answer:

    It shrinks the white parts by removing pixels at the edges. -> Option D
  4. Quick Check:

    Erosion = Shrinks white parts [OK]
Hint: Erosion shrinks white areas by cutting edges [OK]
Common Mistakes:
  • Confusing erosion with dilation
  • Thinking erosion fills holes
  • Mixing erosion with noise removal
2. Which of the following is the correct syntax to perform dilation using OpenCV in Python on an image img with a 3x3 kernel?
easy
A. cv2.erode(img, np.ones((3,3), np.uint8))
B. cv2.dilate(img, np.ones((3,3), np.uint8))
C. cv2.dilate(img, (3,3))
D. cv2.dilate(img, kernel=3)

Solution

  1. Step 1: Recall dilation syntax in OpenCV

    Dilation requires the image and a structuring element (kernel), usually created with np.ones of desired size and type.
  2. Step 2: Check options for correct usage

    cv2.dilate(img, np.ones((3,3), np.uint8)) uses cv2.dilate with a 3x3 kernel created by np.ones and correct dtype, which is valid syntax.
  3. Final Answer:

    cv2.dilate(img, np.ones((3,3), np.uint8)) -> Option B
  4. Quick Check:

    Dilation syntax = cv2.dilate(image, kernel) [OK]
Hint: Use np.ones((3,3), np.uint8) as kernel for dilation [OK]
Common Mistakes:
  • Using erode instead of dilate
  • Passing kernel size tuple directly
  • Using wrong kernel datatype
3. Given the following Python code using OpenCV:
import cv2
import numpy as np
img = np.array([[0,0,0,0,0],
                [0,255,255,255,0],
                [0,255,0,255,0],
                [0,255,255,255,0],
                [0,0,0,0,0]], dtype=np.uint8)
kernel = np.ones((3,3), np.uint8)
eroded = cv2.erode(img, kernel)
print(eroded)

What will be the printed output?
medium
A. [[ 0 0 0 0 0] [ 0 255 0 255 0] [ 0 0 0 0 0] [ 0 255 0 255 0] [ 0 0 0 0 0]]
B. [[ 0 0 0 0 0] [ 0 255 255 255 0] [ 0 255 255 255 0] [ 0 255 255 255 0] [ 0 0 0 0 0]]
C. [[ 0 0 0 0 0] [ 0 0 0 0 0] [ 0 0 0 0 0] [ 0 0 0 0 0] [ 0 0 0 0 0]]
D. [[255 255 255 255 255] [255 255 255 255 255] [255 255 255 255 255] [255 255 255 255 255] [255 255 255 255 255]]

Solution

  1. Step 1: Understand erosion on the given image

    Erosion removes pixels at edges of white regions. The center pixel (0) surrounded by 255s will cause erosion to shrink the white area.
  2. Step 2: Apply 3x3 kernel erosion

    Since the kernel covers neighbors, any pixel with a zero neighbor becomes zero. The white cross shape will erode to a smaller cross with zeros at the center and edges.
  3. Final Answer:

    White cross with zeros at center and edges as shown in option A -> Option A
  4. Quick Check:

    Erosion shrinks white, so edge pixels vanish but some inner pixels remain [OK]
Hint: Erosion removes edge pixels, shrinking white areas [OK]
Common Mistakes:
  • Assuming erosion keeps center pixels
  • Confusing erosion with dilation output
  • Ignoring zero pixels in kernel neighborhood
4. You wrote this code to perform opening on an image img but it does not remove noise as expected:
kernel = np.ones((3,3), np.uint8)
opened = cv2.dilate(cv2.erode(img, kernel), kernel)

What is the error and how to fix it?
medium
A. Kernel size is too small; increase kernel size to remove noise.
B. The order is reversed; opening is dilation followed by erosion, so swap the calls.
C. Use cv2.morphologyEx with cv2.MORPH_OPEN instead for correct opening.
D. The order is reversed; opening is erosion followed by dilation, so code is correct.

Solution

  1. Step 1: Check the definition of opening

    Opening is erosion followed by dilation. The code applies erosion then dilation, which is correct in order.
  2. Step 2: Identify practical issue

    Manual calls may work but can be error-prone; using cv2.morphologyEx with MORPH_OPEN is recommended for correct and optimized opening.
  3. Final Answer:

    Use cv2.morphologyEx with cv2.MORPH_OPEN instead for correct opening. -> Option C
  4. Quick Check:

    Use built-in morphologyEx for opening [OK]
Hint: Use cv2.morphologyEx with MORPH_OPEN for opening [OK]
Common Mistakes:
  • Swapping erosion and dilation order
  • Not using built-in morphology functions
  • Assuming kernel size fixes logic errors
5. You have a noisy binary image with small black holes inside white objects. Which morphological operation should you apply to fill these holes without changing the object shapes much?
hard
A. Closing
B. Dilation
C. Opening
D. Erosion

Solution

  1. Step 1: Understand the problem of black holes inside white objects

    Black holes are small dark spots inside white regions that need to be filled.
  2. Step 2: Choose operation that fills holes without shrinking objects

    Closing is dilation followed by erosion; it fills small holes and gaps while preserving object shape.
  3. Final Answer:

    Closing -> Option A
  4. Quick Check:

    Closing fills holes inside white objects [OK]
Hint: Closing fills holes inside white objects [OK]
Common Mistakes:
  • Using erosion which shrinks objects
  • Using opening which removes noise but not holes
  • Confusing dilation alone with closing