Diffusion Model

A diffusion model learns to reverse a gradual noising process: it is trained to denoise corrupted data and generates samples by iteratively denoising from noise.

A common forward noising form is:

The model is often trained to predict , , or a related velocity target.

Forward Process

In discrete-time DDPM notation:

and the closed-form marginal is:

where:

This marginal is what allows training with randomly sampled timesteps instead of simulating every forward step.

A common noise-prediction objective is:

The reverse process samples from noise by repeatedly applying a learned denoising transition:

Alternative parameterizations predict or velocity :

The parameterization affects stability, guidance behavior, and solver design.

Parameterization Choices

TargetModel PredictsUseful WhenCaveat
noise classic DDPM-style trainingsample quality depends on noise schedule and solver
clean data interpretable reconstruction targetcan be unstable at high noise
scorescore-based SDE/ODE viewscale depends on noise convention
velocity diffusion/flow bridge and stable interpolationmust define convention

For the common parameterization

a velocity target is often written:

Always record which target a paper uses before comparing losses or samplers.

The score associated with the same Gaussian convention is:

with in the simple variance-preserving notation. This connects diffusion noise prediction to score-based models.

Conditioning

Conditional diffusion adds context :

Guidance changes the effective score or denoising direction, which can improve fidelity but reduce diversity.

Classifier-free guidance often combines conditional and unconditional predictions:

where is the guidance scale. Larger can improve condition satisfaction while reducing diversity or validity.

Sampling Budget

Diffusion quality is tied to solver and step count:

where represents sampler settings such as stochasticity, guidance scale, schedule, and step size. A benchmark should report these settings because a model can look better simply by spending more sampling steps or stronger guidance.

Sampler Families

SamplerShapeClaim Affected
ancestral DDPMstochastic reverse chaindiversity and baseline comparability
DDIM-styledeterministic or partially stochastic trajectoryfewer steps, different diversity
SDE samplerstochastic continuous-time reverse processscore quality and noise schedule
probability-flow ODEdeterministic score-derived ODElikelihood route and solver budget
distilled/consistency samplerone or few stepsspeed at possible quality loss

NFE, wall time, memory, and invalid-sample denominator should be reported with sample quality.

Evaluation Boundary

ClaimRequired Evidence
better likelihood or denoisingNLL/ELBO or denoising loss under matched schedule
better sample qualitytask-specific sample metrics and human/domain checks
better conditional controlcondition satisfaction measured separately from diversity
faster generationquality at matched NFE, wall time, memory, and hardware
better molecular/protein samplesvalidity, novelty, diversity, constraints, and downstream utility

Why It Matters

  • Strong sample quality and stable training across images, molecules, and proteins.
  • Flexible conditioning enables guided and inverse-problem generation.
  • Iterative sampling is the main cost, motivating faster samplers.

Failure Modes

  • Too few sampling steps can produce invalid or low-detail samples.
  • Strong guidance can collapse diversity or overfit the condition.
  • The noise schedule may be poorly matched to data scale or geometry.
  • Evaluation can confuse validity, novelty, diversity, and downstream utility.

Checks

  • Does the noise schedule fit the data scale?
  • Is conditioning/guidance trading diversity for fidelity?
  • How many sampling steps are needed for acceptable quality?
  • Are sampling steps and guidance scales fixed across comparisons?
  • Is the prediction target , , score, or velocity clearly stated?
  • Are NFE, solver, stochasticity, and guidance scale matched across baselines?
  • Are validity, diversity, novelty, and task utility reported separately?
  • Is the noising convention variance-preserving, variance-exploding, or another schedule?
  • Are filtered or repaired samples counted in the denominator?