Robustness

Robustness measures whether model behavior remains acceptable under perturbations, noise, missing inputs, distribution shifts, or implementation changes.

A robustness check compares performance under a perturbation family :

The robustness gap is:

Perturbation Types

  • Input noise, crop, masking, corruption, or missing modality.
  • Tokenization or formatting changes.
  • Molecule standardization or conformer variation.
  • Protein sequence homolog or structure-quality changes.
  • Hardware, precision, batching, or decoding changes during inference.

Robustness Contract

FieldQuestionExample
Perturbation familyWhat changes between clean and perturbed input?corruption, masking, conformer, sequence mutation
Label preservationShould the correct label stay the same?scaffold-preserving analog vs activity cliff
SeverityHow large is the perturbation?noise level, mutation count, RMSD range
SliceWhere is robustness measured?class, scaffold, family, source, modality
MetricWhat behavior is allowed to degrade?accuracy, calibration, ranking, geometry validity
Failure policyWhat counts as invalid output?NaN, failed generation, impossible pose, abstention

Robustness is only meaningful when the perturbation is plausible and the expected label behavior is specified.

Relative Robustness

Report the clean score and perturbed score together:

or as a ratio when the metric scale makes that clearer:

For loss-like quantities, reverse the sign or report the gap explicitly. Do not mix “higher is better” and “lower is better” metrics without stating direction.

Computational Biology Examples

AreaPerturbationLabel-Preservation Caveat
Molecule propertytautomer, protonation, salt, stereochemistry, conformerchemical state may change the label
Dockingreceptor preparation, side-chain state, box size, conformer seedpose and score may legitimately change
Protein modelinghomolog removal, mutation, structure resolution, predicted structure inputmutation can alter function or stability
Virtual screeningdecoy construction, library subset, failed docking treatmentactive prevalence changes enrichment
Genome sequencereverse complement, mutation, window shiftstrand and context may change interpretation

Paper Claim Template

Use this shape when writing a paper note:

The model is robust to {perturbation} at {severity} on {slice} under {metric}, with {uncertainty}. The perturbation is label-preserving because {reason}. Failure cases are {failure_modes}.

Checks

  • What perturbation is realistic for deployment?
  • Does the perturbation preserve the correct label?
  • Is robustness measured per subgroup, scaffold, family, source, or modality?
  • Does the model fail gracefully or produce confident invalid outputs?
  • Are robustness checks separated from training-time augmentation?
  • Are failed preprocessing, failed inference, and invalid generations counted?
  • Is the robustness comparison paired on the same examples?