{ "cells": [ { "cell_type": "markdown", "metadata": {}, "source": [ "\n\n# Quality control (QC) reports with mne.Report\n\nQuality control (QC) is the process of systematically inspecting M/EEG data\n**throughout all stages of an analysis pipeline**, including raw data,\nintermediate preprocessing steps, and derived results.\n\nWhile QC often begins with an initial inspection of the raw recording,\nit is equally important to verify that signals continue to \"look reasonable\"\nafter operations such as filtering, artifact correction, epoching, and\naveraging. Issues introduced or missed at any stage can propagate downstream\nand invalidate later analyses.\n\nThis tutorial demonstrates how to create a **single, narrative QC report**\nusing :class:`mne.Report`, focusing on **what should be inspected and how the\nresults should be interpreted**, rather than exhaustively covering the API.\n\nFor clarity and reproducibility, the examples below focus on common QC checks\napplied at representative stages of an analysis pipeline. The same reporting\napproach can\u2014and should\u2014be reused whenever new processing steps are applied.\n\nWe use the MNE sample dataset for demonstration. Not all QC sections are\napplicable to every dataset (e.g., continuous head-position tracking), and\nthis tutorial explicitly handles such cases.\n\n
For several additional examples of complete reports, see the\n [MNE-BIDS-Pipeline QC reports](https://mne.tools/mne-bids-pipeline/stable/examples/examples.html).