The explosion of the usage of Next Generation Sequencing techniques during the past few years due to the seemingly endless portfolio of applications has created the need for new NGS data analytics tools which are able to offer comprehensive and at the same time flexible visualizations under several experimental settings and factors. An established visualization tool in NGS experiments is the visualization of the signal created by short reads after the application of every NGS protocol. Genome Browsers (e.g. the UCSC Genome Browser) serve very well this purpose considering single genomic areas. They are very good when it comes to the visualization of the abundance of a single or a few genes or the strength of a few protein-DNA interaction sites. However, when it comes to the visualization of average signal profiles over multiple genomic locations (gene regions or others like DNA methylation sites or transcription factor binding sites), Genome Browsers fail to depict such information in a comprehensive way. Furthermore, they cannot visualize average signal profiles of factored data, for example a set of genes categorized in high, medium and low expression or even by strand and they cannot visualize all signals of interest mapped on all the genomic regions of interest in a compact way, something that can be done using for example a heatmap.
In such cases, bioinformaticians use several toolkits like BEDTools and facilities from R/Bioconductor to read/import short reads and overlap them with genomic regions of interest, summarize them by binning/averaging overlaps to control the resolution of final graphics etc. This procedure often requires the usage of multiple tools and custom scripts with multiple steps. One of the most comprehensive and easy-to-use tools up to date is ngs.plot. It is sufficiently fast for most applications and has a low memory footprint which allows users to run it in low end machines too. It is command line based and users can run it by using a simple configuration file most of the times, has a rich database of genome annotation and genomic features and uses R/Bioconductor for underlying calculations and plotting of profiles. However, ngs.plot is not up to date with modern R graphics systems like ggplot2
and ComplexHeatmap
. As a result, among others, it is impossible to create faceted genomic profiles using a statistical design and in such cases, a lot of additional manual work and computational time is required in order to reach the desired outcomes. The same applies to heatmap profiles. Furthermore, the resolution of genomic profiles (e.g. per base coverage or per bin of base-pairs coverage) cannot be controlled and this can cause problems in cases where extreme levels of resolution (e.g. DNAse-Seq experiments) is required to reach meaningful biological conclusions. Last but not least, ngs.plot requires a not so straightforward setup in order to run, does not run in a unified working environment (e.g. R environment with its graphics displaying mechanisms) and in some cases produces oversized and complex output.
The recoup package comes to fill such gaps by stepping on the shoulders of giants. It uses the now standardized and stable Bioconductor facilities to read and import short reads from BAM/BED files or processed genomic signals from BIGWig files and also modern R graphics systems, namely ggplot2 and ComplexHeatmap in order to create comprehensive averaged genomic profiles and genomic profile heatmaps. In addition it offers a lot of (easy to use) customization options and automation at various levels. Inexperienced users can gather their data in a simple text file and just choose one of the supported organisms and recoup does the rest for them. More experienced users can play with several options and provide more flexible input so as to produce optimal results. This vignette, although it covers basic usage of the package, it offers the basis for more sophisticated usage. recoup is not as fast as ngs.plot but we are working on this! Also, recoup is not here to replace other more mature packages. It is here to offer more options to users that need more sophisticated genomic profile visualizations. Finally, it offers a very flexible way to reuse genomic profiles whose calculations may be computationally and time expensive by offering a smart way to recognize which parameters have changed and acting based on these.
Specifically, recoup creates three types of plots:
All plots can be faceted using a design file with the categories into which the plots should be separated. All the above are illustrated in the examples in the vignettes of this package.
Detailed instructions on how to run the recoup genomic profile creation pipeline can be found under the main documentation of the package:
library(recoup)
help(recoup)
Briefly, to run recoup you need:
recoup
man page). They can also be provided as an organism version keyword, e.g. hg19
or mm9
and the respective regions will be either retrieved from a local recoup
annotation database setup, or downloaded on the fly (takes significantly more time as some extra operations are required).The package contains a small dataset which serves only for package building and testing purposes as well as complying with Bioconductor guidelines. These data are useful for the user to check how the input data to recoup should look like. For a more complete test dataset (a small one) have a look and download from here
The following commands should provide some information on the embedded test data, which are subsets of the complete test data in the above link.
help(test.input)
help(test.genome)
help(test.design)
help(test.exons)
In order to run smoothly some usage examples and produce some realistic results, you need to download a set of example BAM files, genomic regions and design files from here. Following, a description of each file in the archive (the tissue is always liver):
recoup
annotation databaseIn order to run the vignette examples, you should download and extract the archive to a path of your preference, e.g. /home/me/recoup_tutorial
.
Apart from a user specified file, the reference genomic regions used by recoup to construct average profiles over, can be predefined gene set from a few common organisms supported by recoup. See the recoup
man page for a list of these organisms. In order to use this “database” of predefined genomic areas, you should run the function buildAnnotationStore
with a list of organisms, a list of annotation sources (Ensembl, RefSeq and UCSC supported) and a desired path to store the annotations (defaults to /home/me/.recoup
). For example:
buildAnnotationStore(c("hg19","mm9","rn4"),c("ensembl","refseq"))
See the man page of buildAnnotationStore
for more details. This step is not necessary for recoup to run as these annotations can be also downloaded on the fly. However, if subsets of the supported organisms are to be used often, it is much more preferrable to spend some time building the local store as it can save a lot of running time later by investing some time in the beginning to build this store.
The recoup
function can be used to create coverage profiles from ChIP-Seq like experiments (signals over continuous genomic regions) or from RNA-Seq experiments (signals over non-continuous genomic regions). Due to restrictions (logical ones) imposed by the Bioconductor development core team, the data that are required for a realistic tutorial of the recoup
package cannot be included. Thus, this page along with the rest of the tutorial on how to create genomic profiles from ChIP-Seq or RNA-Seq data can be found either here or in the wiki recoup
pages in github
recoup
deals with that in four possible ways:
spline
function with the default method)approx
function with the default method)NA
values are distributed randomly across the small area coverage vector (e.g. gene with length smaller than the desired number of bins), excluding the first and the last two positions, in order to reach the desired number of bins. Then, each NA
position is filled with the mean value of the two values before and the two values after the NA
position. This method should be avoided when >20% of the values of the extended vector are NA
’s as it may cause a crash. However, it should be the most accurate one in the opposite case (few NA
’s). See the recoup
man page for further information.In the two vignettes explaining the useage of the recoup
package and its functions and in the examples, you will notice the direct use of plot
function instead of direct plotting (plotParams$plot=FALSE
instead of the default TRUE
) or the recoupPlot
function. This has been done on purpose as at this point, it is not straighforward how to tell the knitr
vignette builder how to plot objects created within called functions.
Due to strict Bioconductor guidelines regarding package size, these vignettes can also be found in the github package page with a little more examples.
## R version 3.4.0 (2017-04-21)
## Platform: x86_64-pc-linux-gnu (64-bit)
## Running under: Ubuntu 16.04.2 LTS
##
## Matrix products: default
## BLAS: /home/biocbuild/bbs-3.5-bioc/R/lib/libRblas.so
## LAPACK: /home/biocbuild/bbs-3.5-bioc/R/lib/libRlapack.so
##
## locale:
## [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
## [3] LC_TIME=en_US.UTF-8 LC_COLLATE=C
## [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
## [7] LC_PAPER=en_US.UTF-8 LC_NAME=C
## [9] LC_ADDRESS=C LC_TELEPHONE=C
## [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
##
## attached base packages:
## [1] grid parallel stats4 stats graphics grDevices utils
## [8] datasets methods base
##
## other attached packages:
## [1] recoup_1.4.0 ComplexHeatmap_1.14.0
## [3] ggplot2_2.2.1 GenomicAlignments_1.12.0
## [5] Rsamtools_1.28.0 Biostrings_2.44.0
## [7] XVector_0.16.0 SummarizedExperiment_1.6.0
## [9] DelayedArray_0.2.0 matrixStats_0.52.2
## [11] Biobase_2.36.0 GenomicRanges_1.28.0
## [13] GenomeInfoDb_1.12.0 IRanges_2.10.0
## [15] S4Vectors_0.14.0 BiocGenerics_0.22.0
## [17] BiocStyle_2.4.0
##
## loaded via a namespace (and not attached):
## [1] viridis_0.4.0 viridisLite_0.2.0
## [3] GenomeInfoDbData_0.99.0 yaml_2.1.14
## [5] robustbase_0.92-7 RSQLite_1.1-2
## [7] backports_1.0.5 lattice_0.20-35
## [9] digest_0.6.12 RColorBrewer_1.1-2
## [11] colorspace_1.3-2 htmltools_0.3.5
## [13] Matrix_1.2-9 plyr_1.8.4
## [15] XML_3.98-1.6 GetoptLong_0.1.6
## [17] biomaRt_2.32.0 zlibbioc_1.22.0
## [19] mvtnorm_1.0-6 scales_0.4.1
## [21] whisker_0.3-2 BiocParallel_1.10.0
## [23] tibble_1.3.0 nnet_7.3-12
## [25] lazyeval_0.2.0 magrittr_1.5
## [27] mclust_5.2.3 memoise_1.1.0
## [29] evaluate_0.10 MASS_7.3-47
## [31] class_7.3-14 tools_3.4.0
## [33] GlobalOptions_0.0.11 trimcluster_0.1-2
## [35] stringr_1.2.0 kernlab_0.9-25
## [37] munsell_0.4.3 cluster_2.0.6
## [39] AnnotationDbi_1.38.0 fpc_2.1-10
## [41] compiler_3.4.0 RCurl_1.95-4.8
## [43] rjson_0.2.15 circlize_0.3.10
## [45] bitops_1.0-6 rmarkdown_1.4
## [47] gtable_0.2.0 flexmix_2.3-13
## [49] DBI_0.6-1 gridExtra_2.2.1
## [51] rtracklayer_1.36.0 knitr_1.15.1
## [53] prabclus_2.2-6 rprojroot_1.2
## [55] dendextend_1.5.2 shape_1.4.2
## [57] modeltools_0.2-21 stringi_1.1.5
## [59] Rcpp_0.12.10 DEoptimR_1.0-8
## [61] diptest_0.75-7