<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Quality on Nalar</title>
    <link>https://nalar.dev/tags/data-quality/</link>
    <description>Recent content in Data Quality on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/data-quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Prevent Target Leakage in Machine Learning Evaluation</title>
      <link>https://nalar.dev/prevent-target-leakage-in-machine-learning-evaluation/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/prevent-target-leakage-in-machine-learning-evaluation/</guid>
      <description>&lt;p&gt;A machine learning model can score extremely well in offline evaluation and fail as soon as it reaches production. Sometimes the model is not the main problem. The evaluation accidentally gave it information that would not exist when a real prediction is made.&lt;/p&gt;&#xA;&lt;p&gt;This failure is called &lt;strong&gt;target leakage&lt;/strong&gt;: information related to the outcome enters the model inputs in a way that makes the target easier to predict than it will be at inference time. Leakage can produce impressive metrics because the model is solving an easier, unrealistic problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
