<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Batch Normalization on Nalar</title>
    <link>https://nalar.dev/tags/batch-normalization/</link>
    <description>Recent content in Batch Normalization on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/batch-normalization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recompute BatchNorm Statistics After Weight Averaging</title>
      <link>https://nalar.dev/recompute-batchnorm-statistics-after-weight-averaging/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/recompute-batchnorm-statistics-after-weight-averaging/</guid>
      <description>&lt;p&gt;Averaging two neural-network checkpoints can produce a useful parameter vector, yet leave BatchNorm running statistics tied to a different network. The weights define one set of activations; the stored running means and variances may describe activations produced by earlier weights. Inference then combines state from two different points in parameter space.&lt;/p&gt;&#xA;&lt;p&gt;This mismatch is easy to miss because BatchNorm running statistics are buffers rather than trainable parameters in common implementations. A parameter-averaging routine can handle every weight correctly and still produce an internally inconsistent inference state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
