<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Assessing Generative Models via Precision and Recall · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1806.00035/</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/1806.00035/feed.xml" rel="self" type="application/rss+xml" /><item><title>Assessing Generative Models via Precision and Recall — mentioned by godelski</title><link>https://news.ycombinator.com/item?id=36688068</link><guid isPermaLink="false">urn:hackerpapers:mention:1806.00035:36688068</guid><pubDate>Tue, 11 Jul 2023 22:23:18 GMT</pubDate><description>&lt;p&gt;&amp;gt; I have used LLMs on actually novel tasks for which there aren’t any datasets out there. They “get it”. Can you give an example so that we may better discuss or that I can adequately update my understandings? But I will say that simplifying this down to &amp;quot;just trained to predict the next token&amp;quot; is not accurate as it does not account for the differences in architectures and cost functions which dramatically affect this statement due to the differences in their biases. As a clear example, training an image model on likelihood does note guarantee that the model will produce high fidelity…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1806.00035/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>stat.ML</category></item><item><title>Assessing Generative Models via Precision and Recall — mentioned by godelski</title><link>https://news.ycombinator.com/item?id=36129656</link><guid isPermaLink="false">urn:hackerpapers:mention:1806.00035:36129656</guid><pubDate>Tue, 30 May 2023 19:46:35 GMT</pubDate><description>&lt;p&gt;Oh yeah, those are great papers, which I wish more people read. (I&amp;#x27;ll never not laugh at the journal name) I&amp;#x27;ll add this too[0] since it seems to be highly missed. But as far as validation sets, I have a hard time convincing anyone I talk to that tuning on test data is information leakage. I&amp;#x27;ve also had issues with discussing people (even outside my lab, even at big schools/labs) what &amp;quot;uncurated samples&amp;quot; means. I say &amp;quot;you sample batch and show that&amp;quot; they say you can sample multiple batches and pick the best one... So this is the same kind of thinking and shows why evaluating generative papers…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1806.00035/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>stat.ML</category></item><item><title>Assessing Generative Models via Precision and Recall — HN submission</title><link>https://news.ycombinator.com/item?id=18561235</link><guid isPermaLink="false">urn:hackerpapers:submission:1806.00035:18561235</guid><pubDate>Thu, 29 Nov 2018 16:12:08 GMT</pubDate><description>&lt;p&gt;Keep Drawing It: Iterative language-based image generation and editing&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1806.00035/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>stat.ML</category></item></channel></rss>
