---
title: >
pcaExplorer User Guide
author:
- name: Federico Marini
affiliation:
- &id1 Institute of Medical Biostatistics, Epidemiology and Informatics (IMBEI), Mainz
- Center for Thrombosis and Hemostasis (CTH), Mainz
email: marinif@uni-mainz.de
- name: Harald Binder
affiliation: *id1
date: "`r BiocStyle::doc_date()`"
package: "`r BiocStyle::pkg_ver('pcaExplorer')`"
abstract: >
`r Biocpkg("pcaExplorer")` provides functionality for interactive visualization
of RNA-seq datasets based on Principal Components Analysis. Such methods allow
for quick information extraction and effective data exploration. A Shiny
application encapsulates the whole analysis, and is developed to become a practical
companion for any RNA-seq dataset. This app supports reproducible research with
state saving and automated report generation.
output:
BiocStyle::html_document:
toc_float: true
fig_caption: TRUE
vignette: >
%\VignetteIndexEntry{pcaExplorer User Guide}
%\VignetteEngine{knitr::rmarkdown}
%\VignetteEncoding{UTF-8}
%\VignettePackage{pcaExplorer}
%\VignetteKeywords{Visualization, RNASeq, DimensionReduction, PrincipalComponent, QualityControl, GUI, ReportWriting}
---
**Package**: `r Rpackage("pcaExplorer")`
**Authors**: `r packageDescription("pcaExplorer")[["Author"]]`
**Version**: `r packageDescription("pcaExplorer")$Version`
**Compiled date**: `r Sys.Date()`
**Last edited**: 2019-02-26
**License**: `r packageDescription("pcaExplorer")[["License"]]`
```{r style, echo = FALSE, results = 'asis'}
BiocStyle::markdown()
```
```{r setup, echo=FALSE, warning=FALSE}
library(knitr)
set.seed(42)
opts_chunk$set(comment=NA,
fig.align="center",
warning=FALSE)
stopifnot(requireNamespace("htmltools"))
htmltools::tagList(rmarkdown::html_dependency_font_awesome())
```
# Getting started
`r Biocpkg("pcaExplorer")` is an R package distributed as part of the [Bioconductor](http://bioconductor.org) project.
To install the package, start R and enter:
```{r installation, eval=FALSE}
if (!requireNamespace("BiocManager", quietly=TRUE))
install.packages("BiocManager")
BiocManager::install("pcaExplorer")
```
To install `r Biocpkg("pcaExplorer")` with all its dependencies (i.e. also the ones listed in the `Suggests:` field of the `DESCRIPTION` file, which include the dataset from the `r Biocpkg("airway")` package used as a demo), use this command instead:
```{r installfull, eval=FALSE}
BiocManager::install("pcaExplorer", dependencies = TRUE)
```
If you prefer, you can install and use the development version, which can be retrieved via Github (https://github.com/federicomarini/pcaExplorer).
To do so, use:
```{r installation-github, eval=FALSE}
library("devtools")
install_github("federicomarini/pcaExplorer")
```
Once `r Rpackage("pcaExplorer")` is installed, it can be loaded by the following command.
```{r loadlibrary, message=FALSE}
library("pcaExplorer")
```
# Introduction
`r Biocpkg("pcaExplorer")` is a Bioconductor package containing a Shiny application for analyzing expression data in different conditions and experimental factors.
It is a general-purpose interactive companion tool for RNA-seq analysis, which guides the user in exploring the Principal Components of the data under inspection.
`r Biocpkg("pcaExplorer")` provides tools and functionality to detect outlier samples, genes that show particular patterns, and additionally provides a functional interpretation of the principal components for further quality assessment and hypothesis generation on the input data.
Moreover, a novel visualization approach is presented to simultaneously assess the effect of more than one experimental factor on the expression levels.
Thanks to its interactive/reactive design, it is designed to become a practical companion to any RNA-seq dataset analysis, making exploratory data analysis accessible also to the bench biologist, while providing additional insight also for the experienced data analyst.
Starting from development version 1.1.3, `r Biocpkg("pcaExplorer")` supports reproducible research with state saving and automated report generation.
Each generated plot and table can be exported by simple mouse clicks on the dedicated buttons.
## Citation info
If you use `r Biocpkg("pcaExplorer")` for your analysis, please cite it as here below:
```{r}
citation("pcaExplorer")
```
# Launching the application
After loading the package, the `r Biocpkg("pcaExplorer")` app can be launched in different modes:
- `pcaExplorer(dds = dds, dst = dst)`, where `dds` is a `DESeqDataSet` object and `dst` is a `DESeqTransform` object, which were created during an existing session for the analysis of an RNA-seq dataset with the `r Biocpkg("DESeq2")` package.
- `pcaExplorer(dds = dds)`, where `dds` is a `DESeqDataSet` object. The `dst` object can be automatically computed upon launch, choosing between rlog transformation, variance stabilizing transformations, or shifted logarithm transformation (with pseudocount = 1).
- `pcaExplorer(countmatrix = countmatrix, coldata = coldata)`, where `countmatrix` is a count matrix, generated after assigning reads to features such as genes via tools such as `HTSeq-count` or `featureCounts`, and `coldata` is a data frame containing the experimental covariates of the experiments, such as condition, tissue, cell line, run batch and so on.
If the data is provided in this way, the user can click on the "Generate the dds and dst objects" button to complete the setup and enable the subsequent steps in the other panels.
- `pcaExplorer()`, and then subsequently uploading the count matrix and the covariates data frame through the user interface. These files need to be formatted as tab, semicolon, or comma separated text files, all of which are common formats for storing such count values.
Additional parameters and objects that can be provided to the main `r Biocpkg("pcaExplorer")` function are:
- `pca2go`, which is an object created by the `pca2go` function, which scans the genes with high loadings in each principal component and each direction, and looks for functions (such as GO Biological Processes) that are enriched above the background.
The offline `pca2go` function is based on the routines and algorithms of the `r Biocpkg("topGO")` package, but as an alternative, this object can be computed live during the execution of the app with `limmaquickpca2go` (which relies on the `goana` function provided by the `r Biocpkg("limma")` package).
Although this likely provides more general (and probably less informative) functions, it is a good compromise for quickly obtaining a further data interpretation.
- `annotation`, a data frame object, with `row.names` as gene identifiers (e.g. ENSEMBL ids) identical to the row names of the count matrix or `dds` object, and an extra column `gene_name`, containing e.g. HGNC-based gene symbols.
This can be used for making information extraction easier, as ENSEMBL ids (a usual choice when assigning reads to features) do not provide an immediate readout for which gene they refer to.
This can be either passed as a parameter when launching the app, or also uploaded as a text file (either tab, comma, or semicolon-separated).
The package provides two functions, `get_annotation` and `get_annotation_orgdb`, as a convenient wrapper to obtain the updated annotation information, respectively from `biomaRt` or via the `org.XX.eg.db` packages.
## How to provide your input data in `r Biocpkg("pcaExplorer")`
`r Biocpkg("pcaExplorer")` supports a number of file formats when uploading the data via the file input widgets.
Starting from version 2.9.5, we added functionality to select the separator character for each of the uploadable files.
An information box is also shown by clicking on the question mark icon in the Data upload panel, with detailed information (text, as well as screenshots of valid input files) on the format specification.
In general, `r Biocpkg("pcaExplorer")` requires by default tab separated files:
- the `countmatrix`: contains the expression matrix, with one gene per row and one sample per column; the first column should contain the gene identifiers, and the header (first row) specifies the sample names.
- the `coldata`: one sample per row, and one experimental covariate per column.
Row names should be specified in the first column, and have to match the column names of the `countmatrix`.
Column names will contain the specific experimental covariates.
- the `annotation` (optional): one gene per row, and one identifier type per column.
Gene identifiers in the first column are identical to the row names of the `countmatrix` or `dds` objects.
At least an extra column `gene_name`, containing e.g. HGNC-based gene symbols, needs to be provided.
## Up and running with `r Biocpkg("pcaExplorer")`
We recommend users to switch to the `r Biocpkg("pcaExplorer", vignette="upandrunning.html", label="dedicated vignette")`, entitled "Up and running with `r Biocpkg('pcaExplorer')`".
This document describes a use case for `r Biocpkg("pcaExplorer")`, based on the dataset in the `r Biocpkg("airway")` package.
# The controls sidebar
Most of the input controls are located in the sidebar, some are as well in the individual tabs of the app.
By changing one or more of the input parameters, the user can get a fine control on what is displayed.
## App settings
Here are the parameters that set input values for most of the tabs.
By hovering over with the mouse, the user can receive additional information on how to set the parameter, with tooltips powered by the `r CRANpkg("shinyBS")` package.
- **x-axis PC** - Select the principal component to display on the x axis
- **y-axis PC** - Select the principal component to display on the y axis
- **Group/color by** - Select the group of samples to stratify the analysis. Can also assume multiple values.
- **Nr of (most variant) genes** - Number of genes to select for computing the principal components. The top n genes are selected ranked by their variance inter-samples
- **Alpha** - Color transparency for the plots. Can assume values from 0 (transparent) to 1 (opaque)
- **Labels size** - Size of the labels for the samples in the principal components plots.
This parameter also controls the size of the gene labels, which are displayed in the Genes View once the user has brushed an area in the main plot.
- **Points size** - Size of the points to be plotted in the principal components plots
- **Variable name size** - Size of the labels for the genes PCA - correspond to the samples names
- **Scaling factor** - Scale value for resizing the arrow corresponding to the variables in the PCA for the genes. It should be used for mere visualization purposes
- **Color palette** - Select the color palette to be used in the principal components plots. The number of colors is selected automatically according to the number of samples and to the levels of the factors of interest and their interactions
- **Plot style for gene counts** - Plot either boxplots or violin plots, with jittered points superimposed
## Plot export settings
**Width** and **height** for the figures to export are input here in cm.
Additional controls available in the single tabs are also assisted by tooltips that show on hovering the mouse.
Normally they are tightly related to the plot/output they are placed nearby.
# The task menu
The task menu, accessible by clicking on the cog icon in the upper right part of the application, provides two functionalities:
- `Exit pcaExplorer & save` will close the application and store the content of the `input` and `values` reactive objects in two list objects made available in the global environment, called `pcaExplorer_inputs_YYYYMMDD_HHMMSS` and `pcaExplorer_values_YYYYMMDD_HHMMSS`
- `Save State as .RData` will similarly store `LiveInputs` and `r_data` in a binary file named `pcaExplorerState_YYYYMMDD_HHMMSS.Rdata`, without closing the application
# The app panels
The `r Biocpkg("pcaExplorer")` app is structured in different panels, each focused on a different aspect of the data exploration.
Most of the panels work extensively with click-based and brush-based interactions, to gain additional depth in the explorations, for example by zooming, subsetting, selecting.
This is possible thanks to the recent developments in the `r CRANpkg("shiny")` package/framework.
The available panels are described in the following subsections.
## Data Upload
These **file input** controls are available when no `dds` or `countmatrix` + `coldata` are provided.
Additionally, it is possible to upload the `annotation` data frame.
If the objects are already passed as parameters, or after they have been successfully uploaded, a brief overview/summary for them can be displayed, by clicking on each respective action button.
This panel is where you can perform the preprocessing steps on the data you uploaded/provided: - compose the `dds` object (if you provided `countmatrix` and `coldata`) - normalize the expression values (using the robust method proposed by Anders and Huber in the original DESeq manuscript) - compute the variance stabilizing transformed expression values (stored in the `dst` object). As a note regarding the normalization procedure: the normalization method (implemented in `estimateSizeFactors`) relies on the hypothesis that most of the genes are not differentially expressed across experimental groups, and this holds true for the majority of scenarios. The `DESeqDataSet` object, which pcaExplorer takes as main data container, can still accommodate sample (and gene) specific normalization factors. Should this assumption be violated, users can pre-compute these factors and store them in the input `dds` object. ## Instructions This is where you might be reading a version of the "Up and running with `r Biocpkg('pcaExplorer')`" vignette. Additionally, you can easily reach the fully rendered vignettes, either installed locally, or directly from the Bioconductor package page.
## Counts Table Interactive tables for the raw, normalized or transformed (rlog, variance stabilized, or shifted log) counts are shown in this tab. The user can also generate a sample-to-sample correlation scatter plot with the selected data.
## Data Overview This panel displays information on the objects in use, either passed as parameters or generated from the count matrix provided. Displayed information comprise the design metadata, a sample to sample distance heatmap, the number of million of reads per sample and some basic summary for the counts.
## Samples View This panel displays the PCA projections of sample expression profiles onto any pair of components, a scree plot, a zoomed PCA plot, a plot of the genes with top and bottom loadings. Additionally, this section presents a PCA plot where it is possible to remove samples deemed to be outliers in the analysis, which is very useful to check the effect of excluding them. If needed, an interactive 3D visualization of the principal components is also available.
## Genes View This panel displays the PCA projections of genes abundances onto any pair of components, with samples as biplot variables, to identify interesting groups of genes. Zooming is also possible, and clicking on single genes, a boxplot is returned, grouped by the factors of interest. A static and an interactive heatmap are provided, including the subset of selected genes, also displayed as (standardized) expression profiles across the samples. These are also reported in `datatable` objects, accessible in the bottom part of the tab.
## GeneFinder The user can search and display the expression values of a gene of interest, either by ID or gene name, as provided in the `annotation`. A handy panel for quick screening of shortlisted genes, again grouped by the factors of interest. The graphic can be readily exported as it is, and this can be iterated on a shortlisted set of genes. For each of them, the underlying data is displayed in an interactive table, also exportable with a click.
## PCA2GO This panel shows the functional annotation of the principal components, with GO functions enriched in the genes with high loadings on the selected principal components. It allows for the live computing of the object, that can otherwise provided as a parameter when launching the app. The panel displays a PCA plot for the samples, surrounded on each side by the tables with the functions enriched in each component and direction.
### More on the `pca2go` parameter A note on the functionality provided by the PCA2GO tab: if it is not provided in the `pca2go` parameter, the user can still compute this object while using the app, and this is done using `limma::goana`. The implementation of this function supports a few organism packages, which cover many use cases (human, mouse, rat, fruit fly, or chimpanzee), but some use cases are not directly covered (e.g. if you are working with plants like Arabidopsis Thaliana). For example, with a dataset from Arabidopsis where the genes are encoded as TAIR (The Arabidopsis Information Resource) identifiers, one would ideally call the following commands ```{r eval=FALSE} BiocManager::install("org.At.tair.db") library("org.At.tair.db") # skipping the steps where you normally would generate your dds_at object... dds_at vst_at <- DESeq2::vst(dds_at) anno_at <- get_annotation_orgdb(dds_at,"org.At.tair.db", idtype = "TAIR") # subset the background to include only the expressed genes bg_ids <- rownames(dds_at)[rowSums(counts(dds_at)) > 0] library(topGO) pca2go_at <- pca2go(vst_at, annotation = anno_at, annopkg = "org.At.tair.db", ensToGeneSymbol = TRUE, background_genes = bg_ids) # and finally, with all the objects prepared... pcaExplorer(dds = dds_at, dst = vst_at, annotation = anno_at, pca2go = pca2go_at) ``` ## Multifactor Exploration This panel allows for the multifactor exploration of datasets with 2 or more experimental factors. The user has to select first the two factors and the levels for each. Then, it is possible to combine samples from Factor1-Level1 in the selected order by clicking on each sample name, one for each level available in the selected Factor2. In order to build the matrix, an equal number of samples for each level of Factor 1 is required, to keep the design somehow balanced. A typical case for choosing factors 1 and 2 is for example when different conditions and tissues are present. Once constructed, a plot is returned that tries to represent simultaneously the effect of the two factors on the data. Each gene is represented by a dot-line-dot structure, with the color that is indicating the tissue (factor 2) where the gene is mostly expressed. Each gene has two dots, one for each condition level (factor 1), and the position of the points is dictated by the scores of the principal components calculated on the matrix object. The line connecting the dots is darker when the tissue where the gene is mostly expressed varies throughout the conditions. This representation is under active development, and it is promising for identifying interesting sets or clusters of genes according to their behavior on the Principal Components subspaces. Zooming and exporting of the underlying genes is also allowed by brushing on the main plot.
## Report Editor The report editor is the backbone for generating and editing the interactive report on the basis of the uploaded data and the current state of the application. General `Markdown options` and `Editor options` are available, and the text editor, based on the `shinyAce` package, contains a comprehensive template report, that can be edited to the best convenience of the user. The editor supports R code autocompletion, making it easy to add new code chunks for additional sections. A preview is available in the tab itself, and the report can be generated, saved and subsequently shared with simple mouse clicks.
The functionality to display the report preview is based on `knit2html`, and some elements such as `DataTable` objects might not render correctly. To render them correctly, please install the PhantomJS executable before launching the app. This can be done by using the `r CRANpkg("webshot")` package and calling `webshot::install_phantomjs()` - HTML widgets will be rendered automatically as screenshots. Keep in mind that the fully rendered report (the one you can obtain with the "Generate & Save" button) is not affected by this, since it uses `rmarkdown::render()`. ## About Contains general information on `r Biocpkg("pcaExplorer")`, including the developer's contact, the link to the development version in Github, as well as the output of `sessionInfo`, to use for reproducibility sake - or bug reporting. Information for citing `r Biocpkg("pcaExplorer")` is also reported.
# Running `pcaExplorer` on published datasets We can run `r Biocpkg("pcaExplorer")` for demonstration purpose on published datasets that are available as SummarizedExperiment in a Bioconductor experiment package. We will use the `r Biocpkg("airway")` dataset, which can be installed with this command: ```{r installairway, eval=FALSE} if (!requireNamespace("BiocManager", quietly=TRUE)) install.packages("BiocManager") BiocManager::install("airway") ``` The `r Biocpkg("airway")` package provides a `RangedSummarizedExperiment` object of read counts in genes for an RNA-Seq experiment on four human airway smooth muscle cell lines treated with dexamethasone. More details such as gene models and count quantifications can be found in the `r Biocpkg("airway")` package vignette. The easiest way to explore the `r Biocpkg("airway")` dataset is by clicking on the dedicated button in the **Data Upload** panel. Otherwise, to run `r Biocpkg("pcaExplorer")` on this dataset from the terminal/RStudio IDE, the following commands are required. First, prepare the objects to be passed as parameters of `r Biocpkg("pcaExplorer")`. ```{r loadairway, message=FALSE} library(airway) library(DESeq2) data(airway) dds_airway <- DESeqDataSet(airway,design= ~ cell + dex) dds_airway rld_airway <- rlogTransformation(dds_airway) rld_airway ``` Then launch the app itself. ```{r launchairway, eval=FALSE} pcaExplorer(dds = dds_airway, dst = rld_airway) ``` The `annotation` for this dataset can be built by exploiting the `r Biocpkg("org.Hs.eg.db")` package. ```{r annoairway, message = FALSE} library(org.Hs.eg.db) genenames_airway <- mapIds(org.Hs.eg.db,keys = rownames(dds_airway),column = "SYMBOL",keytype="ENSEMBL") annotation_airway <- data.frame(gene_name = genenames_airway, row.names = rownames(dds_airway), stringsAsFactors = FALSE) head(annotation_airway) ``` or alternatively, by using the `get_annotation` or `get_annotation_orgdb` wrappers. ```{r annofuncs, eval=FALSE} anno_df_orgdb <- get_annotation_orgdb(dds = dds_airway, orgdb_species = "org.Hs.eg.db", idtype = "ENSEMBL") anno_df_biomart <- get_annotation(dds = dds_airway, biomart_dataset = "hsapiens_gene_ensembl", idtype = "ensembl_gene_id") ``` ```{r echo=FALSE} anno_df_orgdb <- get_annotation_orgdb(dds = dds_airway, orgdb_species = "org.Hs.eg.db", idtype = "ENSEMBL") ``` ```{r} head(anno_df_orgdb) ``` Then again, the app can be launched with: ```{r launchairwayanno, eval=FALSE} pcaExplorer(dds = dds_airway, dst = rld_airway, annotation = annotation_airway) # or anno_df_orgdb, or anno_df_biomart ``` If desired, alternatives can be used. See the well written annotation workflow available at the Bioconductor site (https://bioconductor.org/help/workflows/annotation/annotation/). # Running `pcaExplorer` on synthetic datasets For testing and demonstration purposes, a function is also available to generate synthetic datasets whose counts are generated based on two or more experimental factors. This can be called with the command: ```{r ddsmultifac} dds_multifac <- makeExampleDESeqDataSet_multifac(betaSD_condition = 3,betaSD_tissue = 1) ``` See all the available parameters by typing `?makeExampleDESeqDataSet_multifac`. Credits are given to the initial implementation by Mike Love in the `r Biocpkg("DESeq2")` package. The following steps run the app with the synthetic dataset. ```{r prepsimul} dds_multifac <- makeExampleDESeqDataSet_multifac(betaSD_condition = 1,betaSD_tissue = 3) dds_multifac rld_multifac <- rlogTransformation(dds_multifac) rld_multifac ## checking how the samples cluster on the PCA plot pcaplot(rld_multifac,intgroup = c("condition","tissue")) ``` Launch the app for exploring this dataset with: ```{r launchsimul, eval=FALSE} pcaExplorer(dds = dds_multifac, dst = rld_multifac) ``` When such a dataset is provided, the panel for multifactorial exploration is also usable at its best. # Functions exported by the package for standalone usage The functions exported by the `r Biocpkg("pcaExplorer")` package can be also used in a standalone scenario, provided the required objects are in the working environment. They are listed here for an overview, but please refer to the documentation for additional details. Where possible, for each function a code snippet will be provided for its typical usage. ## `pcaplot` `pcaplot` plots the sample PCA for `DESeqTransform` objects, such as rlog-transformed data. This is the workhorse of the Samples View tab. ```{r func-pcaplot} pcaplot(rld_airway,intgroup = c("cell","dex"),ntop = 1000, pcX = 1, pcY = 2, title = "airway dataset PCA on samples - PC1 vs PC2") # on a different set of principal components... pcaplot(rld_airway,intgroup = c("dex"),ntop = 1000, pcX = 1, pcY = 4, title = "airway dataset PCA on samples - PC1 vs PC4", ellipse = TRUE) ``` ## `pcaplot3d` Same as for `pcaplot`, but it uses the `threejs` package for the 3d interactive view. ```{r func-pcaplot3d, eval=FALSE} pcaplot3d(rld_airway,intgroup = c("cell","dex"),ntop = 1000, pcX = 1, pcY = 2, pcZ = 3) # will open up in the viewer ``` ## `pcascree` `pcascree` produces a scree plot of the PC computed on the samples. A `prcomp` object needs to be passed as main argument. ```{r func-pcascree} pcaobj_airway <- prcomp(t(assay(rld_airway))) pcascree(pcaobj_airway,type="pev", title="Proportion of explained proportion of variance - airway dataset") ``` ## `correlatePCs` and `plotPCcorrs` `correlatePCs` and `plotPCcorrs` respectively compute and plot significance of the (cor)relation of each covariate versus a principal component. The input for `correlatePCs` is a `prcomp` object. ```{r func-correlatepcs} res_pcairway <- correlatePCs(pcaobj_airway,colData(dds_airway)) res_pcairway plotPCcorrs(res_pcairway) ``` ## `hi_loadings` `hi_loadings` extracts and optionally plots the genes with the highest loadings. ```{r func-hiloadings} # extract the table of the genes with high loadings hi_loadings(pcaobj_airway,topN = 10,exprTable=counts(dds_airway)) # or alternatively plot the values hi_loadings(pcaobj_airway,topN = 10,annotation = annotation_airway) ``` ## `genespca` `genespca` computes and plots the principal components of the genes, eventually displaying the samples as in a typical biplot visualization. This is the function in action for the Genes View tab. ```{r func-genespca} groups_airway <- colData(dds_airway)$dex cols_airway <- scales::hue_pal()(2)[groups_airway] # with many genes, do not plot the labels of the genes genespca(rld_airway,ntop=5000, choices = c(1,2), arrowColors=cols_airway,groupNames=groups_airway, alpha = 0.2, useRownamesAsLabels=FALSE, varname.size = 5 ) # with a smaller number of genes, plot gene names included in the annotation genespca(rld_airway,ntop=100, choices = c(1,2), arrowColors=cols_airway,groupNames=groups_airway, alpha = 0.7, varname.size = 5, annotation = annotation_airway ) ``` ## `topGOtable` `topGOtable` is a convenient wrapper for extracting functional GO terms enriched in a subset of genes (such as the differentially expressed genes), based on the algorithm and the implementation in the `r Biocpkg("topGO")` package. ```{r func-topGOtable, eval=FALSE} # example not run due to quite long runtime dds_airway <- DESeq(dds_airway) res_airway <- results(dds_airway) res_airway$symbol <- mapIds(org.Hs.eg.db, keys=row.names(res_airway), column="SYMBOL", keytype="ENSEMBL", multiVals="first") res_airway$entrez <- mapIds(org.Hs.eg.db, keys=row.names(res_airway), column="ENTREZID", keytype="ENSEMBL", multiVals="first") resOrdered <- as.data.frame(res_airway[order(res_airway$padj),]) head(resOrdered) # extract DE genes de_df <- resOrdered[resOrdered$padj < .05 & !is.na(resOrdered$padj),] de_symbols <- de_df$symbol # extract background genes bg_ids <- rownames(dds_airway)[rowSums(counts(dds_airway)) > 0] bg_symbols <- mapIds(org.Hs.eg.db, keys=bg_ids, column="SYMBOL", keytype="ENSEMBL", multiVals="first") # run the function topgoDE_airway <- topGOtable(de_symbols, bg_symbols, ontology = "BP", mapping = "org.Hs.eg.db", geneID = "symbol") ``` ## `pca2go` {#pca2go-docs} `pca2go` provides a functional interpretation of the principal components, by extracting the genes with the highest loadings for each PC, and then runs internally `topGOtable` on them for efficient functional enrichment analysis. This function requires a `DESeqTransform` object as main parameter. ```{r func-pca2go, eval=FALSE} pca2go_airway <- pca2go(rld_airway, annotation = annotation_airway, organism = "Hs", ensToGeneSymbol = TRUE, background_genes = bg_ids) # for a smooth interactive exploration, use DT::datatable datatable(pca2go_airway$PC1$posLoad) # display it in the normal R session... head(pca2go_airway$PC1$posLoad) # ... or use it for running the app and display in the dedicated tab pcaExplorer(dds_airway,rld_airway, pca2go = pca2go_airway, annotation = annotation_airway) ``` ## `limmaquickpca2go` `limmaquickpca2go` is an alternative to `pca2go`, used in the live running app, thanks to its fast implementation based on the `limma::goana` function. ```{r func, message = FALSE, eval = FALSE} goquick_airway <- limmaquickpca2go(rld_airway, pca_ngenes = 10000, inputType = "ENSEMBL", organism = "Hs") # display it in the normal R session... head(goquick_airway$PC1$posLoad) # ... or use it for running the app and display in the dedicated tab pcaExplorer(dds_airway,rld_airway, pca2go = goquick_airway, annotation = annotation_airway) ``` ## `makeExampleDESeqDataSet_multifac` `makeExampleDESeqDataSet_multifac` constructs a simulated `DESeqDataSet` of Negative Binomial dataset from different conditions. The fold changes between the conditions can be adjusted with the `betaSD_condition` and `betaSD_tissue` arguments. ```{r func-makedataset} dds_simu <- makeExampleDESeqDataSet_multifac(betaSD_condition = 3,betaSD_tissue = 0.5) dds_simu dds2_simu <- makeExampleDESeqDataSet_multifac(betaSD_condition = 0.5,betaSD_tissue = 2) dds2_simu rld_simu <- rlogTransformation(dds_simu) rld2_simu <- rlogTransformation(dds2_simu) pcaplot(rld_simu,intgroup = c("condition","tissue")) + ggplot2::ggtitle("Simulated data - Big condition effect, small tissue effect") pcaplot(rld2_simu,intgroup = c("condition","tissue")) + ggplot2::ggtitle("Simulated data - Small condition effect, bigger tissue effect") ``` ## `distro_expr` Plots the distribution of expression values, either with density lines, boxplots or violin plots. ```{r eval=FALSE} distro_expr(rld_airway,plot_type = "density") distro_expr(rld_airway,plot_type = "violin") ``` ```{r} distro_expr(rld_airway,plot_type = "boxplot") ``` ## `geneprofiler` Plots the profile expression of a subset of genes, optionally as standardized values. ```{r} dds <- makeExampleDESeqDataSet_multifac(betaSD_condition = 3,betaSD_tissue = 1) dst <- DESeq2::rlogTransformation(dds) set.seed(42) geneprofiler(dst,paste0("gene",sample(1:1000,20)), plotZ = FALSE) ``` ## `get_annotation` and `get_annotation_orgdb` These two wrapper functions retrieve the latest annotations for the `dds` object, to be used in the call to the `pcaExplorer` function. They use respectively the `biomaRt` package and the `org.XX.eg.db` packages. ```{r eval=FALSE} anno_df_biomart <- get_annotation(dds = dds_airway, biomart_dataset = "hsapiens_gene_ensembl", idtype = "ensembl_gene_id") anno_df_orgdb <- get_annotation_orgdb(dds = dds_airway, orgdb_species = "org.Hs.eg.db", idtype = "ENSEMBL") ``` ## `pair_corr` Plots the pairwise scatter plots and computes the correlation coefficient on the expression matrix provided. ```{r} # use a subset of the counts to reduce plotting time, it can be time consuming with many samples pair_corr(counts(dds_airway)[1:100,]) ``` # Further development Additional functionality for the `r Biocpkg("pcaExplorer")` will be added in the future, as it is tightly related to a topic under current development research. Improvements, suggestions, bugs, issues and feedback of any type can be sent to marinif@uni-mainz.de. # Session info {-} ```{r} sessionInfo() ```