Data management
26 March 2021
Package
ORFik 1.10.13
Contents
1 Introduction
Welcome to the introduction of data management with ORFik experiment. This vignette will walk you through how to work with large amounts of sequencing data effectively in ORFik.
ORFik is an R package containing various functions for analysis of RiboSeq, RNASeq and CageSeq data, we advice you to read ORFikOverview vignette, before starting this one.
1.1 Motivation
NGS libraries are becoming more and more numerous. As a bioinformatician you often need to use many data-sets, like RNA-seq or ribo-seq together, to make some plots or statistics. A lot of things can go wrong when you scale up from just 1 data-set to many.
Another problem is also that annotations like gff and fasta files combined with the NGS data, must be separately loaded. Making it possible to use wrong annotation for the NGS data, or wrong chromosome naming as chr1 vs 1 etc.
1.2 What is an ORFik experiment?
It is an object to massively simplify / error correcting your code, by having a table of all libraries and annotation of an experiment. That contains filepaths and info for each library / annotation files in the experiment. It also tries to guess grouping / types / pairs (paired end bam files etc.) by the file names. It is also a safety in that it verifies your experiments contain no duplicate files, or empty or non-accessible files. Making it almost impossible to load the wrong data. In addition it checks chromosome naming of libraries and annotation, making sure you are not mixing chr1 vs 1 as name for chromosome 1 etc.
The main reason to represent your NGS data as an ORFik experiment will now be shown.
1.3 Example of creating an ORFik experiment
First load ORFik
library(ORFik)Let’s say we have a human experiment, containing annotation files (.gtf and .fasta genome) + Next generation sequencing libraries (NGS-data); RNA-seq, ribo-seq and CAGE.
# Read from (create.experiment() template)
# 1. Pick directory (normally a folder with bam / bed / wig files)
dir <- system.file("extdata", "", package = "ORFik")
list.files(dir)## [1] "QC_STATS" "annotations.gtf" "cage-seq-heart.bed.bgz"
## [4] "features.rdata" "genome.fasta" "genome.fasta.fai"
## [7] "pshifted" "ribo-seq-heart.bed.bgz" "ribo-seq.bam"
## [10] "ribo-seq.bam.bai" "rna-seq-heart.bed.bgz"# 2. Pick an experiment name
exper <- "ORFik"
# 3. Pick .gff/.gtf and fasta location
txdb <- system.file("extdata", "annotations.gtf", package = "ORFik")
fasta <- system.file("extdata", "genome.fasta", package = "ORFik")
template <- create.experiment(dir = dir, # dir is the NGS files
exper, # Experiment name
txdb = txdb, # gtf / gff / gff.db annotation
fa = fasta, # Fasta genome
organism = "Homo sapiens", # Scientific naming
saveDir = NULL, # If not NULL, saves experiment directly
viewTemplate = FALSE)
data.frame(template)## X1 X2 X3
## 1 name ORFik
## 2 gff /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/annotations.gtf
## 3 fasta /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/genome.fasta
## 4 libtype stage rep
## 5 CAGE heart
## 6 RFP heart
## 7 RFP
## 8 RNA heart
## X4 X5
## 1
## 2 organism
## 3
## 4 condition fraction
## 5
## 6
## 7
## 8
## X6
## 1
## 2 Homo sapiens
## 3
## 4 filepath
## 5 /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/cage-seq-heart.bed.bgz
## 6 /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/ribo-seq-heart.bed.bgz
## 7 /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/ribo-seq.bam
## 8 /tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/rna-seq-heart.bed.bgzYou see from the template, it excludes files with .bai or .fai, .rdata etc, and only using data of NGS libraries, defined by argument (type).
You can also see it tries to guess library types, stages, replicates, condition etc. It will also try to auto-detect paired end bam files. To fix the things it did not find, you either save the file and modify in Excel / Libre office, or do it directly in R.
Let’s update the template to have correct tissue-fraction in one of the samples.
template$X5[6] <- "heart_valve" # <- fix non unique row (tissue fraction is heart valve)
# read experiment from template
df <- read.experiment(template)To save it, do:
save.experiment(df, file = "path/to/save/experiment.csv")You can then load the experiment whenever you need it.
2 The experiment object
To see the object, just show it like this:
df## experiment: ORFik with 3 library types and 4 runs
## libtype stage fraction
## 1: CAGE heart
## 2: RFP heart heart_valve
## 3: RFP
## 4: RNA heartYou see here that file paths are hidden, you can acces them like this:
If you have varying version of libraries, like p-shifted, bam, simplified wig files, you can get filepaths to different version with this function.
filepath(df, type = "default")## [1] "/tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/cage-seq-heart.bed.bgz"
## [2] "/tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/ribo-seq-heart.bed.bgz"
## [3] "/tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/ribo-seq.bam"
## [4] "/tmp/RtmpBSShP4/Rinst87a6a78df44/ORFik/extdata/rna-seq-heart.bed.bgz"2.1 Loading all data in experiment
# First load experiment if not present
# We use our already loaded experiment: (df) here
# Load transcript annotation
txdb <- loadTxdb(df) # transcript annotation## Import genomic features from the file as a GRanges object ... OK
## Prepare the 'metadata' data frame ... OK
## Make the TxDb object ... OK# And now NGS data
outputLibs(df, chrStyle = seqlevelsStyle(txdb)) # Use txdb as seqlevelsStyle reference## Outputting libraries from: ORFikBy default all libraries are loaded into .GlobalEnv (global environment) with names decided by columns in experiment, to see what the names will be, do:
bamVarName(df) #This will be the names:## [1] "CAGE_heart" "RFP_heart_fheart_valve" "RFP"
## [4] "RNA_heart"If you have multiple experiments, it might be a chance of non-unique naming, 2 experiments might have a library called cage. To be sure names are unique, add the experiment in the variable name:
df@expInVarName <- TRUE
bamVarName(df) #This will be the names:## [1] "ORFik_CAGE_heart" "ORFik_RFP_heart_fheart_valve"
## [3] "ORFik_RFP" "ORFik_RNA_heart"You see here that the experiment name, “ORFik” is in the variable name If you are only working on one experiment, you do not need to include the name, since there is no possibility of duplicate naming (the experiment class validates all names are unique).
Since we want NGS data names without “ORFik”, let’s remove the loaded libraries and load them again.
df@expInVarName <- FALSE
remove.experiments(df)## Removed loaded libraries from experiment:ORFikoutputLibs(df, chrStyle = seqlevelsStyle(txdb)) ## Outputting libraries from: ORFik2.2 Loading transcript regions
Let’s say we want to load all leaders, cds and 3’ UTRs that are longer than 30. With ORFik experiment this is easy:
txNames <- filterTranscripts(txdb, minFiveUTR = 30,minCDS = 30, minThreeUTR = 30)
loadRegions(txdb, parts = c("leaders", "cds", "trailers"), names.keep = txNames)The regions are now loaded into .GlobalEnv, only keeping transcripts from txNames.
2.3 Plotting with ORFik experiments
Lets make a plot with coverage over mrna in just ribo-seq
transcriptWindow(leaders, cds, trailers, df[3,])## RFP## [[1]]
##
## [[2]]
3 P-site shifting experiment
If your experiment consists of Ribo-seq, you want to do p-site shifting.
shiftFootprintsByExperiment(df[df$libtype == "RFP",])P-shifted ribo-seq will automaticly be stored as .wig (wiggle files for IGV and other genome browsers) and .ofst (ORFik serialized for R) files in a ./pshifted folder, relative to original libraries.
To validate p-shifting, use shiftPlots. Here is an example from Bazzini et al. 2014 I made.
df.baz <- read.experiment("zf_bazzini14_RFP")
shiftPlots(df.baz, title = "Ribo-seq, zebrafish, Bazzini et al. 2014")
p-site analysis
To see the shifts per library do:
shifts.load(df)To see the location of pshifted files:
filepath(df[df$libtype == "RFP",], type = "pshifted")To load p-shifted libraries, you can do:
outputLibs(df[df$libtype == "RFP",], type = "pshifted")3.1 Converting bam files to faster formats
Bam files are slow to load, and usually you don’t need all the information contained in a bam file.
Usually you convert to bed or wig files, but ORFik also support 2 formats for much faster loading and use of data.
3.1.1 ofst: ORFik serialized format
From the bam file store these columns as a serialized file: seqname, start, cigar, strand, score (number of identical replicates for that read).
This is the fastest format to use, loading time of 10GB Ribo-seq bam file reduced from minutes to ~ 1 second and ~ 20MB size.
3.1.2 bedo: bed ORFik file
From the bam file store these columns as text file: seqname, start, end (if not all widths are 1), strand, score (number of identical replicates for that read), size (size of cigar Ms according to reference)
The R object loaded from these files are GRanges, since cigar is not needed.
Loading time of 10GB Ribo-seq bam file reduced to ~ 10 seconds and ~ 100MB size.
3.1.3 bedoc: bed ORFik file with cigar
From the bam file store these columns as text file: seqname, cigar, start, strand, score (number of identical replicates for that read)
The R object loaded from these files are GAlignments or GAlignmentPairs, since cigar is needed.
Loading time of 10GB Ribo-seq bam file reduced to ~ 15 seconds and ~ 200MB size.
4 ORFik QC report
ORFik also support a full QC report for post alignment statistics, correlation plots, simplified libraries for plotting, meta coverage, ++.
4.1 General report
The default QC report:
QCreport(df)The plots and statistics are saved to disc. To see the statistics, you can do:
QCstats(df)4.2 Ribo-seq specific QC
In addition there is a QC report for Ribo-seq, with some addition analysis of read lengths and frames. This should only be run on when you have pshifted the reads.
RiboQC.plot(df)5 Using the ORFik system in your script
Usually you want to do some operation on multiple data-sets. If ORFik does not include a premade function for what you want, you can make it yourself. If your data is in the format of an ORFik experiment, this operation is simple.
5.1 Looping over all libraries in experiment
There are 3 ways to run loops for the data:
- if you know you have enough memory to load all data at once
outputLibs(df, type = "pshifted") # Output all libraries, fastest way
libs <- bamVarName(df) # <- here are names of the libs that were outputed
cds <- loadRegion(df, "cds")
# parallel loop
bplapply(libs, FUN = function(lib, cds) {
return(entropy(cds, get(lib)))
}, cds = cds)- Not loading data to global environment
files <- filepath(df, type = "pshifted")
cds <- loadRegion(df, "cds")
# parallel loop
res <- bplapply(files, FUN = function(file, cds) {
return(entropy(cds, fimport(file)))
}, cds = cds)- No parallel evaluation
files <- filepath(df, type = "pshifted")
cds <- loadRegion(df, "cds")
# Single thread loop
lapply(files, FUN = function(file, cds) {
return(entropy(cds, fimport(file)))
}, cds = cds)5.1.1 Reformat output to data.table (merge column-wise)
library(data.table)
outputLibs(df, type = "pshifted")
libs <- bamVarName(df) # <- here are names of the libs that were outputed
cds <- loadRegion(df, "cds")
# parallel loop
res <- bplapply(libs, FUN = function(lib, cds) {
return(entropy(cds, get(lib)))
}, cds = cds)
# Add some names and convert
names(res) <- libs
data.table::setDT(res) # Will give 1 column per library
res # Now by columns