NeuroDAGs
An Extensible and Declarative DAG Framework for Reproducible Neuroscience Workflows
M/EEG studies generate many interdependent intermediate derivatives. Recomputing full pipelines is wasteful; reusing valid intermediates is non-trivial. Large-scale studies require reproducible, extensible, and efficient workflows. NeuroDAGs addresses this with a declarative, graph-based framework for scalable and reusable derivative computation.
Docs | Comparison with Snakemake/Pydra | Poster BRaIN Symposium 2026 Montreal
Core Idea
Pipelines are defined as a directed acyclic graph (DAG) of computation nodes that output reusable derivatives, executed for each input file.
Design Principles
- Reproducible, transparent workflows defined declaratively in YAML — version-controllable and LLM-friendly.
- Uniform node abstraction — preprocessing, features, and any custom nodes are treated identically.
- Directory-agnostic — outputs mirror inputs' organization. Derivatives are labeled with an
@<name>suffix using the derivative name verbatim, and a.donemanifest marks each finished file. - xarray-centered outputs — derivatives stored as language-agnostic, metadata-rich, dimension-aware xarray → NetCDF.
- Graph-based reuse — if a derivative is already computed and
overwrite=False, it is skipped automatically.
Features
- Agnostic to data organization / directory hierarchy
- SLURM / HPC friendly with file-level parallelism via joblib
- Graph-based caching: skip derivatives whose
.donemanifest is valid - Extensible node system — add nodes without forking the package
- YAML-based declarative configuration
- Unified CLI:
neurodags validate,run,dry-run,status,inputs,count-inputs,dataframe,dag,view,slurm-script,migrate,tui - Built-in Terminal User Interface (TUI) for pipeline management and execution
- Built-in nodes for preprocessing, spectral analysis, entropy, complexity, and data transformations
- Dataframe assembly (wide or long format) from derivative artifacts
- Dry-run mode — inspect planned computations without executing
- Built-in Dash-Plotly explorer for
.fifand.ncfiles
Upgrading from 0.3.x? 0.4.0 changes output names, the output layout and when a unit counts as done, and refuses 0.3.x configurations until they are migrated. Preview the upgrade with
neurodags migrate pipeline.yml, then add--apply; see the migration guide.
Installation
pip install neurodags
# Or with TUI support
pip install neurodags[tui]
With uv (recommended):
uv add neurodags
# Or with TUI support
uv add neurodags[tui]
Quickstart
See the quickstart example — full synthetic pipeline, no real data required.
CLI Reference
NeuroDAGs installs a unified neurodags command. Global flags (placed before the subcommand) apply everywhere:
neurodags --log-level WARNING run pipeline.yml # suppress INFO output
neurodags --log-file run.jsonl run pipeline.yml # also write logs to JSONL file
All subcommands accept -d/--datasets <path> to override the datasets YAML defined in the pipeline file.
The JSONL log file loads directly as a dataframe:
import pandas as pd
df = pd.read_json("run.jsonl", lines=True)
Validation
neurodags validate pipeline.yml # load config, print datasets / derivatives summary
neurodags validate pipeline.yml -d alt.yml # override datasets
Execution
neurodags run pipeline.yml # run all derivatives in DerivativeList
neurodags run pipeline.yml --derivative CleanedEEG # run a specific derivative
neurodags run pipeline.yml --derivative A --derivative B # run multiple
# parallelism
neurodags run pipeline.yml --n-jobs 4 # 4 workers
neurodags run pipeline.yml --n-jobs -1 # all cores
neurodags run pipeline.yml --n-jobs 4 --joblib-backend loky --joblib-prefer processes
# subset / error control
neurodags run pipeline.yml --max-files-per-dataset 10
neurodags run pipeline.yml --only-index 0 5 12 # process only these file indices (unknown index = error)
neurodags run pipeline.yml --inputs inputs.tsv # use a frozen input list instead of discovery
neurodags run pipeline.yml --skip-errors # skip files with a prior .error marker
neurodags run pipeline.yml --raise-on-error # stop on first failure
Dry Run
Inspect the execution plan without running any nodes. Returns a CSV/Parquet describing each file, derivative, and whether the output is already cached.
neurodags dry-run pipeline.yml # all derivatives
neurodags dry-run pipeline.yml --derivative CleanedEEG # one derivative
neurodags dry-run pipeline.yml --output plan.csv # save to CSV
neurodags dry-run pipeline.yml --output plan.parquet # or Parquet
neurodags dry-run pipeline.yml --n-jobs 4 # parallel dry-run
neurodags dry-run pipeline.yml --skip-errors # exclude errored files from plan
Status
Quick summary of done / skipped / incomplete / missing / errored counts per derivative — no CSV needed.
neurodags status pipeline.yml # summary table
neurodags status pipeline.yml --derivative Alpha # filter to one derivative
neurodags status pipeline.yml --list-errors # errored files: [idx N] path + .error path
neurodags status pipeline.yml --list-missing # incomplete and missing files: [idx N] path
neurodags status pipeline.yml --list-errors --list-missing
neurodags status pipeline.yml --n-jobs 4 # parallelize underlying dry-run
neurodags status pipeline.yml --format json # machine-readable JSON
neurodags status pipeline.yml --format json --include-files # + per-file records
neurodags status pipeline.yml --format indices # missing/incomplete/errored indices for --only-index
Exit code 0 only when all derivatives are complete (nothing missing, incomplete or errored); 1 otherwise.
Source File Count
neurodags count-inputs pipeline.yml # number of input entries (size of the --only-index range)
neurodags count-inputs pipeline.yml --inputs inputs.tsv # number of entries in a frozen input list
neurodags inputs pipeline.yml -o inputs.tsv # freeze the input list (index, dataset, path below source_root)
Dataframe Assembly
neurodags dataframe pipeline.yml --format wide --output features.csv
neurodags dataframe pipeline.yml --format long --output features.parquet
neurodags dataframe pipeline.yml --include-derivative PowerSpectrum --include-derivative BandPower
neurodags dataframe pipeline.yml --max-files-per-dataset 5
neurodags dataframe pipeline.yml --n-jobs 4 # parallel file-level collection
neurodags dataframe pipeline.yml --n-jobs -1 # all cores
DAG Visualization
neurodags dag pipeline.yml # print Mermaid text
neurodags dag pipeline.yml --html pipeline_dag.html # export to HTML (ELK layout by default)
neurodags dag pipeline.yml --html pipeline_dag.html --open # export and open in browser
neurodags dag pipeline.yml --derivative CleanedEEG --html d.html # node-level DAG for one derivative
neurodags dag pipeline.yml --html pipeline_dag.html --layout dagre # offline fallback (no CDN)
HTML output uses the ELK layout engine by default — orthogonal edge routing with crossing minimisation, significantly cleaner than curved edges for dense pipelines. Use --layout dagre for offline environments.
File Explorer
neurodags view path/to/file.fif # launch Dash-Plotly explorer for MNE .fif files
neurodags view path/to/file.nc # launch Dash-Plotly explorer for xarray NetCDF files
SLURM / HPC Scripts
Generate ready-to-submit SLURM array job scripts:
neurodags slurm-script pipeline.yml # per-file pattern (default)
neurodags slurm-script pipeline.yml --pattern flat # file × derivative flat array
neurodags slurm-script pipeline.yml --pattern chained # chained per-derivative arrays
neurodags slurm-script pipeline.yml --output run_array.sh # write to file
neurodags slurm-script pipeline.yml --derivative CleanedEEG # restrict to specific derivatives
See HPC guide for details on each pattern.
Upgrading a 0.3.x project
neurodags migrate pipeline.yml --report plan.json # preview: changes nothing
neurodags migrate pipeline.yml --apply # rewrite the config, move outputs, write .done
See the migration guide.
TUI (Terminal User Interface)
Requires pip install neurodags[tui]:
neurodags tui # launch empty TUI, load config interactively
neurodags tui pipeline.yml # launch with config pre-loaded
neurodags tui pipeline.yml -d alt.yml # with datasets override
Development
git clone https://github.com/yjmantilla/neurodags
cd neurodags
uv sync --all-extras --all-groups # creates .venv and installs all deps incl. dev/test/docs
uv run pre-commit install
Key commands (all via uv run):
uv run ruff check src/ # lint (fix: uv run ruff check src/ --fix)
uv run black --check . # format check (fix: uv run black .)
uv run pytest -q # run tests
uv run pytest -s -q --no-cov --pdb # debug a failing test
uv run sphinx-build -b html docs docs/_build/html -W --keep-going # build docs
rm -rf docs/_build # clean docs
No uv? Install it with
pip install uvorcurl -Ls https://astral.sh/uv/install.sh | sh. All commands above work with plainpython/piptoo — swapuv run→ activate.venv,uv sync→pip install -e .[dev,test,docs].
Project Structure
my_project/
├── datasets.yml # Dataset sources and paths
├── pipeline.yml # Derivative definitions and execution list
└── custom_nodes.py # Optional custom node definitions
Quick Example
datasets.yml
my_dataset:
name: MyDataset
source_root: # required since 0.4.0
local: data
hpc: /cluster/BIDS
file_pattern: # relative paths: relative to this file's folder
local: data/**/*.vhdr
hpc: /cluster/BIDS/**/*.vhdr
derivatives_path:
local: outputs/
hpc: /cluster/scratch/out
pipeline.yml
naming_version: 1 # required since 0.4.0
datasets: datasets.yml
mount_point: local
new_definitions: custom_nodes.py # optional
DerivativeDefinitions:
CleanedEEG:
nodes:
- id: 0
derivative: SourceFile
- id: 1
node: basic_preprocessing
args:
mne_object: id.0
resample: 256
filter_args:
l_freq: 0.5
h_freq: 110
PowerSpectrum:
for_dataframe: True
nodes:
- id: 0
derivative: CleanedEEG.fif
- id: 1
node: mne_spectrum_array
args:
meeg: id.0
method: multitaper
DerivativeList:
- CleanedEEG
- PowerSpectrum
Python
from neurodags.orchestrators import run_pipeline
# Pass the path: relative paths then resolve against the YAML files. A dict loaded
# in Python needs base_dir=... for relative dataset paths (0.4.0).
config = "pipeline.yml"
# Run all derivatives in "DerivativeList", auto-sorted by dependency order
run_pipeline(config)
# Or run specific ones (also sorted by dependency order)
run_pipeline(config, derivatives=["CleanedEEG"])
CLI
neurodags validate pipeline.yml
# Run all derivatives in DerivativeList (dependency-sorted)
neurodags run pipeline.yml
# Or run specific ones
neurodags run pipeline.yml --derivative CleanedEEG
Custom Nodes
Add nodes without modifying or forking the package:
# custom_nodes.py
from neurodags.nodes import register_node
from neurodags.definitions import Artifact, NodeResult
@register_node
def my_node(data) -> NodeResult:
result = compute(data)
return NodeResult(
artifacts={
".nc": Artifact(
item=result,
writer=lambda path: result.to_netcdf(path),
),
},
)
Key rules:
- A node is a function decorated with
@register_node. - It returns a
NodeResult. - A
NodeResultcontainsartifacts— a dict mapping an artifact suffix (.nc,.report.html) toArtifact(item, writer); the writer returns the files it wrote (orNone).
Dataframe Assembly
from neurodags.orchestrators import build_derivative_dataframe
df = build_derivative_dataframe("pipeline.yml", output_format="wide")
Derivatives marked for_dataframe: True are collected automatically. Supports "wide" (one row per file) and "long" (one row per value) formats.
CLI equivalent:
neurodags dataframe pipeline.yml --format wide --output derivative_dataframe.csv
Parallel Execution
# pipeline.yml
n_jobs: 4 # -1 = all cores, 1 or null = serial
joblib_backend: loky
joblib_prefer: processes
Or via Python:
run_pipeline(config, derivatives=["MyDerivative"], n_jobs=4)
Or via CLI:
neurodags run pipeline.yml --derivative MyDerivative --n-jobs 4
Visualization
neurodags view path/to/file.fif
neurodags view path/to/file.nc
# Alternative module entry point
python -m neurodags.visualization path/to/file.fif
python -m neurodags.visualization path/to/file.nc
Built-in Dash-Plotly explorer with dimension-aware UI — dropdown per axis, plot types: Line, Scatter, Bar, Heatmap.
Inspection (Dry Run)
# All derivatives in DerivativeList
run_pipeline(config, dry_run=True)
# Or a specific one
run_pipeline(config, derivatives=["MyDerivative"], dry_run=True)
Returns a dataframe describing the execution plan without running any nodes. When a node fails, a .error marker file is written with the error message — failed files are retried on the next run. If a retry succeeds, the .error marker is automatically removed.
CLI equivalent:
# All derivatives in DerivativeList
neurodags dry-run pipeline.yml --output dry_run_results.csv
# Or a specific one
neurodags dry-run pipeline.yml --derivative MyDerivative --output dry_run_results.csv
Derivative Flags
| Flag | Default | Description |
|---|---|---|
save |
True |
Persist artifacts to disk. False = compute but don't write. |
overwrite |
False |
Force recompute even if the unit is done (valid .done manifest). |
for_dataframe |
False |
Include this derivative in build_derivative_dataframe. |
Custom Node Definitions
Point new_definitions to one or more Python files:
new_definitions:
- custom_nodes/my_nodes.py
- /abs/path/to/other_nodes.py
Relative paths are resolved from the pipeline YAML location.
Documentation
https://yjmantilla.github.io/neurodags/
HDF5 / NetCDF Note
If you encounter RuntimeError: NetCDF: HDF error:
uv run pip install --no-binary=h5py h5py
# or without uv:
pip install --no-binary=h5py h5py
Contributing
See CONTRIBUTING.md.
License
MIT. See LICENSE.
Metadata
Release files for neurodags 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| neurodags-0.4.0.tar.gz | 210.3 kB | With provenance | Details for neurodags-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neurodags-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for neurodags-0.4.0-py3-none-any.whl |
Total release size: 438.7 kB
Release files / neurodags-0.4.0.tar.gz
| Download URL | neurodags-0.4.0.tar.gz |
|---|---|
| Size | 210.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db85bb51825f7c3161e12ed4b7a5e73f86628a08fbf444c63ee1d6869ad74b7e
|
|
BLAKE2b-256 checksum How to use checksums |
1b259870b53939cd0ecc240c77b8041708e9d84bed4df79bae090c8dda5ff719
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / neurodags-0.4.0-py3-none-any.whl
| Download URL | neurodags-0.4.0-py3-none-any.whl |
|---|---|
| Size | 228.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
854d6501704ead50605670fc8daf6c824d9cb9ab9956b8f540c4475e60df247d
|
|
BLAKE2b-256 checksum How to use checksums |
9ca53145eba98d0e9b7cf6d9895aa290edecdb0dd7893841cd94a901f099b866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for neurodags 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for neurodags-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.