Galaxy DNA-Seq Tutorial
From UABgrid Documentation
Galaxy DNA-Seq Tutorial
Linking to data
Link in the Mark Pritchard Vaccinia virus data set.
- Start with a blank history, there should be no numbered items on the right hand side of the pane. Otherwise create a new history.
- Select "Shared Data" from the top of the screen to bring up the Shared Data screen
- Select Data Library
- Select "Galaxy DNA-Seq Tutorial Vaccinia WR Files" from the alphabetically sorted list
- Click on the subfolder top box to select all 6 files
- Select "import to current history"
- Click on "Analyze Data" from the upper main menu. It should bring up the main page and your history pane should now look like the image below.
- Notice that with just 3 viruses are already over 4 GB of data!
Quality Control = Formatting and Grooming Data
- Your data is often NOT what you expect so it is worth running some quality control programs
- FastQ format can mean many things, see the wikipedia entry on FastQ format
- Ilumina FastQ format also not informative, it changes
- Click on the pencil to icon in one of the virus images to pull up the attributes, your screen should look a bit like this:
- In Galaxy the expected data type of the galaxy tool must match EXACTLY with the data type in your history pane, otherwise the option to use that particular piece of data will not appear in the tool's drop down menu for data selection.
- Some tools care more than others...
- Galaxy requires that everything go into Sanger format to be used. If you know your data is in sanger format, select fastqsanger for your data type. If it is not in that format, select fastq and run the FastQ Groomer.
- FastQ groomer is very useful, but slow
- Not a bad idea to run it if you are dealing with a new machine and have the time. Costly in terms of space.
- Ensure the correct reference genome is selected
- WARNING - seeing the reference genome doesn't mean it is there for using
- The current list of genomes available at UAB is here
- Contact the UAB Galaxy team or me if you need a genome added (similar procedure for Penn State)
- Used for a variety of tools, it can be overridden earlier
- Any problems with CMV-21950R_3_1.fastq ?
Assessing the quality of the data
We will use a number of different tools from the "NGS: QC and manipulation" drop down menu. Try processing the FastQ files with:
- Compute Quality Statistics
FastQC gives an attractive visual output and will flag potential problems.
- Select NGS: QC and manipulation -> FastQC
- Run it on all the fastq files
- Remember, you are on a cluster, this can be done in parallel
Take a look at the other areas that show up as quality issues.
- FastQC flags potential problems
- Are there any problems for us?
- It is imperative to understand your organism and its biology to interpret the data
Running Quality Statistics and Boxplot
- Galaxy has its own set of tools for computing quality statistics (using R)
- Generates raw statistics in tabular format which can then be used for a pretty box plot
- Select NGS: QC and manipulation -> Compute Quality Statistics for CMV-21950R_3_1.fastq
- Run it to compute the tabular file
- Why wait? Jobs can be queued, so go ahead and queue up a box and whiskers plot
- "NGS: QC and manipulation" -> Draw Quality Score Boxplot
- Can run it on "Data 13" (or whatever) even if Data 13 doesn't exist yet / isn't ready
Quality Statistics and Boxplot Results
- Should have a tabbed result file that is easy to manipulate in Galaxy
- Should get a nice box and whiskers plot
- Problems with this data? How does it compare to FastQ?
- About a quarter of the last base is of poor quality
- Trim off the 3' end
- There are other ways to clean up, reads can be filtered by other criteria
- What to keep and what to throw away depends on your requirements
- Take the trimmed data and run again compute quality statistics and draw the boxplot
- Results should look like above if everything was done correctly
- May want to rename your trimmed result file to something more useful like "Cmv21950r 3 1 trimmed" or something
Short read alignment to reference genome using BWA
- BWA will align all the short reads to our reference genome
- BWA is the algorithm of choice for DNA-Seq with Illumina data
- CASAVA 1.8 may do as well for SNPs, BWA does indels better
- Select NGS Mapping -> Map with BWA for Illumina
- Set the reference genome as Vaccinia Western Reserve, BWA doesn't pick this up
- Selected paired reads, make sure the first read (1) comes first
- Do this for all 3 genomes, each run will use 2 fastq files
- Essential toolset, performs a variety of functions
- Format conversion
- Viewing BAM files
- Generation of Pileup
- The output of many mapping programs (including BWA) is in SAM format and must in many cases be converted to the binary format (BAM) format for downstream analysis
- The conversion is lossless.
- As a binary file, it is significantly smaller than the SAM file
- Convert all 3 SAM files to BAM
- In this case we did not do any filtering on the SAM file prior to conversion to BAM
- Often when quality is desired, a filtering step will be done to remove reads which:
- Fail quality control
- Are optical duplicates
- Are not properly paired
Additionally a sorting step may be done, important if you are going to examine the BAM file in a browser like IGV
- See Shared Data -> Published Workflows -> "FastQ to High Quality, Filtered, Headered, Sorted BAM" or
- Click on this workflow
- Examines the flag integer in the BAM File
- Should have 3 BAM files
- Can think of the reads "piling up" on each other
- Each base pair location on the genome is assigned a representative base
- For each of the 3 BAM files, run NGS: SAM Tools -> Generate Pileup
Alternatives to Samtools for Variant Detection
- GATK - Emerging as the new best practice to call variants, not integrated into Galaxy just yet.
- PATRIC - Whole genome annnotation (once you have a sequence) for microbial genomes
- MAQ and others - not used too much anymore
SNPEff - Variation Summation
Summarizing variants and effects of SNPs.
- Reference genome must be in SNPEff, need GFF3 file of your genome annotation
- True for most genomes (even Vaccinia WR, now)
- SNPEff looks at heterozygous and homozygous SNPs, MNPs, lots coverage, indel sizes, etc..
- Select SNP:Effect -> SNPEff near the bottom of the tool menu
- Run on any pileup file
Results from SNPEff
- Only as good as your genome annotation file
- Introns in viruses?!
- Too many results, pileup file needs to be filtered
Finding the Relevant SNPs versus Control
Too many SNPs! We need to make some decisions as to what to include and exclude. This is an active area of research, answer depends on:
- Overall coverage
- Number of reads
- Mapping quality
- Base quality
- Previous knowledge
For the tutorial here, I selected a quality cutoff of 20 and a minimum coverage of 100 reads.
- Filter all 3 pileups
Difference from consensus
Now take only changes which result in a change from the consensus.
To review, the VAC-WR strain is the progenitor (parent) of the other two strains. It does not have a phenotype of interest. Thus we are only interested in genomic differences between our two mutants strains and the parent strain. Differences between the reference NCBI strain are not of interest if they also appear in the parent strain.
- Since our data is in tabular format we can run Join, Subtract and Group -> Compare Two Datasets
- Parameters are below
- I assume changes at the same site are identical between parent and child
- Dump into Excel
- Includes whether mutation is non-synomous, gene identifier, etc..
De novo assembly
- Not covered here
- Velvet on Galaxy, but not functioning properly (yet)
Viewing results in IGV
- Not covered, but worth doing
- Problems can be discovered, good reality check