SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2111.07786 · 2021

Independent SE(3)-Equivariant Models for End-to-End Rigid Protein Docking

arXiv · PDF · Open in the Atlas

Code that ran

3 of 3 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 3 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2111.07786.json · badge: /api/ran/2111.07786.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
octavian-ganea/equidock_public canonical (classifier label)
classifier basis: classifier_2025
3 ran · 0 no recorded run
FunctionStatusWhere it lives
G_fn Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
octavian-ganea/equidock_public/src/inference_rigid.py
code served (permissive licence) · get_code("3af636c75c65ce49")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 1, dtype family float, shape (2,) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# Analyze the function:
# - protein_coords: viewed as (1, -1, 3), so shape should be (N, 3) where N is number of atoms
# - x: viewed as (-1, 1, 3), so shape should be (M, 3) where M is batch size
# - sigma: a scalar float value
# The function computes distances between protein coordinates and batch points

# Create small tensors with distinct sizes
protein_coords = torch.randn(4, 3)  # 4 atoms, 3 coordinates each
x = torch.randn(2, 3)  # batch of 2 points, 3 coordinates each
sigma = 1.0  # scalar

ARGS = {
    "protein_coords": protein_coords,
    "x": x,
    "sigma": sigma,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 1, dtype family float, shape (2,) — shape (2,) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
compute_body_intersection_loss Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
octavian-ganea/equidock_public/src/inference_rigid.py
code served (permissive licence) · get_code("3b41ee1a4cc7e9b1")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# Create small tensors for ligand coordinates (deformed)
# Shape should be (N, 3) where N is number of ligand atoms
model_ligand_coors_deform = torch.randn(2, 3, dtype=torch.float32)

# Create small tensors for bound receptor representation nodes locations
# Shape should be (M, 3) where M is number of receptor nodes
bound_receptor_repres_nodes_loc_array = torch.randn(4, 3, dtype=torch.float32)

# Hyperparameters
sigma = 25.0
surface_ct = 10.0

ARGS = {
    "model_ligand_coors_deform": model_ligand_coors_deform,
    "bound_receptor_repres_nodes_loc_array": bound_receptor_repres_nodes_loc_array,
    "sigma": sigma,
    "surface_ct": surface_ct,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 0, dtype family float, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
get_rot_mat Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
octavian-ganea/equidock_public/src/inference_rigid.py
code served (permissive licence) · get_code("64ef8c256996fa77")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (3, 3) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# The function expects euler_angles to be indexable with [0], [1], [2]
# It should contain three scalar values (roll, yaw, pitch)
# These are used with torch.cos and torch.sin, so they should be tensors or floats
euler_angles = torch.tensor([0.1, 0.2, 0.3])

ARGS = {
    "euler_angles": euler_angles
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (3, 3) — shape (3, 3) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 3 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 3 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
G_fn 2 other papers
2 later
2402.18813 (2024-02)
Protein Multimer Structure Prediction via Prompt Learning
2403.07902 (2024-03)
DECOMPDIFF: Diffusion Models with Decomposed Priors for Structure-Based Drug Design
compute_body_intersection_loss 1 other paper
1 later
2402.18813 (2024-02)
Protein Multimer Structure Prediction via Prompt Learning
get_rot_mat 1 other paper
1 later
2402.18813 (2024-02)
Protein Multimer Structure Prediction via Prompt Learning

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Protein complex formation is a central problem in biology, being involved in most of the cell's processes, and essential for applications, e.g. drug design or protein engineering. We tackle rigid body protein-protein docking, i.e., computationally predicting the 3D structure of a protein-protein complex from the individual unbound structures, assuming no conformational change within the proteins happens during binding. We design a novel pairwise-independent SE(3)-equivariant graph matching network to predict the rotation and translation to place one of the proteins at the right docked position relative to the second protein. We mathematically guarantee a basic principle: the predicted complex is always identical regardless of the initial locations and orientations of the two structures. Our model, named EquiDock, approximates the binding pockets and predicts the docking poses using keypoint matching and alignment, achieved through optimal transport and a differentiable Kabsch algorithm. Empirically, we achieve significant running time improvements and often outperform existing docking software despite not relying on heavy candidate sampling, structure refinement, or templates.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2111.07786")
get_code_for_paper("2111.07786")
have("2111.07786")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2111.07786.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2111.07786.svg)](https://syntology.ai/paper/2111.07786)

Connect an agent — have() is free.