Browse State-of-the-Art › Brain Tumor Segmentation

Brain Tumor Segmentation

178 papers with code · 12 benchmarks · 8 datasets archive 2025-07-28

Computer VisionMedical

Brain Tumor Segmentation is a medical image analysis task that involves the separation of brain tumors from normal brain tissue in magnetic resonance imaging (MRI) scans. The goal of brain tumor segmentation is to produce a binary or multi-class segmentation map that accurately reflects the location and extent of the tumor.

( Image credit: Brain Tumor Segmentation with Deep Neural Networks )

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

12 leaderboard tables shown for this task, 12 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted. 10 shown of 12 until expanded.

Syntology 3 newer papers were judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): BRATS 2019 (1 judged, 0 placed), BRATS 2018 (3 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
BRATS 2019 (5 rows) Segtran (i3d) Medical Image Segmentation Using Squeeze-and-Expansion Transformers code Syntology official (archive's flag): 13 ran · 13 ran (of which 8 constructed an object rather than computing a result; 11 with no instrument failure: 1 honoured, 0 violated, 10 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified Compare
BRATS-2015 (4 rows) OM-Net + CGAp One-pass Multi-task Networks with Cross-task Guided Attention for... code — Compare
BRATS 2018 (4 rows) NVDLMED 3D MRI brain tumor segmentation using autoencoder regularization code Syntology 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified Compare
BRATS-2013 (3 rows) Semantic Genesis Learning Semantics-enriched Representation via Self-discovery,... code — Compare
BRATS-2017 val (3 rows) SegFormer3D SegFormer3D: an Efficient Transformer for 3D Medical Image Segmentation code Syntology official (archive's flag): 2 ran · 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified Compare
BRATS-2013 leaderboard (2 rows) InputCascadeCNN Brain Tumor Segmentation with Deep Neural Networks code — Compare
768 chest X-ray images (1 row) tumor 3D AGSE-VNet: An Automatic Brain Tumor MRI Data Segmentation Framework — — Compare
BRATS-2014 (1 row) Cascaded Anisotropic CNNs Automatic Brain Tumor Segmentation using Cascaded Anisotropic... code Syntology 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified Compare
BRATS 2018 val (1 row) OM-Net + CGAp One-pass Multi-task Networks with Cross-task Guided Attention for... code — Compare
BraTS-Africa (1 row) CNMC_PMILAB Adult Glioma Segmentation in Sub-Saharan Africa using Transfer... — — Compare
BraTs Peds 2024 (1 row) CNMC_PMILAB Magnetic Resonance Imaging Feature-Based Subtyping and Model... code — Compare
BRISC (1 row) Swin-HAFNey BRISC: Annotated Dataset for Brain Tumor Segmentation and... — — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

8 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 436 · with a code link: 178 · where Syntology ran a sample: 29 (21 with a run with no instrument failure, 8 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (29 of 436 tagged: 21 with a run with no instrument failure, 8 where every run was a failure of Syntology's instrument)

Page 1 of 5: papers 1 to 100 of 436, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 19 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections