Interpreting Sequencing Data — Interpret sequencing/variant call outputs conceptually (intro)

Historical Context & Motivation

For most of human history, DNA was invisible and mysterious. Scientists knew that traits were inherited from parents to children, but they had no way to read the actual code hidden inside cells. The breakthrough came when researchers figured out how to sequence DNA — that is, to determine the exact order of the chemical letters (A, T, C, and G) that make up our genetic instructions. Once scientists could read DNA, they needed tools and formats to organize, display, and interpret the massive amounts of data that sequencing produces.

Today, sequencing machines produce enormous files filled with letters and numbers. The central question this lesson addresses is: How do we read and make sense of sequencing and variant call outputs? Understanding these data formats is the first step toward using genetics to solve real-world problems in medicine, agriculture, and forensics.

Core Principles & Definitions

Before diving into data outputs, you need to understand a few foundational ideas. Sequencing data is built on a simple concept: your DNA is a long string of four chemical bases — adenine (A), thymine (T), cytosine (C), and guanine (G). A sequencing machine reads these bases and records them in order. But no machine reads the entire genome in one pass. Instead, the DNA is broken into short overlapping fragments called reads. Software then lines these reads up against a reference genome, like fitting puzzle pieces onto a picture on the box.

Visual Explanation — From Reads to Variants

The diagram below shows how raw sequencing reads are aligned to a reference genome. Notice that several reads overlap the same region. Where all the reads agree with the reference, the bases are shown in their normal color. Where one or more reads show a different letter, a variant is flagged.

In the diagram above, you can see the power of having multiple reads covering the same region. If only one read showed the T, it might just be a machine error. But because three out of five reads agree on the change, the software calls it a real variant with much higher confidence. This concept — requiring multiple reads to confirm a finding — is called read depth or coverage. More coverage means more confidence.

How Variant Calling Works — The Pipeline

Sequencing data doesn't arrive ready to interpret. It goes through a series of processing steps, often called a bioinformatics pipeline. Think of it like an assembly line in a factory — raw materials go in one end, and a finished product comes out the other. Each step cleans, organizes, or analyzes the data a little further.

The Four Main Steps

Step 1 — Sequencing & Raw Data: The machine reads millions of short DNA fragments and outputs them in a file format called FASTQ. Each entry in a FASTQ file contains the sequence of bases and a quality score for each base. The quality score is a number that tells you how confident the machine is about each letter it read.

Step 2 — Alignment: Software takes each read and finds where it best fits on the reference genome, like matching puzzle pieces. The output is saved in a BAM file (Binary Alignment Map), which stores each read's position and how well it matched.

Step 3 — Variant Calling: Another program scans through all the aligned reads, compares them to the reference, and identifies positions where the sample differs. The output is stored in a VCF file (Variant Call Format) — a structured table listing every detected variant.

Step 4 — Annotation & Interpretation: Each variant is annotated with information like which gene it falls in, whether it changes a protein, and whether it has been seen before in databases. This is the step where data becomes meaningful biological information.

Key File Formats — FASTQ, BAM, and VCF

Understanding sequencing data means knowing the three main file formats you'll encounter. Each format serves a different purpose in the pipeline. The diagram below shows a simplified view of what each file looks like and what information it contains.

Worked Example — Reading a VCF Entry

Let's walk through how to read a real variant call from a VCF file. Imagine you are a genetics researcher and you receive the following VCF entry for a patient. Your job is to figure out what it means.

Types of Variants & Their Significance

Not all variants are created equal. Some are harmless differences that make each person unique, while others can cause serious diseases. Understanding the different types of variants and their potential effects is essential for interpreting sequencing data in a meaningful way.

Impact Categories

Connection to Advanced Genomic Analysis

The basic interpretation skills you've learned in this lesson are the foundation for much more advanced analyses. As you progress in genetics, you'll encounter larger datasets, more complex variant types, and sophisticated tools for understanding what variants mean for human health and evolution.

One exciting frontier is pharmacogenomics — using a patient's sequencing data to choose the best medication and dose. Some variants in drug-processing genes mean that a standard dose could be too strong or too weak for certain patients. By reading VCF data, doctors can personalize treatment plans. Another growing area is prenatal screening, where sequencing tiny amounts of fetal DNA floating in a pregnant person's blood can reveal chromosomal conditions early in pregnancy.

Practice Problems

Lesson Summary