> ## Documentation Index
> Fetch the complete documentation index at: https://docs.autocleaneeg.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Derivatives Overview

> Learn how AutoCleanEEG stores processed outputs in the BIDS derivatives folder, including metadata, intermediate files, and subject-level results.

## The `derivatives/` Folder

The `derivatives/` folder follows the [BIDS derivatives standard](https://bids.neuroimaging.io/), where processed data are kept separate from raw‑like files.
AutoCleanEEG writes a single derivatives tree without versioned subfolders; provenance is tracked in the `dataset_description.json` and the top‑level task metadata.

### Example Layout

```
bids/
└── derivatives/
    ├── dataset_description.json
    ├── 01_import/
    ├── 02_resample/
    ├── 03_filter/
    ├── ...
    └── 16_comp/
```

### Key Components

| Item                           | Purpose                                                                                        |
| ------------------------------ | ---------------------------------------------------------------------------------------------- |
| **`dataset_description.json`** | Required by BIDS derivatives. Documents the pipeline, version, and references.                 |
| **Stage folders**              | Numbered stage outputs (e.g., `01_import/` … `16_comp/`) placed directly under `derivatives/`. |

### Why Derivatives Matter

* **Traceability**: `dataset_description.json` names the pipeline; versions are tracked in the task metadata and reports.
* **Separation of concerns**: Raw-like BIDS inputs are preserved; processed stage outputs live here.
* **Compatibility**: BIDS‑aware tools know to look in `derivatives/` for secondary outputs.
* **Debugging**: Stage folders keep step‑wise artifacts organized; QA and reports live at the task root.

<Info>
  If disk space is limited, you can archive or delete stage folders once you no longer need to inspect intermediate files. Final user‑facing outputs live under the task‑root `exports/` folder.
</Info>