State of Proof

Physics · Research method · Peer reviewed · examination not started

Generative diffusion surrogates with analytical variance schedule

Patrick Reichherzer, Gianluca Gregori, David N. Hosking and Subir Sarkar

Source date: 2026-10-08 · Added: 2026-10-15 · Record updated:

Inclusion is not validation. This is an intake record and proposed check plan, not a completed examination or a peer-review decision. Any separate docket states its own exact source and scope.

Physics · Research method · Peer reviewed

Candidate · added · 2609.01705

Blue and teal particles spread along curved field lines inside an amber envelope.
Conceptual illustration · not experimental data, a reproduction, or a proof certificate

Teach AI the physics before asking it to simulate

What it is
A diffusion-model surrogate whose noise schedule follows an analytical law for particle spreading.
Who did it
Patrick Reichherzer, Gianluca Gregori, David N. Hosking and Subir Sarkar.
What it could mean
Could improve calibrated simulations and inference for stochastic transport, within the tested physical regimes.

Examination not started · source-reported evidence

See the check plan

Evidence & validation

From announcement to evidence

Discovery recorded. The source reports the evidence below; State of Proof has not independently reproduced the work.

  1. Read the original work

    Generative diffusion surrogates with analytical variance schedule ↗

    Patrick Reichherzer, Gianluca Gregori, David N. Hosking and Subir Sarkar

  2. See the proposed checks

    Reproduce one simulation comparison, including variance and higher moments, against a conventional test-particle baseline.

  3. Independent examination not started

    Peer review, simulation comparisons, laboratory evidence and independent replication are distinct. Inclusion here does not establish all of them; see the record’s source and current boundary.

    How we distinguish research evidence →
How validation works →

Physics gives a learned simulation its clock

The spreading cloud introduces transport and a variance-based schedule. The envelope and field lines are conceptual, not measured data or a reproduced simulation.

Read the source · Abstract and method · analytical transport variance schedule ↗
Source kind
Physics-informed simulation method
Evidence reported
Peer-reviewed article; Simulation comparisons; Laboratory variance-scale comparison
AI role
A diffusion model learns distributional shape while a known variance law sets its schedule.
Human role
Researchers specify the physical law and compare simulations and laboratory measurements.
Source date
; added 2026-10-15
What it claims
The authors anchor a diffusion model's schedule to a known transport variance law and report agreement with particle simulations and a laboratory-measured variance scale.
Why this could matter
Teach AI the physics before asking it to simulate Known physics can provide a physical clock for a learned particle-transport surrogate. Matching variance does not ensure every feature of the distribution or microscopic dynamics is correct.
If it holds up
Researchers could build transport surrogates with a meaningful clock and fewer arbitrary schedule choices.
If it does not
Higher moments or untested transport regimes would reveal the surrogate's limits.
Impact horizon
Methods · Particle transport · Scientific simulation
Version
Nature Communications version of record
Why we tracked it
The journal article appeared October 8; its preprint dates to September 1.
Highest-risk dependency
Enforcing the variance does not enforce full distributions, finite propagation speed, memory or trajectory correlations.
Available artifacts
Journal manuscript, figures and linked availability statements; no source code or data executed by State of Proof.
Current boundary
Intake record only; examination not started. Peer-reviewed method recorded from its source; independent examination and reproduction have not started. No new physical law or practical fusion gain is established here.

Back to this paper in Paper Watch · Public records as JSON · Suggest a correction