PROFESSIONAL-MACHINE-LEARNING-ENGINEER · Question #168
You recently developed a deep learning model. To test your new model, you trained it for a few epochs on a large dataset. You observe that the training and validation losses barely changed during…
The correct answer is A. Verify that your model can obtain a low loss on a small subset of the dataset. If training and validation losses barely change, the first debugging step should be to confirm the model can overfit a small dataset, which verifies its basic learning capability.
Question
Options
- AVerify that your model can obtain a low loss on a small subset of the dataset
- BAdd handcrafted features to inject your domain knowledge into the model
- CUse the Vertex AI hyperparameter tuning service to identify a better learning rate
- DUse hardware accelerators and train your model for more epochs
How the community answered
(54 responses)- A81% (44)
- B6% (3)
- C11% (6)
- D2% (1)
Why each option
If training and validation losses barely change, the first debugging step should be to confirm the model can overfit a small dataset, which verifies its basic learning capability.
The "overfit a small batch" or "sanity check on a tiny dataset" technique is a fundamental first debugging step for deep learning models when training loss is not decreasing. If the model cannot achieve a very low (near zero) loss on a small, representative subset of the data, it indicates a fundamental issue with the model architecture, data preprocessing, loss function, or optimizer setup, suggesting it's unable to learn anything at all.
Adding handcrafted features is a strategy to improve model performance or interpretability but is not a primary debugging step for a model that isn't learning anything at all; it doesn't address the fundamental issue of unchanging loss.
Using hyperparameter tuning is premature when the model isn't learning at all (losses aren't changing); tuning a learning rate is only useful if the model shows some sign of learning initially.
Training for more epochs or using hardware accelerators is about scaling or prolonging training, not debugging a model that shows no signs of learning from the outset; if the loss isn't changing, more training won't fix a fundamental issue.
Concept tested: Deep learning model debugging (overfitting small batch)
Source: https://developers.google.com/machine-learning/guides/debugging-ml-models
Topics
Community Discussion
No community discussion yet for this question.