Structure

A structure is a spatial arrangement of atoms, residues, or coarse-grained sites with coordinates and geometry.

A structure can be written as typed coordinates:

where is atom, residue, or site identity and is its coordinate.

Why It Matters

  • Structure carries the geometric information needed for docking, folding, and interaction modeling.
  • Equivariance helps models treat rotated or translated structures consistently.
  • Structural representations must distinguish coordinates, frames, distances, and chemical identity.
  • A structure can be represented as coordinates, distances, contact maps, residue graphs, surfaces, grids, or local frames.

Structure Contract

FieldQuestionExample
Unitatom, residue, chain, pocket, complex, surface, grid?protein backbone, ligand atoms
Sourceexperimental, predicted, template-derived, docked, generated?X-ray, cryo-EM, predicted structure
Coordinate frameglobal, receptor-aligned, ligand-centered, local residue frame?arbitrary PDB frame
Resolutionall atom, backbone, C-alpha, coarse-grained, surface points? trace
Chemical stateprotonation, tautomer, charge, waters, cofactors, metals?prepared receptor
Missing dataunresolved residues, missing atoms, alternate locations?loop gaps, side-chain completion
Allowed informationwhat was available at inference time?no test ligand pose

For coordinate matrices:

the model should state whether atom/residue order is meaningful, arbitrary, or tied to a public indexing scheme.

Symmetry Boundary

Rigid motions should not change scalar labels:

Coordinate outputs should transform with the input:

If a paper uses absolute coordinates without explaining the frame, the structure claim is incomplete.

Source and Evidence

Structure SourceClaim StrengthRisk
experimental structurestrongest for measured geometryresolution, missing atoms, construct differences
predicted structureuseful input or hypothesismodel bias and circular evidence
template-derived structureprior from homologtemplate leakage
docked structuregenerated posescoring and pose quality must be separated
generated structuremodel outputvalidity and physical plausibility required

Structure source should be recorded before comparing metrics.

Evaluation Boundary

ClaimMetric or Check
coordinate accuracyRMSD, aligned error, distance error
contact predictionprecision/recall over contact map
pose qualitypose RMSD, clash, interaction recovery
geometry validitybond lengths, angles, chirality, sterics
functional relevanceassay, binding, or downstream task evidence

Checks

  • What coordinate frame, atom subset, and resolution are used?
  • Are missing atoms, alternate conformations, and flexible regions handled?
  • Does the model use distances only, coordinates, local frames, or full equivariant features?
  • Is the output invariant, equivariant, or a mixture of scalar and coordinate predictions?
  • Is the structure experimental, predicted, relaxed, docked, or generated?
  • Does preprocessing leak a reference ligand, template, or future evaluation context?
  • Are atom/residue mappings and alignment policies specified for coordinate metrics?
  • Are invalid or incomplete structures counted rather than silently removed?