Papers › GeoDiff: a Geometric Diffusion Model for Molecular Conformation Generation

GeoDiff: a Geometric Diffusion Model for Molecular Conformation Generation

6 Mar 2022ICLR 2022 4arXiv:2203.02923archive 2025-07-28

Minkai Xu, Lantao Yu, Yang song, Chence Shi, Stefano Ermon, Jian Tang

Predicting molecular conformations from molecular graphs is a fundamental problem in cheminformatics and drug discovery. Recently, significant progress has been achieved with machine learning approaches, especially with deep generative models. Inspired by the diffusion process in classical non-equilibrium thermodynamics where heated particles will diffuse from original states to a noise distribution, in this paper, we propose a novel generative model named GeoDiff for molecular conformation prediction. GeoDiff treats each atom as a particle and learns to directly reverse the diffusion process (i.e., transforming from a noise distribution to stable conformations) as a Markov chain. Modeling such a generation process is however very challenging as the likelihood of conformations should be roto-translational invariant. We theoretically show that Markov chains evolving with equivariant Markov kernels can induce an invariant distribution by design, and further propose building blocks for the Markov kernels to preserve the desirable equivariance property. The whole framework can be efficiently trained in an end-to-end fashion by optimizing a weighted variational lower bound to the (conditional) likelihood. Experiments on multiple benchmarks show that GeoDiff is superior or comparable to existing state-of-the-art approaches, especially on large molecules.

PaperPDFConference PDFCodeCode 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 GEODIFF, 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='GEODIFF') (how to connect); the free check have('2203.02923') needs no token.

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

Code

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

By repository: official repository: 14 samples from 1 repository, 11 ran (7 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 3 of the 11 samples that ran have no recorded date.

minkaixu/geodiff officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 11 ran (4 instrument-failed) · 3 unverified report
seonghann/tsdiff mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Diffusion-based Generative AI for Exploring Transition States from 2D Molecular Graphs (arXiv:2304.12233; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 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

14 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 3 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 · honoured contract
3ran · our draft was wrong
1ran; the contract check could not run
6ran
3unverified

Licence: 2 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 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 minkaixu/geodiff. “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.

minkaixu/geodiff official repository 14 samples, 11 ran (4 instrument-failed) · 3 unverified
assemble_atom_pair_feature models/common.py ran MIT (permissive) · 27a01a34aebe121a · report fixture: signature node_attr:Tensor/2/float, edge_index:Tensor/2/int, edge_attr:Tensor/2/float · returned Tensor · level recorded 2026-09-24
generate_symmetric_edge_noise models/common.py ran MIT (permissive) · ab68381cba40254d · report fixture: signature num_nodes_per_graph:Tensor/1/int, edge_index:Tensor/2/int, edge2graph:Tensor/1/int, device:device/0/? · returned Tensor · level recorded 2026-09-25
get_beta_schedule in 66 papers models/epsnet/diffusion.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · ca0cea1ca1eeec89 · report fixture: signature beta_schedule:str/0/str, beta_start:float/0/float, beta_end:float/0/float, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded, date not recorded
get_distance in 25 papers models/geometry.py ran MIT (permissive) here; the stored copy is pointer only · 5befa7d29d90c70b · report fixture: signature pos:Tensor/2/float, edge_index:Tensor/2/int · returned Tensor · level recorded 2026-09-25
get_ensemble_energy eval_prop.py ran fingerprinted MIT (permissive) · 331254d07dafb6ca · report fixture: signature props:ndarray/2/float · returned ndarray · level recorded 2026-09-24
get_optimizer in 228 papers utils/common.py ran MIT (permissive) · 4c6d0b3e84364cbc · report fixture: signature cfg:OptimizerConfig/0/?, model:callable/0/? · returned Adam · level recorded 2026-09-24
get_prop_matrix eval_prop.py ran MIT (permissive) · b5ea28e5e1631ede · report fixture: signature data:MockData/0/? · returned ndarray · level recorded 2026-09-24
get_timestep_embedding in 138 papers
census: 11 implementations from 15 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 1, kind int, dtype int64
models/epsnet/diffusion.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · cb49209c125de1b4 · report fixture: signature timesteps:Tensor/1/int, embedding_dim:int/0/int · returned Tensor · level recorded, date not recorded
nonlinearity in 140 papers
census: 4 implementations from 11 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/epsnet/diffusion.py ran · our draft was wrong fingerprinted MIT (permissive) · 3137073275f8c21a · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded
repeat_batch utils/common.py ran · our draft was wrong MIT (permissive) · f5f36de2ea7941ea · report fixture: signature batch:callable/0/?, num_repeat:int/0/int · returned DataBatch · level recorded 2026-09-24
repeat_data utils/common.py ran · our draft was wrong MIT (permissive) · c1f07219e3023a8e · report fixture: signature data:callable/0/?, num_repeat:int/0/int · returned DataBatch · level recorded 2026-09-24
get_edge_encoder models/encoder/edge.py unverified MIT (permissive) · 9709623b5759d7ad · report
set_conformer_positions utils/chem.py unverified MIT (permissive) · 5ad06a60ad46fa2e · report
update_data_rdmol_positions utils/chem.py unverified MIT (permissive) · 4738ff7d50f1b6c7 · 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. 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". 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.

1 assembly on this paper: 0 harvested, 1 generated.

generated Assembly for GEODIFF (graph method: GEODIFF), 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. compute_mu_theta_from_epsilon entry · level 3 · ran · honoured contract · 72d88c422b1094194ec1883995a26823d60bcfcb46f7d0f399e9a5eb8d6b580c

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="2203.02923") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Drug Discovery

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