RTNduals is a tool derived from the [RTN](http://bioconductor.org/packages/RTN/) (Reconstruction of Transcriptional Networks) package and searches for possible co-regulatory relationships between pairs of regulators. The tool infers dual regulons, a concept that tests whether pairs of regulators have similar effects on shared target genes. Regulons can be of different types (e.g. transcription factor (TF)-TF, miRNA-miRNA, TF-miRNA, TF-mRNA).
output: BiocStyle::html_document: css: custom.css vignette: > %\VignetteIndexEntry{"RTNduals: analysis of co-regulation and inference of dual regulons."} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- # Overview Recurrent patterns in biological networks may reflect critical roles in multiple biological processes [@Bracken2016], for example, regulatory loops between transcription factors and microRNAs [@Zhang2015]. **RTNduals** searches for regulatory patterns between pairs of regulators, using regulatory networks generated by the **RTN package** (for details, please refer to the [RTN documentation](http://bioconductor.org/packages/RTN/)) [@Castro2016]. In such a network, each regulator has an associated set of target genes (i.e. a regulon), and when we assess the shared targets between a pair of regulators, we find triplets that may be regulated in a positive or negative direction, whith regulators either cooperating or competing in the regulatory network. The inference of *dual regulons* requires three complementary statistics: (1) Targets are assigned to regulons based on mutual information (MI) between the regulator and the target. The significance of the MI statistics is assessed by permutation and bootstrap analysis. (2) Shared targets between any two regulons are identified and the similarity in regulation (i.e. positive or negative direction) is assessed by correlation analysis. (3) A test is carried out to determine if the number of shared targets is higher than expected by chance. The schematics in **Figure 1** show two triplets formed between regulators. In (**a**) the two regulators co-operate by influencing shared targets in the same direction (co-activation or co-repression), while in (**b**) they compete, influencing targets in opposite directions. For gene expression data, typical regulators might include transcription factors, miRNAs, eRNAs and lncRNAs.  Figure 1. Examples of regulators and predicted associations. This figure illustrates four triplets formed between regulators (a). Regulators R1 and R2 co-activate or co-repress shared targets. (b) Regulators R1 and R2 compete, influencing targets in opposite directions. # Quick Start The **RTNduals** workflow starts with a preprocessing step that generates an **MBR-class** (Motifs Between Regulons) object from an expression matrix and a list of regulators. The expression matrix is typically obtained from multiple samples (e.g. transcriptomes from a cancer cohort), while the list of regulators represents some prior biological information indicating which genes in the expression matrix should be regarded as regulators. The input data can also deal with different classes of regulators; for example, genes and microRNAs. In this case, the expression matrix should comprise mRNA and miRNA expression values. Alternatively, the **MBR-class** object can be obtained from a **TNI-class** object pre-computed in the **RTN** package. ## Load datasets This example provides the data required to generate an **MBR-class** object. The dataset **dt4rtn** is available from the **RTN** package and consists of an R list with 6 objects, 3 of which will be used in the subsequent analysis: (1) **gexp**, a named gene expression matrix with 120 samples (genes in rows, samples in cols), (2) **gexpIDs**, a data.frame with Probe-to-ENTREZ annotation, and (3) **tfs**, a named vector listing 148 transcription factors. These datasets were extracted, pre-processed and size-reduced from @Fletcher2013, and should be regarded as examples for demonstration purposes only. ```{r include=FALSE} library(RTNduals) data("dt4rtn", package = "RTN") gexp <- dt4rtn$gexp annot <- dt4rtn$gexpIDs tfs <- dt4rtn$tfs[c("IRF8","IRF1","PRDM1","E2F3","STAT4","LMO4","ZNF552")] ``` ```{r eval=FALSE} ##--- load package and dataset for demonstration library(RTNduals) data("dt4rtn", package = "RTN") gexp <- dt4rtn$gexp annot <- dt4rtn$gexpIDs tfs <- dt4rtn$tfs[c("IRF8","IRF1","PRDM1","E2F3","STAT4","LMO4","ZNF552")] ``` ## Preprocessing The **gexp** data matrix and the corresponding annotation are evaluated by the `mbrPreprocess` function in order to check the consistency of the input data. After this step it is generated a pre-processed **MBR-class** object whose status is updated to 'Preprocess [x]'. ```{r include=FALSE} ##--- generate a pre-processed MBR-class object rmbr <- mbrPreprocess(gexp=gexp, regulatoryElements=tfs, rowAnnotation=annot, verbose=FALSE) ``` ```{r eval=FALSE} ##--- generate a pre-processed MBR-class object rmbr <- mbrPreprocess(gexp=gexp, regulatoryElements=tfs, rowAnnotation=annot) ``` ## Run permutation analysis The `mbrPermutation` method inherits the same algorithm implemented in the **RTN** package. This function takes the pre-processed **MBR-class** object and returns a regulatory network inferred by mutual information analysis (with multiple hypothesis testing corrections). The results are included in the 'TNI' slot, which will be used in the subsequent steps of the pipeline. ```{r include=FALSE} ##--- compute a regulatory network ##--- (set nPermutations>=1000) rmbr <- mbrPermutation(rmbr, nPermutations=100, pValueCutoff=0.05, verbose=FALSE) ``` ```{r eval=FALSE} ##--- compute a regulatory network ##--- (set nPermutations>=1000) rmbr <- mbrPermutation(rmbr, nPermutations=100, pValueCutoff=0.05) ``` ## Run bootstrap analysis In additional to the permutation analysis, the stability of the regulatory network is assessed by bootstrapping using the `mbrBootstrap` function, which also inherits the same algorithm from the **RTN** package. The 'TNI' slot of the **MBR-class** object is updated with a consensus bootstrap network. ```{r include=FALSE} ##--- check stability of the regulatory network ##--- (set nBootstrap>=100) rmbr <- mbrBootstrap(rmbr, nBootstrap=10, verbose=FALSE) ``` ```{r eval=FALSE} ##--- check stability of the regulatory network ##--- (set nBootstrap>=100) rmbr <- mbrBootstrap(rmbr, nBootstrap=10) ``` ## Run DPI filter In a given regulatory network each target can be linked to multiple regulators as a result of both direct and indirect interactions. The Data Processing Inequality (DPI) algorithm [@Meyer2008] is used to remove the weakest interaction between two regulators and a common target. This step also inherits the algorithm that is implemented in the **RTN** package. ```{r include=FALSE} ##---apply DPI algorithm rmbr <- mbrDpiFilter(rmbr, verbose=FALSE) ``` ```{r eval=FALSE} ##---apply DPI algorithm rmbr <- mbrDpiFilter(rmbr) ``` ## Run association analysis between regulons The `mbrAssociation` method takes the transcriptional network computed in the previous steps and enumerates all triplets formed by two regulatores and one shared target. The method retrieves the mutual information between regulators and assesses the agreement between the predicted downstream effects using correlation analysis. A Fisher’s exact test is used to evaluate whether the number of shared targets is greater than expected by chance. ```{r include=FALSE} ##--- test associations for dual regulons rmbr <- mbrAssociation(rmbr, verbose=FALSE) ``` ```{r eval=FALSE} ##--- test associations for dual regulons rmbr <- mbrAssociation(rmbr) ``` A summary of the results can be accessed from 'rmbr' using the `mbrGet` function. ```{r eval=TRUE} ##--- check summary mbrGet(rmbr, what="summary") ``` ```{r eval=TRUE} ##--- get results overlap <- mbrGet(rmbr, what="dualsOverlap") correlation <- mbrGet(rmbr, what="dualsCorrelation") ``` Also, when prior evidences are available this method can add a 'supplementaryTable' regarding the association between regulators. The 'supplementaryTable' is a 'data.frame' listing unique relationships between any two regulators (please refer to the documentation for details on the input data format). # Session information ```{r label='Session information', eval=TRUE, echo=FALSE} sessionInfo() ``` # References