Bring the mental model from Maximum Likelihood; this page will reuse it instead of restarting from zero.
Diffusion, Score-Based Models & Flow Matching
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.
01
Intuition
Build the mental picture first so the rest of the page has something to attach to.
Diffusion models generate by starting from noise and repeatedly denoising.
The forward process is easy: take a data vector, such as an image representation, and add a little noise, again and again, until it becomes almost pure Gaussian noise.
The reverse process is the learning problem: train a network that, given a slightly-noised sample, parameterizes reverse or noise-removal updates toward cleaner, data-like samples. Sampling repeatedly applies learned reverse updates.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
02
Math
Translate the story into symbols, assumptions, and a derivation you can inspect.
A common discrete-time forward process (DDPM-style) is:
where αˉt=∏s=1tαs and αs=1−βs for a noise schedule βs.
Equivalently, you can sample:
Training often uses the noise-prediction loss:
The "score" view connects denoising to the gradient of log-density ∇xlogpt(x). Under the Gaussian DDPM or VP corruption above, a learned noise predictor can be converted into an approximate score estimate:
Flow matching is a separate continuous-vector-field view and is only a forward pointer here.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
03
Code
Keep the implementation aligned with the notation so the algorithm is legible.
import numpy as np
T = 1000
beta = np.linspace(1e-4, 0.02, T)
alpha = 1.0 - beta
alpha_bar = np.concatenate([[1.0], np.cumprod(alpha)]) # alpha_bar[0]=1 (no noise)
x0 = np.array([1.0, -1.0])
for t in [0, 10, 100, 500, 1000]:
eps = np.random.randn(*x0.shape)
xt = np.sqrt(alpha_bar[t]) * x0 + np.sqrt(1.0 - alpha_bar[t]) * eps
print(f"t={t:>3} xt={np.round(xt, 3)} noise_std={np.sqrt(1.0 - alpha_bar[t]):.3f}")
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
04
Interactive Demo
Use direct manipulation to connect the explanation to a moving system.
Live Concept Demo
Explore Diffusion, Score-Based Models & Flow Matching
The stage is code-native and interactive. Use it to test the explanation against the mechanism.
Manipulate one control and predict the visible change.
Choose what to inspect in Diffusion, Score-Based Models & Flow Matching. This shared fallback is an observation guide, not evidence of learning.
This first lab isolates the DDPM forward process. Scrub t to watch
push a two-blob toy distribution toward a near-Gaussian noise cloud. Before checking, predict whether a fixed structure-match proxy crosses its threshold early, in the middle, or late. Score matching and flow matching are separate mechanisms and will be handled in their own focused labs.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
Concept: Diffusion, Score-Based Models & Flow Matching
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
Object contextGenerative Models
concept:generative-models/diffusionDiffusion, Score-Based Models & Flow Matching
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
Start with the prediction checkpoint, then compare the reveal to the mental model.
Take this moveStudy modes
Keep the object fixed; change the lens.Route back through the notebook
Carry the same object through intuition, math, code, and demo.
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.
The next edge should feel earned: use the demo prediction here before following Flow Matching & Rectified Flows.
After The First Pass
Turn the concept into an inspected object.
The lower panels are one second act: keep the object fixed, inspect it visually, check source boundaries, practice transfer, then attach the research question.Mechanism Storyboard
See the idea move before the page explains it
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.

