<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>s1: Simple test-time scaling · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2501.19393/</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/2501.19393/feed.xml" rel="self" type="application/rss+xml" /><item><title>s1: Simple test-time scaling — mentioned by embedding-shape</title><link>https://news.ycombinator.com/item?id=48985025</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:48985025</guid><pubDate>Mon, 20 Jul 2026 21:21:28 GMT</pubDate><description>&lt;p&gt;&amp;gt; My favorite trick for controlling the reasoning level is the hack First described here I think, specifically for Qwen models: https://arxiv.org/abs/2501.19393, although it seems unclear how much it actually improves the final response unless you create a new fine-tuned model with this in mind, and also if it&amp;#x27;s possible to replicate for other models. Still, got inspired and gonna give it a try with DiffusionGemma although slightly differently&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by mxwsn</title><link>https://news.ycombinator.com/item?id=48884181</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:48884181</guid><pubDate>Sun, 12 Jul 2026 20:01:49 GMT</pubDate><description>&lt;p&gt;This is the same reasoning behind why Yann Lecun thought test-time scaling would not work for LLMs: compounding error. Instead, the more tokens LLMs use, the better their performance on many tasks. LLMs can self-correct, evidenced by the power of getting models to question themselves by emitting &amp;quot;Wait,&amp;quot; in S1. https://arxiv.org/abs/2501.19393&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by kgeist</title><link>https://news.ycombinator.com/item?id=47597191</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:47597191</guid><pubDate>Wed, 01 Apr 2026 05:34:48 GMT</pubDate><description>&lt;p&gt;&amp;gt;One theory is that the knowledge required to solve the task is already stored in the parameters of the model, and only the style has to change for task success &amp;gt;In particular, learning to generate longer outputs may be possible in few parameters Reminded me of: https://arxiv.org/abs/2501.19393 &amp;gt;we develop budget forcing to control test-time compute by forcefully terminating the model’s thinking process or lengthening it by appending “Wait” multiple times to the model’s generation when it tries to end. This can lead the model to double-check its answer, often fixing incorrect reasoning steps…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — HN submission</title><link>https://news.ycombinator.com/item?id=44313278</link><guid isPermaLink="false">urn:hackerpapers:submission:2501.19393:44313278</guid><pubDate>Wed, 18 Jun 2025 21:06:55 GMT</pubDate><description>&lt;p&gt;S1: Simple Test-Time Scaling&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by mangoman</title><link>https://news.ycombinator.com/item?id=43839739</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:43839739</guid><pubDate>Wed, 30 Apr 2025 00:24:12 GMT</pubDate><description>&lt;p&gt;a paper with a similar idea on scaling test time reasoning, this is sorta how all the thinking models work under the hood. https://arxiv.org/abs/2501.19393&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by computerex</title><link>https://news.ycombinator.com/item?id=43454547</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:43454547</guid><pubDate>Sun, 23 Mar 2025 17:56:48 GMT</pubDate><description>&lt;p&gt;I don’t think you have an accurate understanding of how LLMs work. https://arxiv.org/abs/2501.19393 These tokens DO extend the thinking time. We are talking about causal autoregressive language models, and so these tokens can be used to guide the generation.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by lelag</title><link>https://news.ycombinator.com/item?id=43281592</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:43281592</guid><pubDate>Thu, 06 Mar 2025 15:51:34 GMT</pubDate><description>&lt;p&gt;If that&amp;#x27;s an issue, there&amp;#x27;s a workaround using structure generation to force it to output a &amp;lt;/thiking&amp;gt; token after some threshold and force it to write the final answer. It&amp;#x27;s a method used to control thinking token generation showcased in this paper: https://arxiv.org/abs/2501.19393&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — HN submission</title><link>https://news.ycombinator.com/item?id=43005221</link><guid isPermaLink="false">urn:hackerpapers:submission:2501.19393:43005221</guid><pubDate>Mon, 10 Feb 2025 21:13:00 GMT</pubDate><description>&lt;p&gt;s1: Simple Test-Time Scaling&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/2501.19393/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by armcat</title><link>https://news.ycombinator.com/item?id=42993175</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42993175</guid><pubDate>Sun, 09 Feb 2025 19:47:19 GMT</pubDate><description>&lt;p&gt;Yes, the authors explicitly highlighted those two points in the abstract, in terms of them being the elicitation threshold for complex reasoning, namely, an extremely complete pre-trained foundation model, and a set of extremely high quality examples post-training. To your question on finetuning on the initial 10 million pool - intuitively, it would require tremendous amount of finetuning data to move the needle - you really won&amp;#x27;t be able to move the gradients much with just 817 examples, that initial pool is effectively enforcing pretty rigid regularization. There is now an increasing…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by psytrancefan</title><link>https://news.ycombinator.com/item?id=42990549</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42990549</guid><pubDate>Sun, 09 Feb 2025 13:29:44 GMT</pubDate><description>&lt;p&gt;Thanks. I had not seen the wait paper yet. That is crazy. s1: Simple test-time scaling https://arxiv.org/pdf/2501.19393&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — HN submission</title><link>https://news.ycombinator.com/item?id=42979455</link><guid isPermaLink="false">urn:hackerpapers:submission:2501.19393:42979455</guid><pubDate>Sat, 08 Feb 2025 01:23:41 GMT</pubDate><description>&lt;p&gt;Test-time scaling new approach: extra test-time compute improves LLM reasoning&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/2501.19393/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by wrenky</title><link>https://news.ycombinator.com/item?id=42964002</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42964002</guid><pubDate>Thu, 06 Feb 2025 16:32:35 GMT</pubDate><description>&lt;p&gt;nope you have the article right. &amp;quot;if you copy an existing model, you can get a pretty comparable model!&amp;quot; Really, [what the underlying paper](https://arxiv.org/abs/2501.19393) shows is how much you can improve existing models with several of the techniques released by openai recently (extending thought processes via &amp;quot;wait&amp;quot;) It shows we can get a lot of mileage out of that technique.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by ozgune</title><link>https://news.ycombinator.com/item?id=42961717</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42961717</guid><pubDate>Thu, 06 Feb 2025 12:28:00 GMT</pubDate><description>&lt;p&gt;Agreed. Here are three things that I find surreal about the s1 paper. (1) The abstract changed how I thought about this domain (advanced reasoning models). The only other paper that did that for me was the &amp;quot;Memory Resource Management in VMware ESX Server&amp;quot;. And that paper got published 23 years ago. (2) The model, data, and code are open source at https://github.com/simplescaling/s1. With this, you can start training your own advanced reasoning models. All you need is a thousand well-curated questions with reasoning steps. (3) More than half the references in the paper are from 2024 and Jan…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by bberenberg</title><link>https://news.ycombinator.com/item?id=42947651</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42947651</guid><pubDate>Wed, 05 Feb 2025 12:38:05 GMT</pubDate><description>&lt;p&gt;In case you’re not sure what S1 is, here is the original paper: https://arxiv.org/html/2501.19393v1&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>s1: Simple test-time scaling — mentioned by xena</title><link>https://news.ycombinator.com/item?id=42935594</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.19393:42935594</guid><pubDate>Tue, 04 Feb 2025 17:26:19 GMT</pubDate><description>&lt;p&gt;The file explains it a bit, but my blogpost https://xeiaso.net/notes/2025/s1-simple-test-time-scaling/ could probably be better explained. I&amp;#x27;ll write out more but just for you I&amp;#x27;ll summarize what I&amp;#x27;m gonna end up writing up. AI models fundamentally work on the basis of &amp;quot;given what&amp;#x27;s before, what comes next?&amp;quot; When you pass messages to an API like: [ { &amp;quot;role&amp;quot;: &amp;quot;system&amp;quot;, content&amp;quot;: &amp;quot;You are an expert in selling propane and propane accessories. Whenever someone talks about anything that isn&amp;#x27;t propane, steer them back.&amp;quot; }, { &amp;quot;role&amp;quot;: &amp;quot;user&amp;quot;, &amp;quot;content&amp;quot;: &amp;quot;What should I use to cook food on my grill?&amp;quot;…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.19393/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
