Papers › Hotspot-Driven Peptide Design via Multi-Fragment Autoregressive Extension

Hotspot-Driven Peptide Design via Multi-Fragment Autoregressive Extension

26 Nov 2024arXiv:2411.18463archive 2025-07-28

Jiahan Li, Tong Chen, Shitong Luo, Chaoran Cheng, Jiaqi Guan, Ruihan Guo, Sheng Wang, Ge Liu, Jian Peng, Jianzhu Ma

Peptides, short chains of amino acids, interact with target proteins, making them a unique class of protein-based therapeutics for treating human diseases. Recently, deep generative models have shown great promise in peptide generation. However, several challenges remain in designing effective peptide binders. First, not all residues contribute equally to peptide-target interactions. Second, the generated peptides must adopt valid geometries due to the constraints of peptide bonds. Third, realistic tasks for peptide drug development are still lacking. To address these challenges, we introduce PepHAR, a hot-spot-driven autoregressive generative model for designing peptides targeting specific proteins. Building on the observation that certain hot spot residues have higher interaction potentials, we first use an energy-based density model to fit and sample these key residues. Next, to ensure proper peptide geometry, we autoregressively extend peptide fragments by estimating dihedral angles between residue frames. Finally, we apply an optimization process to iteratively refine fragment assembly, ensuring correct peptide structures. By combining hot spot sampling with fragment-based extension, our approach enables de novo peptide design tailored to a target protein and allows the incorporation of key hot spot residues into peptide scaffolds. Extensive experiments, including peptide design and peptide scaffold generation, demonstrate the strong potential of PepHAR in computational peptide binder design. Source code will be available at https://github.com/Ced3-han/PepHAR.

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.

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

Code

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

By repository: official repository: 16 samples from 1 repository, 11 ran (3 with no instrument failure; 8 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.

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ced3-han/pephar officialmentioned in paperpytorchMITSyntology: 16 samples, 11 ran (8 instrument-failed) · 5 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.

Code Syntology ran Syntology

16 samples harvested: 11 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 0 violated, 1 with no contract checked; 8 where Syntology's instrument failed) · 5 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.

2ran · honoured contract
6ran · our draft was wrong
2ran; the contract check could not run
1ran
5unverified

Licence: 2 of the 16 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 ced3-han/pephar. “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.

ced3-han/pephar official repository 16 samples, 11 ran (8 instrument-failed) · 5 unverified
GABlock models/density_model.py ran MIT (permissive) · 70ccfaae87f9fdb0 · report fixture: returned GABlock · level recorded 2026-09-22
angstrom_to_nm models/density_model.py ran · honoured contract fingerprinted MIT (permissive) · a85ad2ff0e007c7a · report fixture: signature x:float/0/float · returned float · level recorded 2026-09-22
construct_3d_basis models/density_model.py ran · our draft was wrong MIT (permissive) · c4d2cf69aa69331e · report fixture: signature center:Tensor/3/float, p1:Tensor/3/float, p2:Tensor/3/float · returned Tensor · level recorded 2026-09-22
global_to_local in 5 papers models/density_model.py ran · our draft was wrong fingerprinted MIT (permissive) · d8bc7f88e34943de · report fixture: signature R:Tensor/4/float, t:Tensor/3/float, q:Tensor/4/float · returned Tensor · level recorded 2026-09-22
masked_select datasets/my_select.py ran; the contract check could not run (RAISES) MIT (permissive) · b7a2e9d4dffa5e37 · report fixture: signature v:Tensor/2/float, mask:Tensor/1/bool · returned Tensor · level recorded 2026-09-25
nm_to_angstrom models/ga.py ran · honoured contract fingerprinted MIT (permissive) · 46d22cb265b2e628 · report fixture: signature x:float/0/float · returned float · level recorded 2026-09-25
normalize_vector in 17 papers
census: 6 implementations from 7 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/ga.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · d26ff18f89e81ea5 · report fixture: signature v:Tensor/2/float, dim:int/0/int, eps:float/0/float · returned Tensor · level recorded 2026-09-22
project_v2v models/density_model.py ran · our draft was wrong fingerprinted MIT (permissive) · e83f79b6a566bc97 · report fixture: signature v:Tensor/3/float, e:Tensor/3/float, dim:int/0/int · returned Tensor · level recorded 2026-09-22
register_dataset in 26 papers datasets/_base.py ran · our draft was wrong MIT (permissive) · 76294830633c3f09 · report fixture: signature name:str/0/str · returned function · level recorded 2026-09-25
register_model in 68 papers models/_base.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · be3d8f2945b52b90 · report fixture: signature name:str/0/str · returned function · level recorded 2026-09-22
select in 22 papers datasets/my_select.py ran; the contract check could not run (RAISES) MIT (permissive) · 8337784447c888a4 · report fixture: signature v:list/1/int, index:list/1/int · returned list · level recorded 2026-09-25
DensityModuleV4 models/density_model.py unverified MIT (permissive) · d48913d73f657848 · report
GAEncoder models/density_model.py unverified MIT (permissive) · 991ea9c0d0410c77 · report
_alpha_from_logits models/density_model.py unverified MIT (permissive) · a868e2a65de81bd2 · report
get_dataset in 285 papers datasets/_base.py unverified MIT (permissive) · 12a234a1ea67a141 · report
get_model in 368 papers models/_base.py unverified MIT (permissive) · be1d33da9ab60900 · 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. 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.

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

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

  1. DensityModuleV4 entry · level 0 · unverified · d48913d73f657848
  2. GAEncoder helper · level 0 · unverified · 991ea9c0d0410c77
  3. construct_3d_basis helper · level 1 · ran · our draft was wrong · c4d2cf69aa69331e
  4. register_model helper · level 1 · ran · our draft was wrong · be3d8f2945b52b90
  5. GABlock helper · level 1 · ran · 70ccfaae87f9fdb0
  6. angstrom_to_nm helper · level 1 · ran · honoured contract · a85ad2ff0e007c7a
  7. normalize_vector helper · level 1 · ran · our draft was wrong · d26ff18f89e81ea5
  8. project_v2v helper · level 1 · ran · our draft was wrong · e83f79b6a566bc97
  9. _alpha_from_logits helper · level 0 · unverified · a868e2a65de81bd2
  10. _heads helper · level 1 · ran · our draft was wrong · 682894cbcc498b53
  11. global_to_local helper · level 1 · ran · our draft was wrong · d8bc7f88e34943de
  12. local_to_global helper · level 1 · ran · our draft was wrong · 53bc6ef32589f773
  13. mask_zero helper · level 1 · ran · our draft was wrong · 270c91cf0250ca3b

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

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ADOPT

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