Environment settings and input data
Typically, the user wants to record here the sources and versions of the
reference genome sequence along with the corresponding annotations. In
the provided sample data set all data inputs are stored in a data
subdirectory and all results will be written to a separate results
directory,
while the systemPipeRNAseq.Rmd
script and the targets
file are expected to be located in the parent
directory. The R session is expected to run from this parent directory.
To run this sample report, mini sample FASTQ and reference genome files can be downloaded from here. The chosen data set SRP010938 contains 18 paired-end (PE) read sets from Arabidposis thaliana (Howard et al., 2013). To minimize processing time during testing, each FASTQ file has been subsetted to 90,000-100,000 randomly sampled PE reads that map to the first 100,000 nucleotides of each chromosome of the A. thalina genome. The corresponding reference genome sequence (FASTA) and its GFF annotion files (provided in the same download) have been truncated accordingly. This way the entire test sample data set is less than 200MB in storage space. A PE read set has been chosen for this test data set for flexibility, because it can be used for testing both types of analysis routines requiring either SE (single end) reads or PE reads.
The following loads one of the available NGS workflow templates (here RNA-Seq) into the user’s current working directory. At the moment, the package includes workflow templates for RNA-Seq, ChIP-Seq, VAR-Seq and Ribo-Seq. Templates for additional NGS applications will be provided in the future.
Download latest version of this tutorial
In case there is an updated version of this tutorial, download its systemPipeRNAseq.Rmd
source.
Now open the R markdown script systemPipeRNAseq.Rmd
in your R IDE (e.g. vim-r or RStudio) and
run the workflow as outlined below.
If you are on Windows please run the following command to move all input files into the right location. This problem will be fixed next week.
Required packages and resources
The systemPipeR
package needs to be loaded to perform the analysis steps shown in
this report (Girke , 2014).
In the workflow environments generated by genWorkenvir
all data
inputs are stored in a data/
directory and all analysis results will
be written to a separate results/
directory, while the
systemPipeRNAseq.Rmd
script and the targets
file are
expected to be located in the parent directory. The R session is expected to
run from this parent directory. Additional parameter files are stored under
param/
.
To work with real data, users want to organize their own data similarly and
substitute all test data for their own data. To rerun an established workflow
on new data, the initial targets
file along with the corresponding
FASTQ files are usually the only inputs the user needs to provide.
If applicable users can load custom functions not provided by
systemPipeR
. Skip this step if this is not the case.
Experiment definition provided by targets
file
The targets
file defines all FASTQ files and sample
comparisons of the analysis workflow.