<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chronos-2: From Univariate to Universal Forecasting · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2510.15821/</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/2510.15821/feed.xml" rel="self" type="application/rss+xml" /><item><title>Chronos-2: From Univariate to Universal Forecasting — mentioned by ChernovAndrei</title><link>https://news.ycombinator.com/item?id=46375288</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.15821:46375288</guid><pubDate>Wed, 24 Dec 2025 13:14:38 GMT</pubDate><description>&lt;p&gt;There is no single answer, because there are multiple architectures for foundation time-series models, such as T5, decoder-only models, and state-space models (SSMs). For Chronos-2 (the current state of the art in time-series modeling), the setup is almost identical to that of LLMs because it is based on the T5 architecture. The main difference is that, in time-series models, tokens correspond to subintervals in the real-valued (ℝ) space. You can check the details here: https://arxiv.org/pdf/2510.15821&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.15821/"&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>Chronos-2: From Univariate to Universal Forecasting — mentioned by armcat</title><link>https://news.ycombinator.com/item?id=46363153</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.15821:46363153</guid><pubDate>Tue, 23 Dec 2025 07:16:35 GMT</pubDate><description>&lt;p&gt;The promise is similar to LLMs, if you pretrain on sufficiently large timeseries datasets with sufficiently large variance/characteristics, that you will be able to transfer the model to a completely different use case that exhibits somewhat similar characteristics (in latent space). But it’s always good to check what kind of data the model was trained on, eg Chronos 2.0 training data is described in Appendix A Table 6 here: https://arxiv.org/pdf/2510.15821&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.15821/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
