Promethease costs about $12 and turns a consumer genotype file into a searchable report of SNPedia annotations. It is worth that price as a literature index, and it is not worth treating as a health assessment. Here is what it does, where it breaks, and what we would run instead.
pLI is the probability that a gene is intolerant to heterozygous loss of function, estimated from how many truncating variants are missing from a large population sample. This page covers how it is computed, where the files live, and the cases where the score misleads you.
A working guide to gs://gcp-public-data--gnomad/release/4.1/ht/genomes/gnomad.genomes.v4.1.sites.ht: what is in the table, how to read only the parts you need, how to decode the frequency arrays, and how to annotate your own variants without burning a week of compute.
A working guide to loading a personal whole-genome VCF and RNA-seq quantifications into R, annotating them with Bioconductor, and querying both layers together without exhausting memory.
A practical guide to analyzing 23andMe, AncestryDNA, and whole-genome files yourself, with the tools and commands we would use, and the failure modes that make free consumer reports unreliable.
A practical guide to running ANNOVAR on a personal whole-genome VCF: which databases to download, the exact table_annovar.pl command, how to normalize input, and how transcript choice changes the answer.
A working pipeline for taking raw whole-genome sequencing output (FASTQ, CRAM, VCF) through quality control, annotation, and variant triage, with the specific tools, flags, and thresholds we would use and the failure modes to watch for.
A practical walkthrough of what a sequencing lab hands you, how to verify it before you trust it, and how to go from raw reads to an annotated variant table you can query yourself.
A working guide to going from raw sequencing reads to an annotated, filtered variant list you can reason about: file formats, strand conventions, QC thresholds, annotation commands, and the failure modes that produce confident nonsense.
A genome explorer is a coordinate browser plus a query layer over your own alignments and variant calls. Here is the stack we would use on a personal 30x whole genome, with the commands, file formats, and failure modes.
A working pipeline for analyzing your own DNA with open source tools, from array raw data to whole-genome FASTQ, including the annotation databases, the commands, and the failure modes that produce wrong answers.
How to use R and Bioconductor as the annotation, statistics, and integration layer for a personal molecular dataset: VCFs, RNA-seq counts, proteomics, and continuous glucose data, with the parts you should not do in R.