Skip to content
Français

Anomaly Detection: Find What Is Unusual

Find the few events that matter among millions that do not. Compare rules, robust statistics, control charts, isolation, time-series and deep methods on the same data, choose by the cost of a miss, and run the detector as a daily job that people trust.

Read every lesson as a guest, or sign in to enroll and track your progress.

Is this the right course for you?What this course covers and does not cover, and 4 courses to take for other needs.

This course teaches how to find the unusual: framing an anomaly problem, robust baselines and rules, control charts and drift tests, distance, density and isolation methods, time-series detectors and change points, autoencoders and embeddings, evaluation with few labels under an alert budget, learning from reviewers, and a detection job in production. It does not teach supervised models in general, forecasting in depth, or how to operate a service.

Take another course if you want to:

What you'll learn

By the end of this course, you will be able to:

  • Frame an anomaly problem: what "unusual" means for the decision, the type of anomaly (point, contextual, collective, change), the unit and time of a check, and the cost of a miss and of a false alert.
  • Build simple, explainable baselines (z-score, median and MAD, IQR, seasonal baselines, rules) and say when they are enough.
  • Monitor business processes with statistical process control (I-MR, p- and u-charts, CUSUM, EWMA, run rules), and test for distribution drift (KS, chi-square, PSI, Wasserstein) with a stated false-alarm rate and a size of change that matters.
  • Apply and compare classical and deep methods (kNN distance, LOF, Isolation Forest, One-Class SVM, autoencoders, embedding distance) on the same data, and explain why each wins or loses.
  • Detect anomalies in time series and change points (STL residuals, rolling robust baselines, change-point detection) without confusing a holiday with an incident.
  • Evaluate with few labels the way the business does: precision at k, recall of known cases, alerts per day, an alert budget and cost per week, with honest limits.
  • Run a detector in production: scores to alerts, thresholds that follow an alert budget, a label feedback loop from reviewers, retraining, and drift in what "normal" means.

About this course

Larkfield, an online shop for home and garden products, wants to find unusual events before they cost money. A customer who buys a small basket every week suddenly makes eight payments in a foreign city in ten minutes. One support agent’s refund rate rises a little and stays high. The ticket API slows down a little more every day. A data feed sends zeros for a whole day.

In this course, you follow Priya, a data scientist, as she builds and compares detectors for these problems. Sofia’s team reviews the payment alerts and can check 50 a day. Grace reads the control charts for refunds. Amira owns the ticket API, and Mei owns the data feeds.

Every method runs on the same Larkfield data and goes into one comparison table: alerts per day, the planted anomalies found within the daily budget, the cost per week and the time to explain one alert. You see a three-line rule beat a neural network on one problem and lose on another, and you learn why.

All data is synthetic and has no real people. Every practice anomaly is one we planted on purpose, and the course says so each time. Everything runs in notebooks on a laptop CPU or in free Colab, with no paid service.

Before you start

You completed Machine Learning, From Problem to Reliable Model, or you have the same skills (features, splits, scikit-learn pipelines, precision and recall, thresholds). You can read and change Python and pandas code in a notebook. The mathematics, forecasting and MLOps courses help but are not required; lessons that use their ideas explain them briefly and link to them. You need a free Google or Kaggle account for the notebooks, or Python 3.12 on your computer. You need no paid service.

Courses to take first: Machine Learning: From Problem to Reliable Model.

Who this is for

Data scientists, ML engineers, analysts and backend or operations engineers who must find rare, unusual events (fraud, faults, bad data, sudden changes) and turn them into alerts that people act on.

How we made this course

Experienced AI practitioners designed this course. AI helped us draft the content; people chose the teaching approach and the examples, and reviewed every lesson. The outputs that you see are the actual results of running the code. How we make our courses

Inside the course

Module 3Statistical process control and distribution drift

7 lessons

Statistical process control and distribution drift. Watch the refund rate with I-MR, p-, CUSUM and EWMA charts, measure the price of each run rule, test distributions with KS, PSI and Wasserstein, and use Benford's law and other business checks.

  1. Control charts: is this variation normal?40 min
  2. Rules for patterns, and the price of each rule35 min
  3. Charts for rates and counts35 min
  4. Small, lasting shifts: CUSUM and EWMA40 min
  5. Has the distribution changed?40 min
  6. Drift in many features, and what to do about it35 min
  7. Benford's law and other business checks35 min

Module 9Run a detector in production

3 lessons

Run a detector in production. Build a scheduled detection job that follows the budget and never sends an alert twice, handle a product launch that moves normal, and keep alerts that people still read.

  1. From score to alert45 min
  2. When "normal" moves40 min
  3. Alert fatigue and ownership35 min

Final module · choose at least oneCase studies

4 case studies

Four end-to-end case studies on real open data. Card fraud with a review budget, faults in machine or server metrics, unusual readings in public open data, and control charts on a real production line. Complete at least one for the certificate; each one is a portfolio piece.

Complete at least one case study for the certificate. The others are optional. What each one covers

  1. Card fraud with a review budget150 min
  2. Faults in machine or server metrics120 min
  3. Unusual readings in public open data150 min
  4. Control charts on a real production line120 min

After the case studiesFinal assignment

Use every module in one practice project. You collect evidence, and check it against the course outcomes.

  1. Final assignment180 min

Case studies

Realistic projects from start to finish, on real data, with every output explained. Each one makes a portfolio piece. Complete at least one for the certificate; the others are optional.

  1. Card fraud with a review budget2 hr 30 min

    Anonymised card transactions: compare a rule, Isolation Forest, an autoencoder and a supervised model on the few labels, and choose by precision at a daily review budget.

  2. Faults in machine or server metrics2 hr

    Labelled time series of real systems: compare seasonal baselines, STL residuals, change points and a multivariate detector, scored by time to detection and alerts per day.

  3. Unusual readings in public open data2 hr 30 min

    A public open-data series with no labels: plant anomalies, separate real events from data faults, and write the alert policy.

  4. Control charts on a real production line2 hr

    Sensor readings and pass/fail results from a manufacturing process: control charts and drift checks on the key signals, compared with Isolation Forest.

Reviews

Loading the reviews…

    Took this course? Sign in to review it. Learners can write a review after they complete 25% of the lessons.

    Share this course