bidsgate
A recovery gate for neuroimaging pipelines. Inject a known truth into real BIDS data, run any BIDS app on the result, and score what it recovered. Every pipeline claims to segment lesions or measure atrophy; this is the test that says by how much.
pip install bidsgate
bidsgate inject-lesions /data/bids --out /data/derivatives/bidsgate-lesions
# run your lesion segmenter on /data/derivatives/bidsgate-lesions
bidsgate score-lesions --truth /data/derivatives/bidsgate-lesions \
--pred "/data/derivatives/mytool/{subject}/{base}_seg.nii.gz" --pipeline mytool
Nothing in this repository is evidence about any disease. It is a test of software: the injected lesions and volume changes are synthetic, and the only claim made is about what a given pipeline recovered from them.
Why
There is no public ground truth for most of what neuroimaging pipelines report. Lesion segmenters are compared to expert masks that disagree with each other; morphometry tools report volumes nobody can check; when a new release shifts the numbers, the changelog says "improved" and the user has no way to tell. bidsgate gives every pipeline the same question: here is a scan with a known change in it, what did you find?
This generalises the synthetic backtest of lesiontrack, where injecting known lesion expansions showed a published method recovering a third of the injected change and firing on noise. The same discipline applies to any pipeline.
First results: LST-AI v2 on six healthy controls
LST-AI v2.0.0rc1 (CPU image, fast mode) was run on
the six OpenNeuro ds007908 controls that passed
the input checks, after twelve lesions (30 to 1500 mm3) were injected into each T1w and
FLAIR. Scorecard, JSON and per-lesion tables are in results/lst-ai-v2/.
| Subject | Detected | Dice | Volume ratio | Sensitivity 0-100 / 100-500 / 500+ mm3 | Extra components beyond 2 mm |
|---|---|---|---|---|---|
| sub-9000 | 9 of 12 | 0.75 | 1.15 | 0.83 / 0.50 / 0.75 | 16 (733 mm3) |
| sub-9001 | 11 of 12 | 0.80 | 1.34 | 0.83 / 1.00 / 1.00 | 32 (851 mm3) |
| sub-9002 | 9 of 12 | 0.81 | 0.96 | 0.83 / 0.50 / 0.75 | 3 (54 mm3) |
| sub-9003 | 12 of 12 | 0.83 | 1.03 | 1.00 / 1.00 / 1.00 | 6 (69 mm3) |
| sub-9004 | 12 of 12 | 0.85 | 1.24 | 1.00 / 1.00 / 1.00 | 16 (see JSON) |
| sub-9008 | 11 of 12 | 0.87 | 1.06 | 0.83 / 1.00 / 1.00 | 2 (see JSON) |
| All | 64 of 72 | 0.82 mean | 32/36, 10/12, 22/24 |
What the per-lesion tables show: the misses are not about size, they are about height.
Lesions of 26 to 30 mm3 were found in every subject, and the eight misses span 28 to
611 mm3. Split by where the lesion sits in the brain (thirds of the brain mask's
superior-inferior extent, recorded at injection and reported by score-lesions):
| Height in brain | Detected |
|---|---|
| Lower third (cerebellum, brainstem, inferior temporal level) | 6 of 12 |
| Middle third | 34 of 36 |
| Upper third | 24 of 24 |
Whether that is a weakness of the model or a weakness of injecting supratentorial-looking
lesions into infratentorial tissue is exactly the question the gate raises; --regions
with an atlas in subject space turns the height split into a per-structure one.
The extra components on a healthy control are not necessarily wrong: a control can carry real incidental white-matter hyperintensities, and the gate cannot tell those from false positives. It can only say how much the pipeline reported beyond what was injected. Here it ranged from 2 components to 32 across the six subjects.
Two of the eight controls were refused by the input checks: sub-9005's FLAIR is on a different grid from its T1w, and sub-9006's FLAIR shares the grid but not the affine (17 mm apart), so it was never co-registered. A shape-only check had accepted it. The gate refusing an input is a result too.
One correction on the placement mask, found while writing this and fixed in the version
after 0.1.0: five of the six controls were placed with an earlier estimator that kept only
the largest core piece, the sixth with a version that kept every piece over 100 ml; on this
data the extra piece is neck tissue, so that version reported 1.7 to 2.1 l for four
subjects. The estimator now keeps a second piece only when it sits level with the largest
along the superior-inferior axis (a hemisphere split by a deep fissure), and drops what
lies below (neck, face). All eight controls now measure 0.8 to 1.5 l on their original
images. The placements above were made with the largest-piece rule and are unaffected.
Pass --mask from a real brain extraction if you need placement to be exactly
reproducible across preprocessing variants.
Injections
Lesions (inject-lesions): ellipsoidal lesions with soft edges, placed inside a
white-matter estimate, FLAIR-hyperintense and T1w-hypointense relative to the median of
that estimate (gain 0.6 and −0.2 at the core by default). Sizes cycle through 30, 80,
200, 600 and 1500 mm3 so that the scorecard shows a detection floor by lesion size. No two
lesions touch, and every lesion lies deeper inside the brain than its own longest axis.
The brain mask is estimated from the T1w by morphology (tissue above an Otsu threshold,
eroded by 8 mm to cut scalp, optic nerves and cord; the largest remaining piece plus any
piece over 100 ml that sits level with it, grown back inside tissue, ventricles filled)
and must land between 700 and 2000 ml or the subject is refused. Pass your own mask with --mask "{subject}_brainmask.nii.gz"
if you have a better one. White matter is bright T1w tissue more than 6 mm inside that
mask whose FLAIR is within 0.6 to 1.4 of the FLAIR white-matter median, which excludes
CSF and anything outside the FLAIR field of view.
The soft field is 0.5 on the ellipsoid surface and falls off over 1 mm on either side, so the truth label (the voxels inside the surface) is exactly what a half-maximum segmenter would recover; a perfect segmenter scores Dice 1 and volume ratio 1, not 2. The truth is the label map plus a JSON with every lesion's centre, axes, label volume, nominal volume, voxel count, height in the brain and depth from the brain edge, the seed, the contrasts and the brain volume.
T1w and FLAIR must share grid and affine; a subject that does not is skipped with a
message and nothing is written for it. Every image gets its own seed (a hash of its name
mixed with --seed), so --subject selection and dataset growth do not change what a
subject receives, and run or acquisition entities are kept in the derivative names.
Atrophy (inject-atrophy): a smooth radial contraction of the brain by a known volume
factor (default 0.95, five percent loss) about its centroid, fading to identity over 12 mm
outside the brain mask. The same mask estimate and --mask option apply. The truth JSON
records the factor and the brain volume before and after as measured on the mask itself.
Note that the skull contracts with the brain inside the falloff zone, so a tool that
normalises to intracranial volume will see less change than was injected; compare raw
volumes.
Both write a BIDS derivative dataset: dataset_description.json, the modified images with
their sidecars carrying what was done, and the truth files next to them.
Scoring
score-lesions compares a predicted mask (binary or probabilistic, thresholded at 0.5)
with the truth, which must be on the same grid and affine: Dice, lesion-wise sensitivity
(a lesion is detected when any predicted voxel overlaps it), sensitivity by size bin, by
height in the brain (lower, middle, upper third of the brain mask, recorded at injection),
by region when you pass --regions (a label image on the truth grid, names via
--region-names label<TAB>name), and the predicted-over-injected volume ratio. False positives are every predicted voxel
farther than 2 mm (--fp-margin) from any injected lesion, reported as volume and as
18-connected components, so over-segmentation that happens to touch a true lesion still
counts. score-atrophy takes the volumes your tool reported before and after injection
and gives recovery: measured change over injected change, 1.0 being exact.
Both write JSON and a single-file HTML scorecard.
Limits, stated plainly
- Synthetic lesions are not real lesions. They have the contrast and shape the spec says, no more; a pipeline that finds them may still miss real ones, and a pipeline that misses them has a problem it cannot blame on pathology.
- The white-matter estimate is intensity-based, not a segmentation, and it does not
know cerebrum from cerebellum. Lesions land anywhere in deep bright tissue; a
per-region breakdown (and a
--regionmask) is the next scoring feature. - On real subjects, extra predicted components may be genuine findings. The gate reports them; it cannot judge them.
- Atrophy is global and radial. Regional atrophy needs a region mask; that is the next injector.
- Activation injection for fMRI is not built yet.
Development
pip install -e ".[dev]"
pytest -q
The tests build a head-shaped phantom (brain, skull gap, scalp) and check that the brain estimate excludes the scalp, keeps both hemispheres across a fissure and fills ventricles; that a slab of tissue with no plausible brain volume is refused; that injected lesions have the recorded volumes and contrasts, sit entirely in white matter and never touch; that the half-maximum set of the added contrast is the label; that a perfect prediction scores Dice 1, a slab through a lesion counts as a false positive and a shifted affine is refused; that atrophy shrinks the brain by the requested factor; that run entities survive into derivative names with distinct seeds; that a subject with a mismatched FLAIR leaves no partial output; and that the CLI runs end to end.
scripts/ holds the LST-AI runner used for the result above (run_lst_ai.sh, detached
Docker container per subject; overnight_demo.sh for the whole cohort).
MIT. Written by Cedric Conday with Claude (Anthropic) as coding partner.
Metadata
Release files for bidsgate 0.2.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 | |
|---|---|---|---|
| bidsgate-0.2.0.tar.gz | 28.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bidsgate-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.7 kB
Release files / bidsgate-0.2.0.tar.gz
| Download URL | bidsgate-0.2.0.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e706cf2f274ae13c613e718ed31acf56775f266b2c94abd359f9ec718009a6f0
|
|
BLAKE2b-256 checksum How to use checksums |
aed2753cf28a50a7de565585ac03e5469e6ed98675dc8e18045e0d097c69967e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / bidsgate-0.2.0-py3-none-any.whl
| Download URL | bidsgate-0.2.0-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9253859e1e673d653f3f0569978952e37b406cede76ea1696faf328117f7dede
|
|
BLAKE2b-256 checksum How to use checksums |
ffd0635ff80a8a26a9a2792269f672ed8452ec8a0dd83646b9e115975e76bb8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|