95d62eaffe46026207539ae1d1e815c1c83779ff lrnassar Fri Mar 14 17:24:32 2025 -0700 Fixing the revel values, I accidentally makde the wrong boundaries in my first pass, refs #35352 diff --git src/hg/makeDb/trackDb/human/revel.html src/hg/makeDb/trackDb/human/revel.html index ee6f315af22..095ab2f787b 100644 --- src/hg/makeDb/trackDb/human/revel.html +++ src/hg/makeDb/trackDb/human/revel.html @@ -84,39 +84,39 @@
Track colors
This track is colored according to Table 2 in Vikas et al. The colors represent the recommended ACMG/AMP score cutoffs.
Range | Classification | |
---|---|---|
≥ .773 | +≥ .644 | Pathogenic |
.772 - .184 | +.643 - .291 | Neutral |
≤ .183 | +≤ .290 | Benign |
For hg38, note that the data was converted from the hg19 data using the UCSC liftOver program, by the REVEL authors. This can lead to missing values or duplicated values. When a hg38 position is annotated with two scores due to the lifting, the authors removed all the scores for this position. They did the same when the reference allele has changed from hg19 to hg38. Also, on hg38, the track has the "lifted" icon to indicate this. You can double-check if a nucleotide position is possibly affected by the lifting procedure by activating the track "Hg19 Mapping" under "Mapping and Sequencing".