Papers › DPM-Solver: A Fast ODE Solver for Diffusion Probabilistic Model Sampling in Around 10 Steps

DPM-Solver: A Fast ODE Solver for Diffusion Probabilistic Model Sampling in Around 10 Steps

2 Jun 2022arXiv:2206.00927archive 2025-07-28

Cheng Lu, Yuhao Zhou, Fan Bao, Jianfei Chen, Chongxuan Li, Jun Zhu

Diffusion probabilistic models (DPMs) are emerging powerful generative models. Despite their high-quality generation performance, DPMs still suffer from their slow sampling as they generally need hundreds or thousands of sequential function evaluations (steps) of large neural networks to draw a sample. Sampling from DPMs can be viewed alternatively as solving the corresponding diffusion ordinary differential equations (ODEs). In this work, we propose an exact formulation of the solution of diffusion ODEs. The formulation analytically computes the linear part of the solution, rather than leaving all terms to black-box ODE solvers as adopted in previous works. By applying change-of-variable, the solution can be equivalently simplified to an exponentially weighted integral of the neural network. Based on our formulation, we propose DPM-Solver, a fast dedicated high-order solver for diffusion ODEs with the convergence order guarantee. DPM-Solver is suitable for both discrete-time and continuous-time DPMs without any further training. Experimental results show that DPM-Solver can generate high-quality samples in only 10 to 20 function evaluations on various datasets. We achieve 4.70 FID in 10 function evaluations and 2.87 FID in 20 function evaluations on the CIFAR10 dataset, and a 4∼16× speedup compared with previous state-of-the-art training-free samplers on various datasets.

PaperPDFCodeCode Syntology ranMethod as code

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.

Syntology holds a reference implementation of DPM-Solver, generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: 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.” (quoted from Syntology's server card). For this implementation, level 3 is recorded, but its report lists no property test that passed on both. No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='DPM-Solver') (how to connect); the free check have('2206.00927') needs no token.

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

Code

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

By repository: official repository: 4 samples from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 17 samples from 3 repositories, 15 ran (12 with no instrument failure; 3 where Syntology's instrument failed); community: 3 samples from 1 repository, 1 ran (1 with no instrument failure; 0 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:

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. 1 of the 17 samples that ran has no recorded date.

luchengthu/dpm-solver officialmentioned in papermentioned on GitHubjaxSyntology: 4 samples, 1 ran (0 instrument-failed) · 3 unverified report
astra-vision/LiDPM mentioned on GitHubpytorchApache-2.0Syntology: 12 samples, 11 ran (1 instrument-failed) · 1 unverified report
thomaskerdreux/pdm_sar_insar_generation mentioned on GitHubpytorchSyntology: 4 samples, 3 ran (2 instrument-failed) · 1 unverified report
MaximeVandegar/Papers-in-100-Lines-of-Code pytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
probabilists/azula pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Fast Sampling of Diffusion Models with Exponential Integrator (arXiv:2204.13902; that paper's own run record: 12 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 9 where Syntology's instrument failed) · 14 unverified) and Diffusion Posterior Sampling for General Noisy Inverse Problems (arXiv:2209.14687; that paper's own run record: 6 ran (of which 4 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 1 violated, 4 with no contract checked; 1 where Syntology's instrument failed) · 14 unverified); nothing checks that they implement this paper's method. 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

