824df26b6320b692d629566c5a10b15004da82ce lrnassar Tue Sep 29 16:09:00 2026 -0700 addProteinSequence in mavemdLib translates each transcript's CDS from hg38.2bit so makeMaveMdVariants can check every projected codon against the reference residue its own HGVS term asserts; the existing comparison against MaveDB's genomic mapping only reaches the 3% of projected items that carry both terms, because 18 of the 40 protein accessions have no genomic-route variants at all. 39 of 40 accessions match at 0.000%; NP_689629.2 (FKRP) has 99 nonsense terms numbered one codon downstream of their own reference residue, which still reach mavemdVar through MaveDB's genomic mapping but are dropped from mavemdMap, which places columns from the protein term and has no fallback. The haplotype test now also reads hgvs_nt, since PTEN 00000054-a-1 states 1,236 haplotypes as c.[1207G>T;1209C>T] with no protein term and they were counted as rejected submissions, making both figures in the makeDoc wrong. assayLine runs the heatmap legend through asciiText because bedField turns the en dash in three MaveDB titles into – and the legend is drawn as raster text; clinGenId links to by_canonicalid rather than /allele, which serves JSON to a browser, matching human/civic.ra; the generated filter fragment no longer emits the blank line after each group that the makeDoc itself warns ends a stanza; and runBuild.sh tails the log on failure instead of dying silently under set -e. Also reworded the grey legend entry, which said no threshold was reached in either direction but covers 6,656 normal and 145 abnormal items, alphabetized the references, and fixed stale counts in the makeDoc. Caught by Claude review of 29af14b, fcf788d and 97c7de5. refs #38407 refs #37800 diff --git src/hg/makeDb/trackDb/human/hg38/mavemdVar.html src/hg/makeDb/trackDb/human/hg38/mavemdVar.html index 6ebb72a78c4..18818fe790d 100644 --- src/hg/makeDb/trackDb/human/hg38/mavemdVar.html +++ src/hg/makeDb/trackDb/human/hg38/mavemdVar.html @@ -1,29 +1,29 @@
This track is part of the MaveMD collection. It shows one item per measured variant per score set, so a variant measured in several experiments appears once for each of them.
Each item carries the assay score, the functional class that score falls into, and, where the score set has been calibrated against variants of known clinical significance, the ACMG/AMP functional evidence code that follows: PS3 for evidence of a damaging effect, BS3 for evidence of a normal one, at a strength set by the calibration's odds of pathogenicity following the -ClinGen recommendations for the PS3/BS3 criterion (Brnich et al.). ClinVar +ClinGen recommendations for the PS3/BS3 criterion (Brnich et al., 2019). ClinVar significance, gnomAD allele frequency and the ClinGen allele ID are attached where they exist.
Each item also carries the assay metadata: what the assay measured, in what model system, the molecular mechanism assessed, and how the variant library was built. That last field matters clinically. An assay built on an in vitro construct library introduces a synthetic copy of the target sequence, so it cannot detect an effect on splicing or on nonsense-mediated decay and can read falsely normal for such a variant. An assay that edits the endogenous locus can.
Two cautions when comparing variants. Many of the evidence codes come from calibrations MaveDB marks research use only; each item names its calibration and flags this. And the functional score has no common scale or direction between score sets, so a higher score does not always @@ -35,32 +35,32 @@
Items are colored by the ACMG functional evidence code from the calibration named in the item details. Red shades carry evidence toward pathogenic, blue toward benign, darkening with the strength of the evidence.
| PS3, very strong | |
| PS3, strong | |
| PS3, moderate plus | |
| PS3, moderate | |
| PS3, supporting | |
| - | Evidence not met: measured and calibrated, but the score reaches no threshold in - either direction | Calibrated, but no ACMG evidence code applies to this variant's functional + class |
| BS3, supporting | |
| BS3, moderate | |
| BS3, moderate plus | |
| BS3, strong | |
| BS3, very strong |
Score sets that classify their variants without assigning an ACMG code are a measurement rather than a clinical claim, and use a separate palette:
| Abnormal function measured, no ACMG evidence code assigned |