Papers › Diffusion Models for Implicit Image Segmentation Ensembles
Diffusion Models for Implicit Image Segmentation Ensembles
Julia Wolleb, Robin Sandkühler, Florentin Bieder, Philippe Valmaggia, Philippe C. Cattin
Diffusion models have shown impressive performance for generative modelling of images. In this paper, we present a novel semantic segmentation method based on diffusion models. By modifying the training and sampling scheme, we show that diffusion models can perform lesion segmentation of medical images. To generate an image specific segmentation, we train the model on the ground truth segmentation, and use the image as a prior during training and in every step during the sampling process. With the given stochastic sampling process, we can generate a distribution of segmentation masks. This property allows us to compute pixel-wise uncertainty maps of the segmentation, and allows an implicit ensemble of segmentations that increases the segmentation performance. We evaluate our method on the BRATS2020 dataset for brain tumor segmentation. Compared to state-of-the-art segmentation models, our approach yields good segmentation results and, additionally, detailed uncertainty maps.
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):
get_harvested_code_for_paper(arxiv_id="2112.03145")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2112.03145", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2112.03145")
Code
Syntology 19 code samples harvested from 2 repositories linked to this paper: 15 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 4 honoured, 0 violated, 1 with no contract checked; 10 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 2 samples from 1 repository, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 17 samples from 1 repository, 13 ran (3 with no instrument failure; 10 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 1 of its repositories that Syntology harvested for other papers:
- aimansnigdha/ambiguous-medical-image-segmentation-using-diffusion-models, community (archive-listed): harvested for another paper, listed under the repository
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. 2 of the 15 samples that ran have no recorded date.
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
19 samples harvested: 15 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 4 honoured, 0 violated, 1 with no contract checked; 10 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 9 of the 19 samples are pointer only, meaning Syntology does not serve that copy's text. For 9 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 2 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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
42c9692e3f59033f · report
fixture: signature pred:Tensor/2/float, targs:Tensor/2/float · returned Tensor · level recorded 2026-09-22 004f59ffcd28edcc · report
fixture: signature img:Tensor/2/float · returned Tensor · level recorded 2026-09-22 census: 4 implementations from 14 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 guided_diffusion/losses.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only ·
cfd76fd0d89574a4 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded 6cdc8772f5db6f48 · report
fixture: signature num_diffusion_timesteps:int/0/int, alpha_bar:callable/0/?, max_beta:float/0/float · returned ndarray · level recorded 2026-09-22 census: 6 implementations from 10 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 guided_diffusion/losses.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only ·
cd33283d615fb3d7 · report
fixture: signature x:Tensor/2/float, means:Tensor/2/float, log_scales:Tensor/2/float · returned Tensor · level recorded, date not recorded 141937afc98f8d1e · report
fixture: signature schedule_name:str/0/str, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded 2026-09-22 e41367ad14ff58fd · report
fixture: signature named_model_params:list/1/tuple · returned list · level recorded 2026-09-24 e20dd5102da3b050 · report
fixture: signature param_groups_and_shapes:list/1/tuple · returned list · level recorded 2026-09-24 bcd8b4acab199405 · report
fixture: signature format:str/0/str, ev_dir:str/0/str, log_suffix:str/0/str · returned HumanOutputFormat · level recorded 2026-09-24 e515a67f7f32e76d · report
fixture: signature comm:MockComm/0/?, local_name2valcount:dict/0/? · returned dict · level recorded 2026-09-26 census: 14 implementations from 24 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 · arg 4: rank 2, kind float, dtype float32 guided_diffusion/losses.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only ·
cf2798b666b231ca · report
fixture: signature mean1:Tensor/2/float, logvar1:Tensor/2/float, mean2:Tensor/2/float, logvar2:Tensor/2/float · returned Tensor · level recorded 2026-09-22 9b6e4e070473e76f · report
fixture: signature num_timesteps:int/0/int, section_counts:list/1/int · returned set · level recorded 2026-09-22 f7b9e18794a10023 · report
fixture: signature img:Tensor/2/float · returned Tensor · level recorded 2026-09-25 64fff1e30802b815 · report
fixture: signature param_group:list/1/tuple, master_param:Tensor/1/float · returned tuple · level recorded 2026-09-24 129b804760b3115f · report
fixture: signature module:callable/0/? · returned SimpleModule · level recorded 2026-09-22 ecd0fc28815b65ae · report
fe4eb545bbb728e0 · report
49a5e51a44d77a98 · report
17e660f0e95b0309 · report
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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