Diagnose a team's dev/test performance gap in a shared-distribution setting
Case context: A machine learning team builds a system and evaluates it on their dev set, achieving strong performance. When they later evaluate the same system on their test set, performance is noticeably worse. The team confirms that both the dev and test sets were sampled from the same underlying data distribution.
Question: Based on this case, what should the team diagnose as the cause of the performance gap, and what should they do about it?
Sample answer: Since the dev and test sets come from the same distribution, the team should diagnose that their system has overfit the dev set; the performance gap is not due to the test set representing different data. The obvious cure is to get more dev set data, which will make the dev set a more reliable and representative basis for tuning the system, reducing the risk of the system fitting to idiosyncrasies of a small dev set.
Key points:
- Same distribution rules out distribution mismatch as a cause
- Diagnosis is that the system has overfit the dev set
- Cure is to obtain more dev set data
- The diagnosis is described as clear/obvious given the shared distribution condition
Rubric: Full credit requires identifying dev set overfitting as the diagnosis given the shared distribution, and recommending more dev set data as the cure.
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
A system performs well on the dev set but poorly on the test set (same distribution). What is the diagnosis?
True or False: If dev and test sets share a distribution, dev-test performance gaps always mean the model is too complex.
The obvious cure for overfitting the dev set is to get more _____ data.
Match each dev/test performance scenario to its correct diagnosis
Order the reasoning steps for diagnosing a same-distribution dev/test performance gap
Explain why a same-distribution dev/test gap points specifically to dev set overfitting
Diagnose a team's dev/test performance gap in a shared-distribution setting
Why must dev and test sets share the same distribution to clearly diagnose dev set overfitting?
What is the recommended cure when a system has overfit the dev set?
True or False: A dev/test performance gap always requires collecting more test set data as the fix.