When is a random train/test split a poor evaluation choice?
Question: In one to three sentences, explain when a random 80%/20% train/test split is a bad way to evaluate a system.
Sample answer: A random split is a poor choice when the data the model is trained on does not match the data it will face after deployment. For example, a model trained on studio product photos may need to work on customer photos taken in very different lighting.
Key points:
- The problem is a mismatch between training and deployment data.
- Random splitting can hide that mismatch.
- The training and target distributions should be similar for the split to be reliable.
Rubric: Full credit requires stating that the split fails when the training data distribution differs from the real-world use distribution; partial credit for mentioning a random split without naming the mismatch condition.
0
1
Tags
Machine Learning
Deep Learning
Machine Learning Strategy
Supervised Learning
Dive into Deep Learning @ D2L
Data Science
Machine Learning Yearning @ DeepLearning.AI
Related
Why can a random 70/30 train/test split be misleading in deployed machine-learning systems?
True or False: A random 70/30 split always creates a test set that matches the deployment distribution.
A Common Historical Train/Test Split
Match each data situation to whether a random 70/30 split is a good choice.
Order the steps for deciding whether a random split is appropriate.
Why a Random Split Can Mislead Under Distribution Shift
Diagnose a training split for a retail shelf classifier.
When is a random train/test split a poor evaluation choice?
When Can a Random 70/30 Split Be Misleading?
True or False: A 70/30 train/test split was a common default when datasets were much smaller than they are today.