← Về thư mục
📄 / / profiles / r-and-d / raw_evidence / scientific-agent-skills / skills / alphagenome / references / interpretation.md

Interpreting AlphaGenome and Atlas scores

Distilled from the AlphaGenome and Atlas papers, the official FAQ, and the interpretation guide DeepMind ships with its own AlphaGenome agent skill. Everything here is a rule for writing up a prediction, not a claim about biology.

The frame

AlphaGenome predicts what a genomics assay would read out from a DNA sequence. An Atlas or model score is therefore a predicted molecular effect in a biosample the model was trained on, nothing more:

Raw score and quantile: always both

Quantity What it is Use it for
raw_score effect size on the scorer's own scale (RNA_SEQ: log2 fold change; center-mask scorers: log2 ratio of summed signal; splicing: change in probability or usage) magnitude, direction, comparing tissues within one scorer
quantile_score rank against common variants (gnomAD v3 MAF > 0.01), signed, saturates near +/-0.99999 unusualness; comparing across scorers
AVI avi_raw composite model output ranking within a set
AVI Phred -10 log10(1 - cdf); 10 / 20 / 30 = top 10 % / 1 % / 0.1 % of all SNVs genome-wide rank, thresholds

Rules of thumb for raw_score, derived mainly from RNA-seq and to be checked against the plotted tracks:

|raw| Reading
< 0.1 no meaningful effect, whatever the quantile says
0.1 to 0.5 weak; report as a possible subtle change
0.5 to 1.0 moderate (about 1.4x to 2x for RNA-seq)
> 1.0 strong (more than 2x for RNA-seq); -4 is a 16-fold reduction

Raw scores are not percentages. Quote them with the scorer name and track.

The common trap: high quantile, tiny raw score. In low-expression genes and quiet regions the background distribution is so narrow that a raw change of 0.05 ranks above 0.99. Report "no significant predicted effect" and name the artefact. Conversely a raw -1.5 with quantile 0.9 in a highly variable track is still a large predicted effect worth mentioning.

Unsigned scorers (POLYADENYLATION, SPLICE_*, CONTACT_MAPS, all *_ACTIVE) have no direction; *_ACTIVE scores are the activity of the stronger allele and cannot be read as a difference at all.

AVI thresholds

The report recommends ranking over hard cut-offs and thresholds that are "genomic region- or application-aware": pathogenic regulatory variants sit in lower AVI bins than pathogenic protein-truncating or splice-motif variants, so a single genome-wide Phred cut-off systematically under-calls regulatory hits. Practical pattern:

  1. Rank the candidate set by Phred and report the ranks.
  2. State the top-percentile the Phred implies (Phred 20 = top 1 % of SNVs).
  3. Read the feature attribution. MERGED_SPLICING or ALPHAMISSENSE dominant means a coding or splice mechanism; MAX_ABS_DNASE / MAX_ABS_CHIP_TF / MAX_ABS_RNA_SEQ mean a regulatory mechanism you can drill into by track; CACTUS_241_WAY / PHASTCONS_470_WAY dominant means conservation is carrying the score and the molecular mechanism is not resolved by AVI.
  4. Only then drill into the per-track scores for the matched tissue.

Tissue matching

Negative results

Most variants are benign and the model will say so. "AlphaGenome predicts no molecular effect in the 305 DNase and 371 RNA-seq tracks" is a complete, valuable answer. Do not invent a cryptic splice site or an enhancer disruption that the tracks do not show; do not infer disruption from location in a peak when REF and ALT tracks are identical.

What the model cannot see

Coordinate hygiene before any lookup

  1. Assembly must be GRCh38 for the Atlas (hg38 for the human model, mm10 for mouse). Lift over GRCh37 sources first and re-check REF.
  2. REF must equal the reference base; the Atlas key ignores REF, so a swapped allele silently returns the wrong record.
  3. Variants are 1-based, genome.Interval is 0-based half-open. Converting a 1-based closed chr:start-end means start - 1, end.
  4. Left-normalise indels before scoring with the model.
  5. Keep the chr prefix (chrM for the mitochondrion).

The genomic-coordinates skill covers all of this with scripts.

Reporting checklist