Self-Supervised Learning

Self-supervised learning trains representations from structure in the data instead of direct human labels. The target can be masked tokens, corrupted views, contrastive pairs, future states, or reconstruction objectives.

The common pattern is to create a training signal from the input:

Here is the visible or augmented view and constructs a target from the same raw example.

More explicitly, many SSL methods sample one or more views:

where is an augmentation policy. The method then defines which information should match between views and which information can be ignored.

Objective Families

FamilyTargetMain Risk
Masked predictionhidden token, pixel, node, residue, atom, or featuretarget may be too local or too easy
Contrastive learningpositive identity among negativesfalse negatives and augmentation semantics
Joint-embedding predictiontarget representationcollapse prevention and target abstraction
Autoregressive predictionfuture or next token/stateteacher-forcing mismatch and context leakage
Reconstruction or denoisingclean input from corrupted inputreconstructing nuisance detail instead of useful abstraction

Canonical paper examples:

RoutePaper
teacher-student self-distillationDINO
masked image reconstructionMAE

Pretraining Data Boundary

SSL is often limited by data construction rather than architecture. Record:

where is augmentation or corruption metadata, is source, and is time or split group when relevant. If test-like examples or near-duplicates appear in pretraining, downstream evaluation can overstate generalization.

Why It Matters

  • Useful when labels are sparse or expensive.
  • Can pretrain sequence, graph, molecular, and protein representations.
  • Often shifts the main question from architecture to data construction and evaluation.
  • Makes data curation and leakage control part of the learning method, not only preprocessing.

Evaluation

SSL is usually evaluated indirectly through downstream performance:

Common evaluation modes are linear probing, full fine-tuning, retrieval, clustering quality, and task-specific metrics. These belong to representation evaluation, not to the pretraining objective itself.

Evaluation Budget

Different evaluation protocols answer different questions:

ProtocolTestsCaveat
frozen linear probelinear separability of frozen representationweak evaluator may understate useful representation
kNN or retrievalneighborhood structurecorpus and metric define the claim
full fine-tuningadaptation performancemixes pretraining quality with optimization budget
low-data fine-tuningsample efficiencyneeds matched search budget and seeds
OOD or grouped splittransfer beyond pretraining distributionsplit must match the biological or deployment claim

Checks

  • Is the pretext task aligned with the downstream task?
  • Can train and test data leak through near-duplicates, scaffolds, protein families, or temporal splits?
  • Does the representation transfer beyond the pretraining distribution?
  • Does the objective avoid representation collapse?
  • Are augmentation and masking choices valid for the domain?
  • Are linear probe, fine-tuning, and retrieval protocols kept separate?
  • Are pretraining and evaluation splits deduplicated at the right entity level?
  • Is the adaptation budget fixed before comparing representations?