Papers › Score-Based Generative Models for Designing Binding Peptide Backbones

Score-Based Generative Models for Designing Binding Peptide Backbones

10 Oct 2023arXiv:2310.07051archive 2025-07-28

John D Boom, Matthew Greenig, Pietro Sormanni, Pietro Liò

Score-based generative models (SGMs) have proven to be powerful tools for designing new proteins. Designing proteins that bind a pre-specified target is highly relevant to a range of medical and industrial applications. Despite the flurry of new SGMs in the last year, there has been little systematic exploration of the impact of design choices in SGMs for protein design. Here we present LoopGen, a flexible SGM framework for the design of short binding peptide structures. We apply our framework to design antibody binding loop structures conditional on a target epitope and evaluate a variety of modelling choices in SGM-based protein design. We demonstrate that modelling residue orientations in addition to positions improves not only the quality of the output structures but also their diversity. Additionally, we identify variance schedules that result in significant performance improvements and observe patterns that may motivate the development of better schedules for protein design. Finally, we develop three novel tests to evaluate whether the model generates structures that are appropriately conditioned on an epitope, demonstrating that LoopGen's generated structures are dependent on the structure, sequence, and position of the epitope. Our findings will help guide future development and evaluation of generative models for binding proteins.

Code

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.

Code Syntology ran Syntology

5 samples harvested; 4 ran; 0 honoured the contract we drafted; 1 has no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

Licence: 5 of the 5 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 mgreenig/loopgen. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

Tasks

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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