Understanding the Double Descent Phenomenon in Deep Learning

Marc Lafon, Alexandre Thomas
3/15/2024
cs.LGcs.CVstat.ML

No confident code implementation found for this paper.

Abstract

Combining empirical risk minimization with capacity control is a classical strategy in machine learning when trying to control the generalization gap and avoid overfitting, as the model class capacity gets larger. Yet, in modern deep learning practice, very large over-parameterized models (e.g. neural networks) are optimized to fit perfectly the training data and still obtain great generalization performance. Past the interpolation point, increasing model complexity seems to actually lower the test error. In this tutorial, we explain the concept of double descent and its mechanisms. The first section sets the classical statistical learning framework and introduces the double descent phenomenon. By looking at a number of examples, section 2 introduces inductive biases that appear to have a key role in double descent by selecting, among the multiple interpolating solutions, a smooth empirical risk minimizer. Finally, section 3 explores the double descent with two linear models, and gives other points of view from recent related works.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{lafon2024understanding,
  title  = {Understanding the Double Descent Phenomenon in Deep Learning},
  author = {Marc Lafon and Alexandre Thomas},
  year   = {2024},
  eprint = {2403.10459},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2403.10459v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2403.10459.svg)](https://codeofpaper.com/paper/2403.10459)

Discussion