Papers › MolCRAFT: Structure-Based Drug Design in Continuous Parameter Space

MolCRAFT: Structure-Based Drug Design in Continuous Parameter Space

18 Apr 2024arXiv:2404.12141archive 2025-07-28

Yanru Qu, Keyue Qiu, Yuxuan Song, Jingjing Gong, Jiawei Han, Mingyue Zheng, Hao Zhou, Wei-Ying Ma

Generative models for structure-based drug design (SBDD) have shown promising results in recent years. Existing works mainly focus on how to generate molecules with higher binding affinity, ignoring the feasibility prerequisites for generated 3D poses and resulting in false positives. We conduct thorough studies on key factors of ill-conformational problems when applying autoregressive methods and diffusion to SBDD, including mode collapse and hybrid continuous-discrete space. In this paper, we introduce MolCRAFT, the first SBDD model that operates in the continuous parameter space, together with a novel noise reduced sampling strategy. Empirical results show that our model consistently achieves superior performance in binding affinity with more stable 3D structure, demonstrating our ability to accurately model interatomic interactions. To our best knowledge, MolCRAFT is the first to achieve reference-level Vina Scores (-6.59 kcal/mol) with comparable molecular size, outperforming other strong baselines by a wide margin (-0.84 kcal/mol). Code is available at https://github.com/AlgoMole/MolCRAFT.

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 MolCRAFT, 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). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='MolCRAFT') (how to connect); the free check have('2404.12141') needs no token.

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

Code

No sample from the archive's official repository (algomole/molcraft) is linked to this paper; the 11 samples below come from 2 repositories the archive does not mark official. Syntology harvested code from algomole/molcraft for 2 other papers.

algomole/molcraft: Syntology's graph links these samples to Empower Structure-Based Molecule Optimization with Gradient Guided Bayesian Flow Networks (arXiv:2411.13280; that paper's own run record: 0 ran · 4 unverified) and Piloting Structure-Based Drug Design via Modality-Specific Optimal Schedule (arXiv:2505.07286; that paper's own run record: 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); nothing checks that they implement this paper's method.

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

By repository: community (archive-listed): 9 samples from 1 repository, 6 ran (2 with no instrument failure; 4 where Syntology's instrument failed); found in paper text by Syntology: 2 samples from 1 repository, 2 ran (2 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

algomole/molcraft officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Empower Structure-Based Molecule Optimization with Gradient Guided Bayesian Flow Networks (arXiv:2411.13280; that paper's own run record: 0 ran · 4 unverified) and Piloting Structure-Based Drug Design via Modality-Specific Optimal Schedule (arXiv:2505.07286; that paper's own run record: 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); nothing checks that they implement this paper's method. report
AlgoMole/GeoBFN mentioned on GitHubpytorchSyntology: 9 samples, 6 ran (4 instrument-failed) · 3 unverified 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

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

Licence: 11 of the 11 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 2 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.

AlgoMole/GeoBFN community (archive-listed) 9 samples, 6 ran (4 instrument-failed) · 3 unverified
clip_noise_schedule in 7 papers core/losses/loss_utils.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 227cedce4e185b09 · report fixture: signature alphas2:ndarray/1/float, clip_value:float/0/float · returned ndarray · level recorded 2026-09-24
coord2diff in 7 papers core/module/egnn_new.py ran; the contract check could not run (RAISES) no licence file found · pointer only · e9fb6b7c8ea39384 · report fixture: signature x:Tensor/2/float, edge_index:tuple/1/Tensor, norm_constant:int/0/int · returned tuple · level recorded 2026-09-22
cosine_beta_schedule in 76 papers core/losses/loss_utils.py ran no licence file found · pointer only · 963b75c89db024dd · report fixture: signature timesteps:int/0/int, s:float/0/float, raise_to_power:float/0/float · returned ndarray · level recorded 2026-09-24
get_edges in 20 papers core/module/egnn_clean.py ran · honoured contract fingerprinted no licence file found · pointer only · c2f9c401f5379aac · report fixture: signature n_nodes:int/0/int · returned list · level recorded 2026-09-24
unsorted_segment_mean in 27 papers core/module/egnn_clean.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only · bc66f19be57720e7 · report fixture: signature data:Tensor/2/float, segment_ids:Tensor/1/int, num_segments:int/0/int · returned Tensor · level recorded 2026-09-22
unsorted_segment_sum in 33 papers core/module/egnn_clean.py ran · our draft was wrong no licence file found · pointer only · 5fb62a78eb65d3d7 · report fixture: signature data:Tensor/2/float, segment_ids:Tensor/1/int, num_segments:int/0/int · returned Tensor · level recorded 2026-09-22
get_bond_order in 5 papers core/evaluation/bond_analyze.py unverified no licence file found · pointer only · ad93a44e4f1360e6 · report
parse_config in 30 papers core/config/config.py unverified no licence file found · pointer only · 105db6cd366459a3 · report
simplest_type core/config/config.py unverified no licence file found · pointer only · 4d94fb4d31cad179 · report
gnina/models found in paper text by Syntology 2 samples, 2 ran (0 instrument-failed) · 0 unverified
Net in 54 papers pytorch/default2018_model.py ran no licence file found · pointer only · 662bb12613df805e · report fixture: returned Net · level recorded 2026-09-22
View in 9 papers pytorch/default2018_model.py ran no licence file found · pointer only · 340f867cc788cfa1 · report fixture: returned View · level recorded 2026-09-22

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". 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.

2 assemblies on this paper: 1 harvested, 1 generated.

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

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

  1. update_coordinates_and_atom_types entry · level 3 · ran; the contract check could not run · a040162eae4650f88f0215dccf0c5d54dd8524ed1712e5deb8197bbfb9aa6d4c

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

  1. Net entry · level 1 · ran · 662bb12613df805e
  2. View helper · level 1 · ran · 340f867cc788cfa1

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

Tasks

Drug Design

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

DiffusionFocus

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