Pocket Representation

Pocket representation describes how a protein binding site is converted into model input. The pocket can be represented as residues, atoms, surfaces, grids, graphs, coordinates, or learned embeddings.

A distance-defined pocket around ligand coordinates can be:

where is a cutoff radius.

The pocket representation is then:

where are coordinates or features and is optional adjacency or contact structure.

Common Representations

RepresentationCapturesMain risk
residue sequence windowlocal sequence contextmisses 3D proximity and long-range contacts
residue graph/contact mapresidue-level geometrycutoff and missing residues change graph
atom-level graphlocal chemistry and coordinatesatom typing, protonation, and side-chain uncertainty
3D grid or voxelspatial density around pocketresolution, frame, and memory cost
surface patchshape and chemical surface featuressurface generation parameters affect features
learned embeddingcompact representation for retrieval or predictionhard to audit what information is preserved

Pocket Source Contract

SourceAvailable at deployment?Claim boundary
known binding siteyes, if site is annotatedtests site-conditioned modeling, not blind site discovery
predicted binding siteyes, if predictor is part of workflowincludes predictor error in the pipeline
ligand-defined pocketno for unknown bindersuseful for retrospective analysis, risky for blind prediction
residue cutoff from reference complexno for new pairscan leak the answer if used in evaluation
whole-protein inputyesshifts burden to model to find relevant region

If a pocket is defined from a bound test ligand, the task is no longer blind pocket discovery or deployment-like docking.

Key Risks

  • Pocket extraction can leak ligand information if defined from the test ligand.
  • Different cutoffs can change the apparent task.
  • Missing side chains, cofactors, metals, and waters may alter interactions.
  • Whole-protein context can matter even when the model only sees a local pocket.
  • Pocket similarity across train and test can hide target-family leakage.
  • Predicted pockets can fail silently if the benchmark only scores successful extractions.

Checks

  • Is the pocket known, predicted, transferred, or ligand-defined?
  • What atoms, residues, chains, waters, metals, and cofactors are included?
  • Does the representation preserve rotation/translation invariance or equivariance?
  • Is the pocket representation available at deployment time?
  • Is pocket similarity controlled across train and test?
  • Are failed pocket detections, empty pockets, and missing structures counted?
  • Does the evaluation separate pocket detection quality from downstream scoring quality?