Browse State-of-the-Art › Cell Segmentation

Cell Segmentation

91 papers with code · 12 benchmarks · 22 datasets archive 2025-07-28

Computer Vision

Cell Segmentation is a task of splitting a microscopic image domain into segments, which represent individual instances of cells. It is a fundamental step in many biomedical studies, and it is regarded as a cornerstone of image-based cellular research. Cellular morphology is an indicator of a physiological state of the cell, and a well-segmented image can capture biologically relevant morphological information.

Source: Cell Segmentation by Combining Marker-controlled Watershed and Deep Learning

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.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
Fluo-N2DL-HeLa (3 rows) Dual U-Net (Neighbor distances) Cell Segmentation and Tracking using CNN-Based Distance... code — Compare
LIVECell (3 rows) Cascade Mask RCNN-ResNest-200 LIVECell—A large-scale dataset for label-free live cell segmentation code — Compare
DIC-C2DH-HeLa (2 rows) EncLSTM Microscopy Cell Segmentation via Convolutional LSTM Networks code — Compare
EVICAN (2 rows) DeepCeNS DeepCeNS: An end-to-end Pipeline for Cell and Nucleus Segmentation... — — Compare
Fluo-N2DH-GOWT1 (2 rows) DecLSTM Microscopy Cell Segmentation via Convolutional LSTM Networks code — Compare
Fluo-N2DH-SIM+ (2 rows) EncLSTM Microscopy Cell Segmentation via Convolutional LSTM Networks code — Compare
CoNSeP (1 row) PromptNu Prompting Vision-Language Model for Nuclei Instance Segmentation... code — Compare
Fluo-C3DL-MDA231 (1 row) Dual U-Net (Neighbor distances) Cell Segmentation and Tracking using CNN-Based Distance... code — Compare
MoNuSeg (1 row) PromptNu Prompting Vision-Language Model for Nuclei Instance Segmentation... code — Compare
PanNuke (1 row) PromptNu Prompting Vision-Language Model for Nuclei Instance Segmentation... code — Compare
PhC-C2DH-U373 (1 row) EncLSTM Microscopy Cell Segmentation via Convolutional LSTM Networks code — Compare
STARE (1 row) U-Net U-Net: Convolutional Networks for Biomedical Image Segmentation code Syntology 530 ran (of which 247 constructed an object rather than computing a result; 378 with no instrument failure: 18 honoured, 10 violated, 350 with no contract checked; 152 where Syntology's instrument failed) · 227 unverified 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

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

Subtasks archive 2025-07-28

1 subtask in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 178 · with a code link: 91 · where Syntology ran a sample: 7 (6 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (7 of 178 tagged: 6 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument)

Page 1 of 2: papers 1 to 100 of 178, 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 7 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