Learn Before
Why Dev-Set and Test-Set Mismatch Hurts Prioritization
Question: Why does a mismatch between the dev set and the test set make it harder for a machine learning team to decide what to improve next?
Sample answer: Because it becomes unclear whether a change that helps the dev set will also help the test set. Without that link, the team cannot reliably tell which fixes are truly improving overall performance, so choosing the next task becomes much harder.
Key points:
- A mismatch weakens the connection between dev-set gains and test-set gains.
- It makes it harder to judge which changes are genuinely useful.
Rubric: The answer should explain that the mismatch creates uncertainty about whether dev-set improvements transfer to the test set, which makes prioritizing work more difficult.
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 mismatched dev and test sets waste improvement work?
Misaligned Dev and Test Sets Make Prioritization Harder
Development and Test Sets Should Differ
Effects of a Development/Test Distribution Mismatch
Order the chain of events that shows how a misleading validation set can waste tuning effort.
Why Distribution Mismatches Can Waste Tuning Effort
Explaining a Credit-Risk Model Gap
Why Dev-Set and Test-Set Mismatch Hurts Prioritization
What problem can appear when the development set and test set come from different distributions?
A test set should always be harder than a dev set