Start with the picture, metaphor, or geometric mechanism.
Before reading further, choose the kind of change Diffusion, Score-Based Models & Flow Matching should make visible.
Visual Inquiry
Make the image answer a mathematical question
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.
Which visible object should carry the first intuition?
Pick the cue that should make Diffusion, Score-Based Models & Flow Matching easier to reason about before the page gives the answer.
Source Grounding
Canonical references for the mechanism on this page.
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
concept:generative-models/diffusionsources: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde
Open the closest source note before trusting the local explanation.
3 selected-object sources shown first; 3 references total.
Audit the claim boundary, then ask from the same selected object.
Early diffusion framing: a gradual noising process paired with learned reverse dynamics.
Sohl-Dickstein supports iterative forward corruption plus learned reverse diffusion. Ho supports the DDPM closed-form q(x_t|x_0), reparameterized x_t sample, and simplified L_simple epsil...
Exported math refs cover only q(x_t|x_0) and reparameterized x_t. Code/demo isolate forward noising/backward replay, not a trained sampler. Excludes guidance, latent diffusion, sampler va...
Grounds DDPM forward noising equations and simplified epsilon-prediction training; the page demo uses the forward noising equation.
Sohl-Dickstein supports iterative forward corruption plus learned reverse diffusion. Ho supports the DDPM closed-form q(x_t|x_0), reparameterized x_t sample, and simplified L_simple epsil...
Exported math refs cover only q(x_t|x_0) and reparameterized x_t. Code/demo isolate forward noising/backward replay, not a trained sampler. Excludes guidance, latent diffusion, sampler va...
Connects score-based modeling, diffusion processes, and reverse-time SDE sampling.
Sohl-Dickstein supports iterative forward corruption plus learned reverse diffusion. Ho supports the DDPM closed-form q(x_t|x_0), reparameterized x_t sample, and simplified L_simple epsil...
Exported math refs cover only q(x_t|x_0) and reparameterized x_t. Code/demo isolate forward noising/backward replay, not a trained sampler. Excludes guidance, latent diffusion, sampler va...
Claim Review
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
concept:generative-models/diffusionsources: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde
Treat every claim as provisional until source support and a local witness agree.
1 structured claim check on this concept.
Run the prediction or practice transfer before asking for a grounded review.
Publisher-side editorial review is not independent replication. Claims without it still need exact source-support review. 3 references and 3 local witnesses are available for inspection.
Sohl-Dickstein supports iterative forward corruption plus learned reverse diffusion. Ho supports the DDPM closed-form q(x_t|x_0), reparameterized x_t sample, and simplified L_simple epsilon-prediction MSE. S...
Exported math refs cover only q(x_t|x_0) and reparameterized x_t. Code/demo isolate forward noising/backward replay, not a trained sampler. Excludes guidance, latent diffusion, sampler variants, flow matchin...
Sohl-Dickstein supports iterative forward corruption plus learned reversal; Ho supports DDPM q(x_t|x_0), reparameterized x_t, and L_simple epsilon-MSE; Song grounds reverse-time SDE sampling from time-dependent scores. Local math/code/demo witness only forward noising; epsilon-MSE and Score-SDE mechanics are source-supported, not locally simulated.
Reviewer: codex+oracle+codex-5.3; reviewed 2026-05-08Practice notebook
Use the idea, then test it somewhere new
Denoise noise into data: the diffusion forward process, score matching, and modern sampling via reverse-time dynamics and flow matching.
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
concept:generative-models/diffusionsources: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde
Use one state from Diffusion, Score-Based Models & Flow Matching to explain what changes, why it changes, and which assumption the explanation needs.
No learner move yet; no learning state is inferred.
Write first, use only the help you need, then try a new case without it.
Use one state from Diffusion, Score-Based Models & Flow Matching to explain what changes, why it changes, and which assumption the explanation needs.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Write an attempt before asking the companion.
0 of 3 progressive hints opened.
This draft and any AI response do not establish mastery; a later unassisted case can.
- ObjectConceptDiffusion, Score-Based Models & Flow Matching
- PredictBefore revealDiffusion, Score-Based Models & Flow Matching prediction
- WitnessCompare codeDiffusion, Score-Based Models & Flow Matching code witness 1
- RoomAsk groundedChecking local snapshot
Research Room
Attach the question to an exact object
Pick the concept, equation, source, code witness, claim, misconception, or demo state before asking for help. The handoff stays grounded to that object.Open the draft below to save one note and next action in this browser.
Diffusion, Score-Based Models & Flow Matching
What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math?
These are fixed, deterministic perspectives derived from the selected object. They do not represent people, community contributions, or independent review.
Source ids sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde must support the exact object, not just the surrounding topic.
Treat this as a mechanism object: connect the definition to one equation, code witness, or demo before broadening the discussion.
Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo.
The learner can state the mechanism in their own words
Local action draftNo local draft saved yetExpand only when ready to capture one local next action
This draft stays locally in this browser for concept:generative-models/diffusion.
- Source ids to inspect: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde
- Definition, prerequisite, and contrast concept links
- The equation or code witness that makes the concept operational
- One demo state that shows the invariant instead of a slogan
- The learner can state the mechanism in their own words
- The learner can name the prerequisite that would repair confusion
- The learner can predict how the mechanism changes under one perturbation
I am working in Continuous Function's research reading room. Object: concept - Diffusion, Score-Based Models & Flow Matching Object key: concept:generative-models/diffusion Context: Generative Models Anchor id: concept/concept-notebook/generative-models/diffusion Open question: What is the smallest example that makes Diffusion, Score-Based Models & Flow Matching click without losing the math? Evidence to inspect: - Source ids to inspect: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde - Definition, prerequisite, and contrast concept links - The equation or code witness that makes the concept operational - One demo state that shows the invariant instead of a slogan Deterministic role lenses for this object: - Boundary: fixed perspectives, not people, community contributions, or independent review - Source-checking summary: Treat this as a mechanism object: connect the definition to one equation, code witness, or demo before broadening the discussion. - Proposed experiment: Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo. - Teach/transfer move: Turn the mechanism into one sentence that predicts a neighboring concept. - Assumptions: - Source ids sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde must support the exact object, not just the surrounding topic. - The stable content-object key lets local drafts, prompts, and route memory attach without changing the source page. - The concept explanation is local atlas prose until checked against its math, code, and source support. - Prerequisite gaps should become a repair route, not a reason to leave the object vague. - Role-lens requests: - Learner: ask for "Ask what would make "Diffusion, Score-Based Models & Flow Matching" feel predictable rather than familiar." | assumption: Source ids sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde must support the exact object, not just the surrounding topic. | next action: The learner can state the mechanism in their own words - Researcher: ask for "Source ids to inspect: sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde" | assumption: The stable content-object key lets local drafts, prompts, and route memory attach without changing the source page. | next action: The learner can name the prerequisite that would repair confusion - Experimenter: ask for "Choose one variable or condition to perturb before asking for an explanation." | assumption: The concept explanation is local atlas prose until checked against its math, code, and source support. | next action: The learner can predict how the mechanism changes under one perturbation - Professor: ask for "Find the smallest transferable rule a learner could reuse without the AI." | assumption: Prerequisite gaps should become a repair route, not a reason to leave the object vague. | next action: Teach or transfer: Turn the mechanism into one sentence that predicts a neighboring concept. What would resolve this: - The learner can state the mechanism in their own words - The learner can name the prerequisite that would repair confusion - The learner can predict how the mechanism changes under one perturbation Answer as a careful research tutor: stay source-grounded, separate verified evidence from assumptions, name the relevant math objects, and end with one next action. Current deterministic role lens for this object: - Role lens: Learner - Evidence request: Ask what would make "Diffusion, Score-Based Models & Flow Matching" feel predictable rather than familiar. - Assumption to keep visible: Source ids sohl-dickstein-2015-nonequilibrium, ho-2020-ddpm, song-2020-score-sde must support the exact object, not just the surrounding topic. - Proposed experiment: Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo. - Next action: The learner can state the mechanism in their own words
concept/concept-notebook/generative-models/diffusion
concept:generative-models/diffusion