← Back to the vault

Lab Note · updated 2026-06-20

Evaluating Segmentation Models in Real Microscopy Workflows

A segmenter's benchmark Dice rarely predicts its behavior in a real workflow. Instance counting, merge/split errors, and cross-instrument generalization are the quantities that decide whether the downstream readout is correct — and standard semantic overlap scores are blind to all three.

SegmentFeaturesReadoutCell PaintingDigital PathologyLight-Sheet 3D/4DSpatial OmicsCellposeStarDistnnU-NetPanoptic QualitySEG
← Back to constellation

The problem — A segmentation model arrives with a leaderboard Dice, and the number is treated as a forecast of how it will perform on your images. It is not. Benchmark Dice is a semantic (pixel-class) overlap on a curated dataset; a microscopy workflow needs instance correctness — the right number of objects, each one whole and separate — on images from your instrument. Those are different quantities, and the gap between them is where pipelines silently fail.

What it is / how it works — Three distinctions decide real-workflow performance, and a single overlap score collapses all of them:

  • Instance vs semantic. Pixel-class Dice can be high while objects are wrong. The biology is usually counted per object — cells, nuclei, organoids — so the honest metric is instance-aware: object-level F1, Panoptic Quality, or the Cell Tracking Challenge SEG measure (mean Jaccard over matched reference cells). Metrics Reloaded makes the selection explicit — instance problems demand instance metrics.
  • Merge and split errors. The two failure modes that destroy a count — two touching cells fused into one (merge), one cell broken into two (split) — barely move pixel Dice but directly corrupt the readout. A clustered, confluent field is exactly where they spike.
  • Generalization across instruments. A benchmark rank is not robust: it shifts with the test set, the ranking scheme, and the annotators (Maier-Hein et al.). A model tuned on one microscope, magnification, or stain can drop sharply on another — the distribution shift that benchmark numbers never see.

The operating rule: evaluate on your data, at the object level, separating merges and splits, and report performance conditioned on the instrument — not a single dataset's Dice.

Where it breaks — The general principle: benchmark overlap measures average pixel agreement on someone else's images, while a workflow needs per-object correctness on yours — so the two diverge wherever objects touch, are rare, or come from a new instrument. In Cell Painting, merge/split errors in confluent wells propagate straight into per-cell feature distributions and break profile reproducibility. In digital pathology, a nucleus segmenter tuned on one scanner and stain protocol mis-segments on another, and tile-level Dice hides it. In light-sheet, dense 3D volumes make under-segmentation (merges) the dominant error, invisible to a global score but fatal to lineage counts. In spatial omics, boundary errors that barely touch IoU misassign transcripts to neighboring cells and corrupt the count matrix. The unifying discipline is to make the evaluation match the workflow — instance metrics, error decomposition, and cross-instrument testing — which is the same problem-aware stance behind choosing the metric for the question and validation without a clean reference.

A leaderboard Dice is not a forecast of workflow performance. Evaluate instance-wise on your own instrument, count merges and splits separately, and assume generalization breaks until you have tested it — the substance behind [verified outputs](/lab-notes/why-microscopy-needs-verified-outputs/).

References

References

Local graph