<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Beam Search on Nalar</title>
    <link>https://nalar.dev/tags/beam-search/</link>
    <description>Recent content in Beam Search on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/beam-search/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Control Beam Search Length Bias with Length Normalization</title>
      <link>https://nalar.dev/control-beam-search-length-bias-with-length-normalization/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/control-beam-search-length-bias-with-length-normalization/</guid>
      <description>&lt;p&gt;Beam search is a common way to decode sequence models when choosing the most likely token at every step is too shortsighted. It keeps several partial candidates alive, expands them, and repeatedly retains the strongest alternatives.&lt;/p&gt;&#xA;&lt;p&gt;There is a subtle problem: the score used for a sequence usually accumulates one log-probability per generated token. Because token probabilities are at most 1, their log-probabilities are normally non-positive. Extending a sequence therefore tends to make its raw cumulative score smaller. When finished candidates of different lengths compete directly, this can create a preference for outputs that end too early.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
