<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Anomaly Detection on Inês Garcia</title>
    <link>https://null-hypothesis.ines-garcia263.workers.dev/tags/anomaly-detection/</link>
    <description>Recent content in Anomaly Detection on Inês Garcia</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Inês Garcia</copyright>
    <lastBuildDate>Thu, 11 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://null-hypothesis.ines-garcia263.workers.dev/tags/anomaly-detection/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Automatic Dip Detection in Time Series: A Statistical Approach</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/automatic-dip-detection-statistical-approach/</link>
      <pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/automatic-dip-detection-statistical-approach/</guid>
      <description>&lt;p&gt;Monitoring availability metrics at scale creates a familiar problem: you have a time series, you need to know when it drops, and you need to know this automatically — without someone staring at a dashboard.&lt;/p&gt;&#xA;&lt;p&gt;This post walks through a statistical algorithm I built to do exactly that. It detects dips in any continuous metric (availability, reachability, error rate) and returns precise start and end timestamps for each event. No ML required — just a modified z-score, two rolling windows, and a few transition rules.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
