<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RoFormer: Enhanced Transformer with Rotary Position Embedding · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2104.09864/</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/2104.09864/feed.xml" rel="self" type="application/rss+xml" /><item><title>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by spott</title><link>https://news.ycombinator.com/item?id=44802389</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:44802389</guid><pubDate>Tue, 05 Aug 2025 18:43:52 GMT</pubDate><description>&lt;p&gt;All the Llamas have done it (well, 2 and 3, and I believe 1, I don&amp;#x27;t know about 4). I think they have a citation for it, though it might just be the RoPE paper (https://arxiv.org/abs/2104.09864). I&amp;#x27;m not actually aware of any model that doesn&amp;#x27;t do positional embeddings on a per-layer basis (excepting BERT and the original transformer paper, and I haven&amp;#x27;t read the GPT2 paper in a while, so I&amp;#x27;m not sure about that one either).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by spmurrayzzz</title><link>https://news.ycombinator.com/item?id=43598551</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:43598551</guid><pubDate>Sun, 06 Apr 2025 02:46:21 GMT</pubDate><description>&lt;p&gt;Not sure what you mean by summary paper, its a pretty dense topic that assumes a fair amount of prior knowledge of the fundamentals. But maybe the Meta blog post may suffice for that? Otherwise yes there are lots of papers on this and related topics, a few dozen in fact. But here are some notable ones, a couple of them are linked in their blog post. RoFormer: Enhanced Transformer with Rotary Position Embedding - https://arxiv.org/abs/2104.09864 Scaling Laws of RoPE-based Extrapolation - https://arxiv.org/abs/2310.05209 The Impact of Positional Encoding on Length Generalization in Transformers…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by jimmyl02</title><link>https://news.ycombinator.com/item?id=43596305</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:43596305</guid><pubDate>Sat, 05 Apr 2025 19:49:18 GMT</pubDate><description>&lt;p&gt;the large context windows generally involve RoPE[0] which is a trick that allows the training window to be smaller but expand larger during inference. it seems like they have a new &amp;quot;iRoPE&amp;quot; which might have better performance? [0]https://arxiv.org/pdf/2104.09864&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by EGreg</title><link>https://news.ycombinator.com/item?id=43563970</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:43563970</guid><pubDate>Thu, 03 Apr 2025 02:14:22 GMT</pubDate><description>&lt;p&gt;LLaMa 3 already has RoPE encoding which can handle arbitrarily long contexts (within reason) https://arxiv.org/abs/2104.09864 The difference RoPE makes vs traditional positional encoding is that you just care about relative distances between tokens, and we can attenuate the attention over great distances. Instead of making the model look at every token in the entire sequence all at once (which gets expensive fast), you can break the text into logical chunks—like sentences or paragraphs—and run self-attention within each chunk. That keeps things efficient while still capturing local meaning.…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by GistNoesis</title><link>https://news.ycombinator.com/item?id=37061438</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:37061438</guid><pubDate>Wed, 09 Aug 2023 12:09:14 GMT</pubDate><description>&lt;p&gt;Cool, there are also additional issues with the RoPEAttention you might want to fix as well : The reference paper for rotary embedding is Roformer https://arxiv.org/pdf/2104.09864v4.pdf First you shouldn&amp;#x27;t rotate the values, only keys and queries. This is wrong : v_out = (torch.bmm(v.transpose(0,1), self.R[:m, ...])).transpose(0,1) Second you shouldn&amp;#x27;t apply multihead attention which as additional inner weights that will mess with the rotations you have just done. This is wrong : activations, attn_weights = self.multihead (q_out,k_out,v_out) Instead you should use…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by mfn</title><link>https://news.ycombinator.com/item?id=35508348</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:35508348</guid><pubDate>Mon, 10 Apr 2023 01:47:52 GMT</pubDate><description>&lt;p&gt;Sinusoidal positional embeddings have always seemed a bit mysterious - even more so since papers don&amp;#x27;t tend to delve much into the intuition behind them. For example, from Vaswani et al., 2017: &amp;gt; That is, each dimension of the positional encoding corresponds to a sinusoid. The wavelengths form a geometric progression from 2π to 10000 · 2π. We chose this function because we hypothesized it would allow the model to easily learn to attend by relative positions, since for any fixed offset k, PE(pos+k) can be represented as a linear function of PE(pos). Inspired largely by the RoFormer paper…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>RoFormer: Enhanced Transformer with Rotary Position Embedding — mentioned by sebzim4500</title><link>https://news.ycombinator.com/item?id=35123483</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.09864:35123483</guid><pubDate>Sun, 12 Mar 2023 17:49:37 GMT</pubDate><description>&lt;p&gt;It doesn&amp;#x27;t really use them, it uses something called RoPE which is hardcoded rather than learned and is applied multiplicatively at every layer to both the key and the value. https://arxiv.org/abs/2104.09864&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.09864/"&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>
