Variant Effect Prediction

Variant effect prediction estimates how a sequence variant changes a biological or functional target. In this wiki, it is treated as a genome-level sequence modeling task, not as a clinical interpretation workflow.

A variant can be represented as:

where is the genomic position or region, is the reference allele, and is the alternate allele.

A model often compares reference and alternate sequence contexts:

The prediction target must say what “effect” means:

Without that context, a variant effect score is only a generic ranking signal.

Task Contract

FieldQuestion
Variant unitSNV, insertion/deletion, haplotype, edited region, or window
Reference contextassembly, strand, window length, flanking sequence
Alternate contexthow the alternate sequence is constructed
Target observableannotation, assay readout, expression proxy, constraint score, or benchmark label
Label sourcemeasured, curated, simulated, predicted, or derived
Split unitregion, locus, chromosome, source, variant family, or species
Metricclassification, regression, ranking, calibration, or retrieval metric

Reference and Alternate Windows

For a fixed window operator , a common construction is:

where is the reference genome and is the region around the variant. The edit operation should be deterministic and documented.

ChoiceRisk
window lengthtoo short loses regulatory or protein-context information
strand handlingreverse-complement mismatch
indel handlingcoordinate shift and alignment ambiguity
multiple variantssingle-variant assumption breaks
assembly versionref/alt sequence mismatch

Label Types

Label TypeMeaningCaution
functional assay readoutmeasured change in a defined experimentassay/source-specific
computational annotationlabel produced by another model or ruleteacher leakage and circular evidence
conservation or constraint proxyevolutionary signalnot the same as experimental function
public benchmark labeltask-specific evaluation labelbenchmark scope may be narrow
clinical categoryinterpretation labelout of scope here unless explicitly public and non-sensitive

Evaluation Boundary

Variant effect prediction can be evaluated as classification, regression, ranking, or prioritization. The metric should match the output claim.

ClaimEvidence Needed
variant classificationlabel semantics, threshold, calibration or confusion matrix
effect-size regressionunit, transform, uncertainty, error scale
prioritizationranked-list metric and candidate set definition
cross-region generalizationregion/locus split and overlap checks
cross-source robustnesssource-held-out or annotation-version-held-out evaluation

For a score difference , calibration is not automatic. A larger score may rank variants without being a well-calibrated probability or measured effect size.

Leakage Risks

RiskCheck
nearby variants in train and testgroup by region or locus
overlapping windowssplit before window extraction
same source evidence in labelsrecord source and version
annotation-derived labels used as featuresseparate input features from targets
homologous or duplicated regionsgroup duplicated sequence contexts
post-hoc threshold tuningtune threshold on validation only

Checks

  • What target does “effect” mean?
  • Are reference and alternate contexts generated from the same assembly?
  • Are variants near each other split carefully to avoid regional leakage?
  • Are labels measured, curated, simulated, or inferred?
  • Is the model evaluated on held-out regions, variant types, or sources?
  • Is the task classification, regression, ranking, or prioritization?
  • Does the metric match the claim rather than only the model output format?
  • Are threshold choices, candidate sets, and failed variants included in the protocol?
  • Is the note staying within sequence/region/variant modeling rather than clinical interpretation?