Learn Before
How large should an Eyeball dev set be for useful manual error review?
Question: What size requirement should guide an Eyeball dev set, and about how many errors should it contain so that people can inspect failures by hand?
Sample answer: It should be large enough to include a workable number of mistakes for inspection. A practical target is about 100 misclassified examples, which gives enough errors to study patterns without making manual review overwhelming.
Key points:
- The set must be large enough to produce enough errors for analysis.
- A reasonable target is roughly 100 misclassified examples.
Rubric: The answer should say that the Eyeball dev set needs to be large enough for manual inspection and should contain about 100 errors.
0
1
Tags
Machine Learning
Deep Learning
Supervised Learning
Dive into Deep Learning @ D2L
Data Science
Machine Learning Strategy
Machine Learning Yearning @ DeepLearning.AI
Related
Spotting Overfitting to a Manually Reviewed Dev Slice
How to Size an Eyeball Dev Set When Data Is Easy to Review
A Review Set Should Expose the Main Error Types
Manual Review Sets Can Be Unhelpful for Tasks People Cannot Judge Reliably
What is the main purpose of the human-review subset when a validation set is split into two parts?
The label "manual review set" can remind a team that people should inspect those examples directly.
What fraction of the dev set is manually reviewed in the Eyeball subset?
Match each dev set split term to its description.
Arrange the steps for building and using a small review subset from a larger development set in the correct order.
If 20% of a 3,000-example dev set is set aside as the Eyeball dev set, how many examples are in that subset?
If a 400-example Eyeball dev set has the same 20% error rate as the full dev set, you would expect about 80 misclassified examples.
The eye-check dev set should contain enough mistakes for you to _____.
Match each manual-review subset fact to the idea it describes.
Order the steps for deciding whether a small inspection subset is large enough for error analysis.
How should the manual-review subset be named in a voice transcription project?
Split the Development Set Into an Inspection Set and a Locked Set
How large should an Eyeball dev set be for useful manual error review?