Augmentation Policy

An augmentation policy defines how raw examples are transformed into alternative views during training. In self-supervised learning, the policy often defines the invariances a representation is expected to learn.

For an input , two views can be sampled as:

where and are stochastic transformations such as masking, cropping, noise injection, graph perturbation, sequence masking, or coordinate transforms.

Why It Matters

  • Augmentation defines what information should be preserved.
  • Strong augmentations can improve invariance but destroy label-relevant content.
  • Weak augmentations can make the pretext task too easy.
  • Domain-specific data needs domain-specific validity checks.

Examples

DomainCommon transformsMust preserve
Imagecrop, color jitter, blur, patch maskingclass or target object semantics
Text or sequencetoken masking, span masking, dropout, corruptionrecoverable linguistic or sequence context
Graphnode masking, edge dropping, subgraph samplinggraph identity or target-relevant relation
Moleculeconformer perturbation, atom masking, graph maskingchemical identity, valence, stereochemistry when relevant
3D structurerigid transform, coordinate noise, residue masking, distance/contact maskingtransformation contract and physical plausibility

Invariance Contract

An augmentation policy implicitly states an invariance:

This is only desirable if the downstream target is also invariant to . If changes under the transform, enforcing invariance can damage the representation.

TransformSafe whenRisky when
croptarget is still visiblecrop removes the causal object
token maskingcontext can infer missing tokentarget depends on exact token identity
edge droppinggraph label is robust to missing relationrelation is chemically or physically essential
rigid transformtarget is invariant to global poseoutput must rotate equivariantly
coordinate noiselabel tolerates small perturbationgeometry validity or chirality changes

For coordinate data, decide whether the desired behavior is invariance or equivariance:

The first is appropriate for scalar labels such as class or energy-like scores. The second is appropriate for coordinate outputs.

Checks

  • Does the transformation preserve the downstream label or target semantics?
  • Does it create unrealistic examples?
  • Does it leak the answer through a view construction rule?
  • Are positives still positive after augmentation?
  • Are false negatives likely because different examples share the same class, scaffold, family, or target?
  • Is the augmentation sampled independently across train, validation, and test in a way that does not leak identity?
  • Does the evaluation report performance under natural data, augmented data, or both?