Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Coverage roadmap

This page tracks known gaps in the book — topics that belong here and are not yet written. It exists so that contributors can see where the holes are without having to audit 80-odd pages, and so that the reasoning behind each gap is recorded rather than rediscovered.

How the gaps were identified

The book was compared against a full research-lifecycle model — a nine-stage pipeline (propose, initialize, curate, analyze, checkpoint, QC, export, publish, disseminate) running inside a continuous administrative track covering funding, ethics, deadlines and credit.

The comparison produced one clear finding: the book covers the middle of the lifecycle well and both ends barely at all.

Lifecycle:  Govern → Initialize → Curate → Analyze → Checkpoint → QC → Export → Publish → Disseminate
Coverage:   ░░░░░░   ████████     ██████   ███████   ░░░░░░░░░░   ███  ░░░░░░   ░░░░░░░   ░░░░░░░░░░
            └─ thin ─┘                                            └────────── thin ──────────┘
            └──────────── administrative track: thin throughout ────────────┘

The Start Here pathway reflects the same shape: it begins at “find data” and ends at “share your work”, which skips what must be settled before data access and stops short of what turns an analysis into a citable research product.

Documentation of tools is genuinely strong. Documentation of process is where the gaps are.

A second axis: analysis and craft

The audit above asked whether every stage of the lifecycle was covered. A later pass asked a different question — whether the analytical and craft topics a scholar needs are present regardless of stage — and found a second set of holes, recorded as priorities 8–12 below.

Two findings stand out. The Research Methods section is entirely machine learning: there was no classical statistical inference anywhere in a book about analysing clinical neuroimaging cohorts. And cross-cohort pooling is a stated premise of several CNS projects while site harmonization, the thing that makes pooling valid, had no coverage at all.

Note that research_topics/ and modalities/ pages are deliberately short — they are link-dense hubs, not content pages. Their length is not a gap.

Priority 1 — Provenance and data versioning

The largest single hole, now partly filled.

TopicStatus
DataLadWritten
YODA project layoutCovered inside the DataLad page
git-annex / large-file versioningCovered inside the DataLad page

Before this, DataLad appeared in four pages purely as a name in a list, despite being the mechanism most of the reproducibility advice elsewhere in the book depends on.

Priority 2 — Before you touch data

Nothing in the book covered this stage. A new scholar’s first real blocker is usually data access, and the book documented which datasets exist without ever describing how to get into one.

TopicStatus
Ethics and data accessStub — highest value here
Data management plansStub
Pre-registrationStub

Priority 3 — Turning an analysis into a research product

The book stops at “share your work”. The steps that make work citable and reusable are absent.

TopicStatus
Releasing data and codeStub — OSF, Zenodo, DOIs
Reporting guidelinesStub — COBIDAS, TRIPOD
Executable articlesStub — NeuroLibre

Priority 4 — Curation depth

BIDS is explained as a standard, but not as a task you have to perform.

TopicStatus
Getting data into BIDSStub — dcm2niix, HeuDiConv, validator
Neurobagel and semantic annotationStub — SNOMED, harmonization

Cross-cohort pooling is a premise of several CNS projects, and variable harmonization is the unglamorous step it depends on.

Priority 5 — Administration and credit

TopicStatus
Credit and contributionsStub — ORCID, CRediT
Research administrationStub — decision logs, obligations

Priority 6 — AI in the research workflow

The existing AI models section covers how large language models work. It does not cover working with them, which is now part of most people’s daily practice and has unresolved implications for provenance.

TopicStatus
AI assistants in the research workflowStub
Agent-callable methodsStub — MCP, Paper2Agent

Priority 7 — A quality framework

TopicStatus
STAMPED principlesStub

The book already argues for most of STAMPED without naming it — containers for portability, provenance for tracking, BIDS for modularity. Naming the framework would let those arguments reinforce each other instead of appearing as unrelated advice.

Priority 8 — Statistics and inference

The largest hole on the second axis. Research Methods covers deep learning and five ML method pages; nothing covered inference. A new Statistics and Inference section was added to hold it.

TopicStatus
Prediction vs inferenceStub — the distinction the rest depends on
Multiple comparisonsStub — FWE, FDR, cluster inference, permutation
Power and sample sizeStub — effect sizes, inflation under low power
Mixed modelsStub — longitudinal and multi-site designs
Harmonization and site effectsStub — ComBat; highest value here

Priority 9 — Ways to fool yourself

TopicStatus
Data leakageStub — subject, site, and preprocessing leakage

Pairs with imbalanced data, which already covers resampling inside the fold.

Priority 10 — Tools used everywhere and documented nowhere

Each of these appeared across the book only as a name in passing.

TopicStatus
NilearnStub — the most-used Python neuro package here
MNE-PythonStub — six projects use EEG/MEG
FreeSurferStub — and fMRIPrep already runs it
Visualizing brain dataStub — colormaps, thresholds, figures
Testing research codeStub — pytest, CI, regression tests

Priority 11 — Privacy and review

TopicStatus
De-identificationStub — defacing, DICOM scrubbing, PHI in sidecars
Peer reviewStub — preprints, response letters, reviewing

Priority 12 — Program and career

A different genre from the rest of the book and lower priority, but a fellowship is fixed-term and the transition out of it is a real part of the experience here.

Also outstanding

Contributing

Every stub above states what it needs. Pick one, write it, open a PR — and if you have actually done the thing, write from that experience rather than from the documentation. The first-hand version is worth considerably more.