0c1e751423b38dd741875d4cdcc6ffb5d4c4a135 max Tue May 12 07:51:34 2026 -0700 mei: add DeepMEI 1000G subtrack on hg38 91,617 MEIs (68,282 Alu, 16,891 L1, 6,444 SVA) called by DeepMEI on the 3,202 high-coverage 1000 Genomes samples. Same 1-bp anchor convention and Okabe-Ito colors as meiHgsvc3. DeepMEI's symbolic ALT carries no inserted sequence or insertion length, so the bigBed schema is a subset of meiHgsvc3 (no svLen, callerCount, validation flags, insertSeq). Also fixes the INS-svLen:carrierCount label format note in meiHgsvc3.html. refs #37524 diff --git src/hg/makeDb/trackDb/human/meiHgsvc3.html src/hg/makeDb/trackDb/human/meiHgsvc3.html index 4be1fd837ac..36341cbb9db 100644 --- src/hg/makeDb/trackDb/human/meiHgsvc3.html +++ src/hg/makeDb/trackDb/human/meiHgsvc3.html @@ -31,31 +31,31 @@ L1ME-AID and PALMER validation flags, overlap with reference segmental duplications and tandem repeats, and the full DNA sequence of the inserted mobile element (the ALT allele minus the anchor base).

Display Conventions and Configuration

An insertion has zero length on the reference: it attaches between two adjacent reference bases without replacing any of them. Following the VCF convention used by the underlying PAV calls and by the other long-read SV tracks, each MEI is drawn as a 1-bp block sitting on the anchor base — the reference base immediately to the left of the insertion attachment point. The inserted mobile element itself is not present in the reference and is therefore not drawn; its length is reported on the detail page (svLen) and in the item label -(INS-svLen-carrierCount). bigBed does support truly zero-width +(INS-svLen:carrierCount). bigBed does support truly zero-width features between nucleotides, but for consistency with the long-read SV tracks, this track uses the 1-bp anchor representation instead.

Items are colored by element class: