Case Study

Dev and Test Splits for a Field-Photo Classifier

Case context: A team is building a plant disease classifier. They train on 60,000 images downloaded from agriculture websites. Their app will mainly be used by field scouts who take photos on low-end phones under outdoor lighting, so the future data will look different from the website images. The team decides to set aside 20% of the website images for development and testing.

Question: What is wrong with this split, and how should the development and test sets be chosen instead?

Sample answer: The split is a poor choice because the held-out examples still come from the website-image distribution, while the real deployment data will be phone photos taken in the field. Development and test sets should be built to match the data the system is expected to face after launch, so they should contain representative phone photos rather than only website images.

Key points:

  • A random holdout from the website images still reflects the website distribution.
  • Evaluation data should match the deployment distribution.
  • The goal is to measure performance on the kind of images the app will actually receive.

Rubric: The answer must say that a random 20% split of website images is a poor choice because it does not match the future phone-photo distribution, and it must state that dev and test sets should be drawn to reflect the deployment data.

0

1

Updated 2026-08-12

Contributors are:

Who are from:

Tags

Machine Learning

Deep Learning

Supervised Learning

Dive into Deep Learning @ D2L

Data Science

Machine Learning Strategy

Machine Learning Yearning @ DeepLearning.AI

Related