<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cold Case: The Lost MNIST Digits · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1905.10498/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1905.10498/feed.xml" rel="self" type="application/rss+xml" /><item><title>Cold Case: The Lost MNIST Digits — mentioned by mattkrause</title><link>https://news.ycombinator.com/item?id=29462438</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.10498:29462438</guid><pubDate>Mon, 06 Dec 2021 17:10:29 GMT</pubDate><description>&lt;p&gt;I disagree: some &amp;quot;collective overfitting&amp;quot; happens when everyone evaluates on the same dataset (and often, the same test set). There&amp;#x27;s a neat set of papers by Recht et al. showing results are slightly overfit to the test partitions of ImageNet and CIFAR-10: rotating examples between the train and test partitions causes systems to perform up to 10-15% worse. https://arxiv.org/abs/1806.00451 https://arxiv.org/abs/1902.10811 There&amp;#x27;s another neat bit of work involving MNIST. The original dataset (from the mid-90s) had 60,000 test examples, but the distributed versions that virtually everyone uses…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.10498/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Cold Case: The Lost MNIST Digits — mentioned by gwern</title><link>https://news.ycombinator.com/item?id=24579387</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.10498:24579387</guid><pubDate>Thu, 24 Sep 2020 15:16:35 GMT</pubDate><description>&lt;p&gt;Yes, because your validation set performance is imperfectly correlated with performance on more samples (because it&amp;#x27;s of finite size), so it will tend to overestimate within-distribution. There&amp;#x27;s also the problem that you probably want to deploy it on data which was not exactly collected the same way. So you have issues of both internal and external validity. In practice, at least for CNN classifiers on ImageNet etc, it seems to be a pretty minor issue overall. Some links: https://arxiv.org/abs/1711.11561 https://arxiv.org/abs/1806.00451 https://arxiv.org/abs/1902.10811…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.10498/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Cold Case: The Lost MNIST Digits — HN submission</title><link>https://news.ycombinator.com/item?id=20070010</link><guid isPermaLink="false">urn:hackerpapers:submission:1905.10498:20070010</guid><pubDate>Sat, 01 Jun 2019 16:41:36 GMT</pubDate><description>&lt;p&gt;Cold Case: The Lost Mnist Digits&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1905.10498/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
