Papers › A Probabilistic U-Net for Segmentation of Ambiguous Images

A Probabilistic U-Net for Segmentation of Ambiguous Images

13 Jun 2018NeurIPS 2018 12arXiv:1806.05034archive 2025-07-28

Simon A. A. Kohl, Bernardino Romera-Paredes, Clemens Meyer, Jeffrey De Fauw, Joseph R. Ledsam, Klaus H. Maier-Hein, S. M. Ali Eslami, Danilo Jimenez Rezende, Olaf Ronneberger

Many real-world vision problems suffer from inherent ambiguities. In clinical applications for example, it might not be clear from a CT scan alone which particular region is cancer tissue. Therefore a group of graders typically produces a set of diverse but plausible segmentations. We consider the task of learning a distribution over segmentations given an input. To this end we propose a generative segmentation model based on a combination of a U-Net with a conditional variational autoencoder that is capable of efficiently producing an unlimited number of plausible hypotheses. We show on a lung abnormalities segmentation task and on a Cityscapes segmentation task that our model reproduces the possible segmentation variants as well as the frequencies with which they occur, doing so significantly better than published approaches. These models could have a high impact in real-world applications, such as being used as clinical decision-making algorithms accounting for multiple plausible semantic segmentation hypotheses to provide possible diagnoses and recommend further actions to resolve the present ambiguities.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

No sample from the archive's official repository (SimonKohl/probabilistic_unet) is linked to this paper; the 9 samples below come from 4 community repositories. Syntology harvested code from SimonKohl/probabilistic_unet for another paper.

SimonKohl/probabilistic_unet: Syntology's graph links these samples to A Hierarchical Probabilistic U-Net for Modeling Multi-Scale Ambiguities (arXiv:1905.13077; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method.

Syntology 9 code samples harvested from 4 repositories linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 9 samples from 4 repositories, 7 ran (5 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

SimonKohl/probabilistic_unet officialmentioned in papermentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Hierarchical Probabilistic U-Net for Modeling Multi-Scale Ambiguities (arXiv:1905.13077; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
MIC-DKFZ/probabilistic_unet mentioned on GitHubtfApache-2.0Syntology: 6 samples, 4 ran (1 instrument-failed) · 2 unverified report
Usman-Rafique/Probabilistic_UNet mentioned on GitHubpytorchSyntology: not harvested report
cviviers/prob_3d_segmentation mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
jenspetersen/probabilistic-unet mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
kilgore92/Probabalistic-U-Net mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to U-Net: Convolutional Networks for Biomedical Image Segmentation (arXiv:1505.04597; that paper's own run record: 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); nothing checks that they implement this paper's method. report
rizalmaulanaa/robustness_of_prob_u_net mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to U-Net: Convolutional Networks for Biomedical Image Segmentation (arXiv:1505.04597; that paper's own run record: 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); nothing checks that they implement this paper's method. report
stefanknegt/Probabilistic-Unet-Pytorch mentioned on GitHubpytorchApache-2.0Syntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
stefanknegt/probabilistic_unet_pytorch mentioned on GitHubpytorchApache-2.0Syntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
2ran
2unverified

Licence: 0 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

MIC-DKFZ/probabilistic_unet community (archive-listed) 6 samples, 4 ran (1 instrument-failed) · 2 unverified
get_array_of_modes evaluation/eval_cityscapes.py ran · our draft was wrong Apache-2.0 (permissive) · 65cc4cdcce48e4cb · report fixture: signature cf:Config/0/?, seg:ndarray/4/int · returned ndarray · level recorded 2026-09-22
get_array_of_samples evaluation/eval_cityscapes.py ran · honoured contract Apache-2.0 (permissive) · d600a3dd3ae5b79f · report fixture: signature cf:Config/0/?, img_key:str/0/str · returned ndarray · level recorded 2026-09-22
numpy_one_hot utils/training_utils.py ran Apache-2.0 (permissive) · 73daa4c05abbf736 · report fixture: signature label_arr:ndarray/2/int, num_classes:int/0/int · returned ndarray · level recorded 2026-09-26
softmax_2_onehot utils/training_utils.py ran fingerprinted Apache-2.0 (permissive) · 394d537f276d03c2 · report fixture: signature arr:ndarray/2/float · returned ndarray · level recorded 2026-09-26
ce_loss in 34 papers utils/training_utils.py unverified Apache-2.0 (permissive) · 1154f612e91c9287 · report
get_mode_counts evaluation/eval_cityscapes.py unverified Apache-2.0 (permissive) · 0621b823c2321b0f · report
cviviers/prob_3d_segmentation community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
get_model in 368 papers pytorch3dunet/unet3d/model.py ran · our draft was wrong MIT (permissive) · 7c3bc634ea8906ac · report fixture: signature model_config:dict/0/? · returned UNet3D · level recorded 2026-09-22
jenspetersen/probabilistic-unet community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
is_conv probunet/model.py ran · violated contract MIT (permissive) · 0a5cbe60b0814cee · report fixture: signature op:callable/0/? · returned bool · level recorded 2026-09-22
stefanknegt/Probabilistic-Unet-Pytorch community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
l2_regularisation in 7 papers utils.py ran · honoured contract Apache-2.0 (permissive) · c23b05634625d281 · report fixture: signature m:callable/0/? · returned Tensor · level recorded 2026-09-22

Tasks

Decision MakingSegmentationSemantic Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Concatenated Skip ConnectionConvolutionMax PoolingReLUU-Net

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