Papers › DoseDiff: Distance-aware Diffusion Model for Dose Prediction in Radiotherapy

DoseDiff: Distance-aware Diffusion Model for Dose Prediction in Radiotherapy

28 Jun 2023arXiv:2306.16324archive 2025-07-28

Yiwen Zhang, Chuanpu Li, Liming Zhong, Zeli Chen, Wei Yang, Xuetao Wang

Treatment planning, which is a critical component of the radiotherapy workflow, is typically carried out by a medical physicist in a time-consuming trial-and-error manner. Previous studies have proposed knowledge-based or deep-learning-based methods for predicting dose distribution maps to assist medical physicists in improving the efficiency of treatment planning. However, these dose prediction methods usually fail to effectively utilize distance information between surrounding tissues and targets or organs-at-risk (OARs). Moreover, they are poor at maintaining the distribution characteristics of ray paths in the predicted dose distribution maps, resulting in a loss of valuable information. In this paper, we propose a distance-aware diffusion model (DoseDiff) for precise prediction of dose distribution. We define dose prediction as a sequence of denoising steps, wherein the predicted dose distribution map is generated with the conditions of the computed tomography (CT) image and signed distance maps (SDMs). The SDMs are obtained by distance transformation from the masks of targets or OARs, which provide the distance from each pixel in the image to the outline of the targets or OARs. We further propose a multi-encoder and multi-scale fusion network (MMFNet) that incorporates multi-scale and transformer-based fusion modules to enhance information fusion between the CT image and SDMs at the feature level. We evaluate our model on two in-house datasets and a public dataset, respectively. The results demonstrate that our DoseDiff method outperforms state-of-the-art dose prediction methods in terms of both quantitative performance and visual quality.

PaperPDFCodeCode 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

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

By repository: official repository: 13 samples from 1 repository, 9 ran (5 with no instrument failure; 4 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.

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. 4 of the 9 samples that ran have no recorded date.

whisney/dosediff officialmentioned in paperpytorchMITSyntology: 13 samples, 9 ran (4 instrument-failed) · 4 unverified 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.

Code Syntology ran Syntology

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 3 honoured, 0 violated, 2 with no contract checked; 4 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 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.

3ran · honoured contract
4ran · our draft was wrong
2ran
4unverified

Licence: 6 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. For 6 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 whisney/dosediff. “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.

whisney/dosediff official repository 13 samples, 9 ran (4 instrument-failed) · 4 unverified
approx_standard_normal_cdf in 150 papers
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 MIT (permissive) here; the stored copy is pointer only · cfd76fd0d89574a4 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded
betas_for_alpha_bar in 123 papers guided_diffusion/gaussian_diffusion.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · 2ab2316ac6fdd869 · report fixture: signature num_diffusion_timesteps:int/0/int, alpha_bar:callable/0/?, max_beta:float/0/float · returned ndarray · level recorded, date not recorded
create_named_schedule_sampler in 58 papers guided_diffusion/resample.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 35572566acf61c78 · report fixture: signature name:str/0/str, diffusion:MockDiffusion/0/? · returned UniformSampler · level recorded 2026-09-22
discretized_gaussian_log_likelihood in 124 papers
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 MIT (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
get_3D_Dose_dif evaluate_openKBP.py ran MIT (permissive) · 807805b0abc0bf7b · report fixture: signature pred:ndarray/3/float, gt:ndarray/3/float, possible_dose_mask:ndarray/3/float · returned float32 · level recorded 2026-09-26
get_DVH_metrics evaluate_openKBP.py ran MIT (permissive) · 844d590aace920e3 · report fixture: signature _dose:ndarray/3/float, _mask:ndarray/3/float, mode:str/0/str, spacing:NoneType/0/? · returned dict · level recorded 2026-09-26
get_named_beta_schedule in 119 papers guided_diffusion/gaussian_diffusion.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · a086d6286a40b889 · report fixture: signature schedule_name:str/0/str, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded, date not recorded
normal_kl in 188 papers
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 MIT (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
zero_module in 184 papers guided_diffusion/nn.py ran · our draft was wrong MIT (permissive) · 129b804760b3115f · report fixture: signature module:callable/0/? · returned SimpleModule · level recorded 2026-09-22
avg_pool_nd in 83 papers guided_diffusion/nn.py unverified MIT (permissive) · ecd0fc28815b65ae · report
conv_nd in 94 papers guided_diffusion/nn.py unverified MIT (permissive) · fe4eb545bbb728e0 · report
load_file in 52 papers csv2nii.py unverified MIT (permissive) · 98a36741b705a3e9 · report
shape_data csv2nii.py unverified MIT (permissive) · 839a9b3e6ffc98e5 · report

Tasks

Computed Tomography (CT)DenoisingPrediction

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Diffusion

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