<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LLM Myths on Honglu Fan</title>
    <link>https://honglu2875.github.io/tags/llm-myths/</link>
    <description>Recent content in LLM Myths on Honglu Fan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Oct 2024 20:58:38 -0400</lastBuildDate>
    <atom:link href="https://honglu2875.github.io/tags/llm-myths/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLM myths 2: perplexity and surprise</title>
      <link>https://honglu2875.github.io/posts/2024-10-27-llm_myths_2_perplexity_and_surprise/</link>
      <pubDate>Sun, 27 Oct 2024 20:58:38 -0400</pubDate>
      <guid>https://honglu2875.github.io/posts/2024-10-27-llm_myths_2_perplexity_and_surprise/</guid>
      <description>&lt;p&gt;Given a language model, &amp;ldquo;perplexity&amp;rdquo; is defined as the mean of the negative log-likelihood. It is perhaps coined to correlate with the human sense of confusion (more when the number is high) and in many cases it is reasonable. Sometimes, we also refer to the negative log-likelihood of a single token as &amp;ldquo;surprise&amp;rdquo;. They are indeed good terminologies used both in academia and industry, and they also get the concept across a wide audience. But when people build their intuition by relying too much on these terms, misleading subtleties will occur.&lt;/p&gt;</description>
    </item>
    <item>
      <title>LLM myths 1: why does LLM generate infinite loops</title>
      <link>https://honglu2875.github.io/posts/2024-10-27-llm_myths_1_why_does_llm_generate_loops/</link>
      <pubDate>Sun, 27 Oct 2024 19:57:30 -0400</pubDate>
      <guid>https://honglu2875.github.io/posts/2024-10-27-llm_myths_1_why_does_llm_generate_loops/</guid>
      <description>&lt;p&gt;Looping is fairly common when sampling from an LLM. We normally do not want it to happen and there has been many tricks trying to make it behave such as repetition penalties or hard-coded loop detections, but their effectiveness is debatable. The explanation of this phenomenon seems scarce in literature and it might at first feels like another bug in our day-to-day data/model engineering without anything deep.&lt;/p&gt;&#xA;&lt;p&gt;But for modern LLMs without ad-hoc outer logics to guard its output, sampling loops has been out there with us all along. For example, you can easily induce Deepseek model into a loop by writing this prompt (as of Oct 30th, 2024): &amp;ldquo;Write me a bunch of bullet points.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
