Methods › General › Loss Functions › Dice Loss

Dice Loss

108 papers tagged archive 2025-07-28

Introduced by Carole H. Sudre et al. in Generalised Dice overlap as a deep learning loss function for highly unbalanced segmentations

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

DiceLoss( y, p ) = 1 - ( 2yp + 1 ) ( y+p + 1 )

PaperSource

In Syntology for a different name, 'DICE', about another paper, arXiv:2101.05544: verified reference implementation at level V2; retrieve with get_reference_implementation(name='DICE'). The lookup matched a different name in Syntology's graph, 'DICE' (resolution: token_match); this answer is about that name. About another paper: this answer is about arXiv:2101.05544, while the archive credits arXiv:1707.03237.

Origin paper of this answer, arXiv:2101.05544 (its page on Syntology).

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 108 · with a code link: 47 · where Syntology ran a sample: 5 (3 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (5 of 108 tagged: 3 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument)

Page 1 of 2: papers 1 to 100 of 108, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “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. It is per sample and not a correctness claim. 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; “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.

Tasks archive 2025-07-28

20 shown of 96 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Segmentation58
Semantic Segmentation43
Image Segmentation28
Medical Image Segmentation17
Tumor Segmentation13
Decoder11
Brain Tumor Segmentation9
Computed Tomography (CT)5
Data Augmentation5
Deep Learning5
Lesion Segmentation5
Anatomy4
Specificity4
Boundary Detection3
Diagnostic3
General Classification3
Medical Image Analysis3
Survival Prediction3
Anomaly Detection2
Attribute2

Usage over time archive 2025-07-28

Papers per year tagged with Dice Loss: 2017 to 2025, peak 19 19 0 2017: 1 paper 2017 2018: 9 papers 2018 2019: 18 papers 2019 2020: 19 papers 2020 2021: 12 papers 2021 2022: 18 papers 2022 2023: 11 papers 2023 2024: 9 papers 2024 2025: 11 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (108 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Loss Functions

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