24 samples harvested: 17 ran (of which 2 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 1 violated, 13 with no contract checked; 3 where Syntology's instrument failed) · 7 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.

1ran · violated contract
3ran · our draft was wrong
13ran
7unverified

Licence: 0 of the 24 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 5 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.

luchengthu/dpm-solver official repository 4 samples, 1 ran (0 instrument-failed) · 3 unverified
DPM_Solver dpm_solver_pytorch.py ran MIT (permissive) · 18673fd093501c14 · report fixture: returned DPM_Solver · level recorded 2026-09-22
interpolate_fn in 42 papers examples/score_sde_jax/dpm_solver.py unverified MIT (permissive) · 8f6335e1c872cedc · report
model_wrapper in 37 papers examples/score_sde_jax/dpm_solver.py unverified MIT (permissive) · aafc0d7013851789 · report
astra-vision/LiDPM community (archive-listed) 12 samples, 11 ran (1 instrument-failed) · 1 unverified
cosine_beta_schedule in 76 papers lidpm/utils/scheduling.py ran fingerprinted Apache-2.0 (permissive) · 2844790a72cc7fd1 · report fixture: signature timesteps:int/0/int, s:float/0/float · returned Tensor · level recorded 2026-09-24
feats_to_coord lidpm/utils/collations.py ran Apache-2.0 (permissive) · b8a1f3b1f37f7fde · report fixture: signature p_feats:Tensor/2/float, resolution:float/0/float, bs:int/0/int, dim:int/0/int · returned Tensor · level recorded 2026-09-24
linear_beta_schedule in 42 papers lidpm/utils/scheduling.py ran fingerprinted Apache-2.0 (permissive) · 84a1879c66fb8e8b · report fixture: signature timesteps:int/0/int, beta_start:float/0/float, beta_end:float/0/float · returned Tensor · level recorded 2026-09-26
load_config in 389 papers lidpm/utils/configs.py ran Apache-2.0 (permissive) · 33bdf42966c6d6f3 · report fixture: signature file_path:str/0/str · returned dict · level recorded 2026-09-24
load_poses in 11 papers lidpm/utils/pcd_preprocess.py ran Apache-2.0 (permissive) · dd375501c42dd070 · report fixture: signature path:str/0/str, calib_fname:str/0/str, poses_fname:str/0/str · returned list · level recorded 2026-09-24
parse_calibration in 7 papers lidpm/utils/pcd_preprocess.py ran · our draft was wrong Apache-2.0 (permissive) · b39e1616e4146e48 · report fixture: signature filename:str/0/str · returned dict · level recorded 2026-09-26
quadratic_beta_schedule in 9 papers lidpm/utils/scheduling.py ran fingerprinted Apache-2.0 (permissive) · f9097d641770f184 · report fixture: signature timesteps:int/0/int, beta_start:float/0/float, beta_end:float/0/float · returned Tensor · level recorded 2026-09-26
random_flip_point_cloud lidpm/utils/pcd_transforms.py ran fingerprinted Apache-2.0 (permissive) · 418cad3868631abf · report fixture: signature batch_data:ndarray/3/float, scale_low:float/0/float, scale_high:float/0/float · returned ndarray · level recorded 2026-09-24
rotate_perturbation_point_cloud lidpm/utils/pcd_transforms.py ran fingerprinted Apache-2.0 (permissive) · 0fb3faa4f806ee7a · report fixture: signature batch_data:ndarray/3/float, angle_sigma:float/0/float, angle_clip:float/0/float · returned ndarray · level recorded 2026-09-25
rotate_point_cloud in 17 papers lidpm/utils/pcd_transforms.py ran fingerprinted Apache-2.0 (permissive) · a9f27fc650c1d8ce · report fixture: signature batch_data:ndarray/3/float · returned ndarray · level recorded 2026-09-25
smart_config lidpm/utils/configs.py ran Apache-2.0 (permissive) · 22c48367db1c5906 · report fixture: signature config_path:str/0/str, ctx:MockContext/0/? · returned dict · level recorded 2026-09-24
convert_inf lidpm/utils/callbacks.py unverified Apache-2.0 (permissive) · 87d3711ace93ad00 · report
thomaskerdreux/pdm_sar_insar_generation community (archive-listed) 4 samples, 3 ran (2 instrument-failed) · 1 unverified
NoiseScheduleVP utils/utils_sample_DPM.py ran fingerprinted MIT (permissive) · c1dc4eb5c194ce8d · report fixture: signature t:Tensor/2/float · returned Tensor · level recorded 2026-09-24
expand_dims in 38 papers
census: 6 implementations from 13 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 1, kind float, dtype float32
utils/utils_sample_DPM.py ran · our draft was wrong MIT (permissive) · b68777351ff35e18 · report fixture: signature v:Tensor/1/float, dims:int/0/int · returned Tensor · level recorded 2026-09-22
interpolate_fn in 42 papers utils/utils_sample_DPM.py ran · our draft was wrong fingerprinted MIT (permissive) · 75f87754036e8581 · report fixture: signature x:Tensor/2/float, xp:Tensor/2/float, yp:Tensor/2/float · returned Tensor · level recorded 2026-09-22
DPM_Solver utils/utils_sample_DPM.py unverified MIT (permissive) · c92037e529d03d02 · report
MaximeVandegar/Papers-in-100-Lines-of-Code community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
DiffusionModel in 14 papers DPM_Solver_A_Fast_ODE_Solver_for_Diffusion_Probabilistic_Model_Sampling_in_Around_10_Steps/dpm_solver.py ran MIT (permissive) · aeb2f4987825e6b3 · report fixture: returned DiffusionModel · level recorded 2026-09-22
thu-ml/DPM-Solver-v3 community 3 samples, 1 ran (0 instrument-failed) · 2 unverified
index_list codebases/score_sde/samplers/dpm_solver_v3.py ran · violated contract MIT (permissive) · 522ab9ee79479d93 · report fixture: signature lst:list/1/int, index:list/1/int · returned list · level recorded, date not recorded
weighted_cumsumexp_trapezoid codebases/score_sde/samplers/dpm_solver_v3.py unverified MIT (permissive) · 62681c73cc1d446e · report
weighted_cumsumexp_trapezoid_torch codebases/score_sde/samplers/dpm_solver_v3.py unverified MIT (permissive) · 510b207c6841a775 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another. Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

4 assemblies on this paper: 3 harvested, 1 generated, listed in 2 groups (siblings lifted in one batch form one group).

generated Assembly for DPM-Solver (graph method: DPM-Solver), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer; level 3 is recorded, but its report lists no property test that passed on both.

label matches by construction: the code was generated for this method (not judged by a model)

  1. dpm_solver_2_step entry · level 3 · ran · honoured contract · 51903ba1c20890ea660422c374c662ef965f87af721c6ff898baba9223a98285

3 sibling assemblies for DPM-Solver (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for DPM-Solver (graph method: DPM-Solver). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 3 siblings

  1. DiffusionModel entry · level 1 · ran · aeb2f4987825e6b3

harvested Assembly for DPM-Solver (graph method: DPM-Solver). 2 bricks; individually on a fixture: 2 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. DPM_Solver entry · level 1 · ran · 18673fd093501c14
  2. expand_dims helper · level 1 · ran · our draft was wrong · e6110366588c5c65

harvested Assembly for DPM-Solver (graph method: DPM-Solver). 4 bricks; individually on a fixture: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. DPM_Solver entry · level 0 · unverified · c92037e529d03d02
  2. NoiseScheduleVP scheduler · level 1 · ran · c1dc4eb5c194ce8d
  3. expand_dims helper · level 1 · ran · our draft was wrong · b68777351ff35e18
  4. interpolate_fn helper · level 1 · ran · our draft was wrong · 75f87754036e8581

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2206.00927") returns these assemblies with each brick's role and wiring (how to connect).

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