Browse State-of-the-Art › Antibody-antigen binding prediction

Antibody-antigen binding prediction

9 papers with code · 4 benchmarks · 3 datasets archive 2025-07-28

Medical

Antibody-antigen binding prediction involves using computational or experimental methods to assess how well an antibody interacts with its target antigen. This can be done by analyzing features such as sequence, structure, and physicochemical properties. These predictions aid in designing therapeutic antibodies, vaccines, and diagnostic tests. Validation through experimental assays ensures the accuracy of the predictions and their applicability in biomedical research and development.

The binding site prediction task is used to predict which antibody residues interact with an antigen. A residue is considered part of the paratope’s binding site if any of its heavy atoms (non-hydrogen atoms) is located within 4.5˚A of any antigen-heavy atom.

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

4 leaderboard tables shown for this task, 4 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.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
MIPE (7 rows) ParaSurf ParaSurf: A Surface-Based Deep Learning Approach for... code — Compare
PECAN (5 rows) ParaSurf ParaSurf: A Surface-Based Deep Learning Approach for... code — Compare
Antibody sequences against Sars-Cov-2 and Omicron BA.1 (3 rows) XBCR-net (ACNN) Deep learning-based rapid generation of broadly reactive... code — Compare
Paragraph Expanded (2 rows) ParaSurf ParaSurf: A Surface-Based Deep Learning Approach for... 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

3 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 10 · with a code link: 9 · 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 10 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 10 of 10, 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.

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