Browse State-of-the-Art › Protein-Ligand Affinity Prediction
Protein-Ligand Affinity Prediction
4 papers with code · 2 benchmarks · 0 datasets archive 2025-07-28
Benchmarks archive 2025-07-28
2 leaderboard tables shown for this task, 2 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): PDBbind (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| PDBbind (7 rows) | BAPULM | BAPULM: Binding Affinity Prediction using Language Models | code | — | Compare |
| CSAR-HiQ (3 rows) | BAPULM | BAPULM: Binding Affinity Prediction using Language Models | code | — | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
No dataset record in the archive lists this task.
Subtasks archive 2025-07-28
1 subtask in the archive's task tree.
Papers archive 2025-07-28
archive papers tagged: 8 · with a code link: 4 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 8 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 8 of 8, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
6 Nov 2024 1 repository listedIdentifying drug-target interactions is essential for developing effective therapeutics.
-
8 Feb 2024 1 repository listedUnderstanding protein-ligand binding affinity is crucial for drug discovery, enabling the identification of promising drug candidates efficiently.
-
6 Jun 2022 1 repository listedOn small molecule dataset for predicting quantum chemical properties, PaxNet reduces the prediction error by 15% and uses 73% less memory than the best baseline.
-
21 Jul 2021 1 repository listedTo this end, we propose a structure-aware interactive graph neural network (SIGN) which consists of two components: polar-inspired graph attention layers (PGAL) and pairwise interactive pooling (PiPool).
-
Protein-ligand binding representation learning from fine-grained interactions9 Nov 2023 0 repositories listedThe binding between proteins and ligands plays a crucial role in the realm of drug discovery.
-
14 May 2022 0 repositories listedPrediction of protein-ligand (PL) binding affinity remains the key to drug discovery.
-
A Point Cloud-Based Deep Learning Strategy for Protein-Ligand Binding Affinity Prediction9 Jul 2021 0 repositories listedThere is great interest to develop artificial intelligence-based protein-ligand affinity models due to their immense applications in drug discovery.
-
ResAtom System: Protein and Ligand Affinity Prediction Model Based on Deep Learning17 Apr 2021 0 repositories listedMotivation: Protein-ligand affinity prediction is an important part of structure-based drug design.
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