Name Mode Size
.github 040000
R 040000
data 040000
docs 040000
inst 040000
man 040000
tests 040000
vignettes 040000
.Rbuildignore 100644 1 kb
.gitignore 100644 1 kb 100644 1 kb
DESCRIPTION 100644 3 kb
LICENSE 100644 34 kb
NAMESPACE 100644 2 kb 100644 1 kb 100644 21 kb
_pkgdown.yml 100644 1 kb
[![master](]( [![devel](]( [![codecov](]( [![License: GPL v3](]( <a href=""><img src=""></a> [![tutorials](]( [![Netbooks](]( [![discussions](]( [![DOI](]( netZooR is tested on: (OS: Ubuntu + Macos) X (Language: R v4.2) ## Description netZooR is an R package to reconstruct, analyse, and plot biological networks. ## Features netZooR currently integrates: <details> <summary>PANDA</summary> * **PANDA** (Passing Attributes between Networks for Data Assimilation) [[Glass et al. 2013]]( PANDA is a method for estimating bipartite gene regulatory networks (GRNs) consisting of two types of nodes: transcription factors (TFs) and genes. An edge between TF $i$ and gene $j$ indicates that gene $j$ is regulated by TF $i$. The edge weight represents the strength of evidence for this regulatory relationship obtained by integrating three types of biological data: gene expression data, protein-protein interaction (PPI) data, and transcription factor binding motif (TFBM) data. PANDA is an iterative approach that begins with a seed GRN estimated from TFBMs and uses message passing between data types to refine the seed network to a final GRN that is consistent with the information contained in gene expression, PPI, and TFBM data. </details> <details> <summary>CONDOR</summary> * **CONDOR** (COmplex Network Description Of Regulators) [[Platig et al. 2016]]( CONDOR is a tool for community detection in bipartite networks. Many community detection methods for unipartite networks are based on the concept of maximizing a modularity metric that compares the weight of edges within communities to the weight of edges between communities, prioritizing community assignments with higher values of the former relative to the latter. CONDOR extends this concept to bipartite networks by optimizing a bipartite version of modularity defined by [[Barber (2007)]]( To enable bipartite community detection on large networks such gene regulatory networks, CONDOR uses a fast unipartite modularity maximization method on one of the two unipartite projections of the bipartite network. In Platig et al. (2016), CONDOR is applied to bipartite networks of single nucleotide polymorphisms (SNPs) and gene expression, where a network edge from a SNP node to a gene node is indicative of an association between the SNP and the gene expression level, commonly known as an expression quantitative trait locus (eQTL). Communities detected with CONDOR contained local hub nodes ("core SNPs") enriched for association with disease, suggesting that functional eQTL relationships are encoded at the community level. </details> <details> <summary>LIONESS</summary> * **LIONESS** (Linear Interpolation to Obtain Network Estimates for Single Samples) [[Kuijjer et al. 2019]]( LIONESS is a flexible method for single-sample network integration. The machinery behind LIONESS is a leave-one-out approach. To construct a single-sample network for sample $i$, a first network is estimated on the full dataset and a second network is estimated on the dataset with sample $i$ withheld. The single-sample network is then estimated based on the difference between these two networks. Any method that can be used to estimate a network can be used with LIONESS to estimate single-sample networks. Two common use cases are the use of LIONESS to generate single-sample GRNs based on PANDA and the use of LIONESS to generate single-sample Pearson correlation networks. </details> <details> <summary>ALPACA</summary> * **ALPACA** (ALtered Partitions Across Community Architectures) [[Padi and Quackenbush 2018]]( ALPACA is a method for differential network analysis that is based on a novel approach to comparison of network community structures. Comparisons of community structure have typically been accomplished by assessing which nodes switch community membership between networks ("community comparison") or by computing the edge weight differences by subtracting the adjacency matrices of two networks and then performing community detection on the resulting differential network ("edge subtraction"). Both these approaches have important limitations. Community comparison is subject to a resolution limit and cannot detect differences smaller than the average community size in a network. Edge subtraction transfers noise from both of the original networks to the differential network, leading to an imprecise estimator. Moreover, positive and negative edge differences cannot be distinguished in the subsequent community detection performed on the differential network. In contrast to community comparison and edge subtraction, ALPACA compares the community structure of two networks by optimizing a new metric: "differential modularity". In the ALPACA algorithm, one network is defined as the reference network and the second is defined as the perturbed network. The differential modularity metric measures the extent to which edges in a community in the perturbed network differ from those that would be expected by random chance according to a null distribution based on the reference network. Community structure of the perturbed network is determined by maximizing this differential modularity. The resulting communities are "differential modules" that show how the perturbed network differs from the reference network at the community level. </details> <details> <summary>SAMBAR</summary> * **SAMBAR** (Subtyping Agglomerated Mutations By Annotation Relations) [[Kuijjer et al.]]( SAMBAR is a tool for studying cancer subtypes based on patterns of somatic mutations in curated biological pathways. Rather than characterize cancer according to mutations at the gene level, SAMBAR agglomerates mutations within pathways to define a pathway mutation score. To avoid bias based on pathway representation, these pathway mutation scores correct for the number of genes in each pathway as well as the number of times each gene is represented in the universe of pathways. By taking a pathway rather than gene-by-gene lens, SAMBAR both de-sparsifies somatic mutation data and incorporates important prior biological knowledge. Kuijjer et al. (2018) demonstrate that SAMBAR is capable of outperforming other methods for cancer subtyping, producing subtypes with greater between-subtype distances; the authors use SAMBAR for a pan-cancer subtyping analysis that identifies four diverse pan-cancer subtypes linked to distinct molecular processes. </details> <details> <summary>MONSTER</summary> * **MONSTER** (Modeling Network State Transitions from Expression and Regulatory data) [[Schlauch et al.]]( MONSTER is a method for estimating transitions between network states by modeling the adjacency matrix of one state as a linear transformation of the adjacency matrix of another. Like LIONESS, MONSTER is a flexible method that does not require a particular type of network structure. MONSTER models the perturbation of an initial network A into a perturbed network B according to a matrix product B = AT. T is a transition matrix encoding the changes that map A to B. When A and B are gene regulatory networks, i.e., bipartite networks between TFs and genes, the MONSTER framework leads naturally to the definition of TF involvement as the sum of the off-diagonal weights for a transcription factor $i$ in the transition matrix T. This perspective enables MONSTER to identify differentially involved TFs that contribute to network transitions differently between different conditions. This dimension cannot be captured from a traditional differential expression analysis of TFs, which will not detect TFs that have the same concentration between conditions. </details> <details> <summary>OTTER</summary> * **OTTER** (Optimization to Estimate Regulation) [[Weighill et al.]]( OTTER is a GRN inference method based on the idea that observed biological data (PPI data and gene co-expression data) are projections of a bipartite GRN between TFs and genes. Specifically, PPI data represent the projection of the GRN onto the TF-TF space and gene co-expression data represent the projection of the GRN onto the gene-gene space. OTTER reframes the problem of GRN inference as a problem of relaxed graph matching and finds a GRN that has optimal agreement with the observed PPI and coexpression data. The OTTER objective function is tunable in two ways: first, one can prioritize matching the PPI data or the coexpression data more heavily depending on one's confidence in the data source; second, there is a regularization parameter that can be applied to induce sparsity on the estimated GRN. The OTTER objective function can be solved using spectral decomposition techniques and gradient descent; the latter is shown to be closely related to the PANDA message-passing approach (Glass et al. 2013). </details> <details> <summary>CRANE</summary> * **CRANE** (Constrained Random Alteration of Network Edges) [[Lim et al.]]( CRANE is a method for determining statistical significance of structural differences between networks. Analysis with CRANE is a four-phase process. The first step of CRANE is to estimate two networks: a reference network and a perturbed network. In the same spirit as LIONESS, CRANE is flexible: any network inference method (e.g., correlation, partial correlation, PANDA) can be used at this stage. In the second step, differential features are determined by comparing the reference and perturbed networks. Here, CRANE is again flexible: such differential features could arise from simple measures such as a comparison of node degree or centrality, or from more nuanced techniques such as differential module detection with ALPACA. Third, a large number of constrained random networks are developed based on the network structure of the reference network. By comparing each random network with the original reference network, a set of null differential measures is obtained. Fourth, the observed differential features from step two can be compared with the null distribution from step three to generate empirical p-values. A typical workflow for applying CRANE in NetZooR would involve fitting PANDA networks in step one and using ALPACA to estimate differential modules in step two. </details> <details> <summary>EGRET</summary> * **EGRET** (Estimating the Genetic Regulatory effects on TFs) [[Weighill et al.]]( EGRET incorporates genetic variants as a fourth data type in the PANDA message-passing framework, enabling the estimation of genotype-specific GRNs. Genetic variants can alter transcription factor binding by affecting the composition of motif sites on the DNA. Not every genetic variant has such an affect; EGRET incorporates only genetic variants which have (1) been shown to be associated with gene expression (expression quantitative trait loci, or eQTL), and (2) are predicted to affect transcription factor binding based on a tool called QBiC (Martin et al. 2019). This information is used in combination with TFBM predictions as input to the PANDA message-passing framework. The resulting EGRET network is a genotype-specific bipartite GRN that is similar to a PANDA network but incorporates the information contained by individual genetic variation. </details> <details> <summary>YARN</summary> * **YARN** (Yet Another RNa-seq package) [[Paulsson et al.]]( YARN is a package that combines quality control, gene filtering, and normalization steps to streamline the preprocessing of large-scale, multi-tissue gene expression data from resources such as the Genotype-Tissue Expression (GTEx) project. Among other steps, YARN uses principal coordinate analysis (PCoA) to determine if samples collected from different sites on the same tissue (for example, transverse and sigmoid colon) can be treated as "transcriptionally indistinguishable" and grouped together to increase power for downstream analyses. Paulsson et al. (2017) demonstrate the use of YARN to develop a pan-cancer RNA-seq dataset for 30,333 genes from 9435 samples across 38 tissues from the GTEx dataset. </details> netZooR also integrates additional functions to: * Source protein-protein interaction network from [STRINGdb]( based on a list of protein of interest. * Plot one PANDA network in [Cytoscape]( * Plot two differential PANDA networks in Cytoscape. ## Requirements, installation and basic configuration. - netZooR is compatible with R (>= 4.1), click [here]( for more installation details. - To use PANDA and LIONESS, there are two options: 1. Use `` and `` by invoking the respective Python implementations in [netZooPy](( Because the native R linear algebra libraries can be slow, this way is recommended for faster analysis. However, optimized parallel libraries can give reasonable run times (option ii). To invoke Python scripts, there are some requirements to meet before using netZooR: a) [**Python**]( (>= 3.5.0) installed; b) Python libraries [pandas](, [numpy](, and [scipy]( installed; c) Internet access as package `reticulate` will link the R wrapper to the Python scripts located [here]( for those two methods. 2. Use `panda()` and `lioness()` for the pure R implementations of PANDA and LIONESS. To speed up the run time, it is highly recommended to install an optimized linear algebra library, particularly for Ubunutu. Macos generally comes with optimized linear algebra libraries. You can check the `BLAS/LAPACK` fields in `sessionInfo()` in your R console. Detailed instructions can be found [here]( :warning: However, we found that Intel MKL linear algebra library with R 4.0.3 on Ubuntu 18.04 gave inconsistent results for the multiplication of large matrices and the results of PANDA were inconsistent. Therefore, Intel MKL is not currently recommended. - Most of plotting function can be realized by functions in [igraph](, which will be loaded with netZooR through `library(netZooR)`. Some plotting functions like `` and `` are able to plot interactive PANDA networks in [Cytoscape](, but installation of Cytoscape is required before using these plotting functions. Also, please make sure that Cytoscape is open when these functions are called. ### Installation #### Using devtools/remotes ```r # install.packages("devtools") # install netZooR pkg with vignettes, otherwise remove the "build_vignettes = TRUE" argument. devtools::install_github("netZoo/netZooR", build_vignettes = TRUE) library(netZooR) ``` You can use `remotes` instead of `devtools` because it is faster to install and run. The synatx is the following: ```r # install.packages("remotes") # install netZooR pkg with vignettes, otherwise remove the "build_vignettes = TRUE" argument. remotes::install_github("netZoo/netZooR", build_vignettes = TRUE) library(netZooR) ``` #### Using Bioconductor netZooR is also available through [Bioconductor]( ```r if (!requireNamespace("BiocManager", quietly = TRUE)) install.packages("BiocManager") # The following initializes usage of Bioc devel BiocManager::install(version='devel') BiocManager::install("netZooR") ``` For more details please refer to the [documentation website]( #### Using bioconda netZooR is also available through [Bioconda]( ```bash conda install bioconductor-netzoor ``` ### Python binding This package will invoke Python programming language in R environment through [reticulate]( package, by default setting there is no additional configuration needed. Configuring which version of Python to use , here in netZooR, Python 3.X is required. More details can be found [here]( ```r #check your Python configuration and the specific version of Python in use currently py_config() # reset to Python 3.X if necessary, like below: # use_python("/usr/local/bin/python3") ``` ## Help If you need help or if you have any question about netZoo, feel free to start with [discussions]( To report a bug, please open a new [issue]( ## Tutorials For more details please refer to the [documentation website]( Tutorials are available at the top navigation bar **Articles/** for basic usage and application cases. Or use `browseVignettes("netZooR")` after installing the package. Also check [netbooks]( to go through the tutorials on a Jupyter notebook cloud server. ## Contribution and Development Contributions are welcome! The contribution guide to netZooR can be found [here]( We follow the [Bioconductor code guidelines]( Before pushing a contribution, please run ```r library(BiocCheck) BiocCheck("packageDirOrTarball") ``` And resolve any warnings, notes, and errors before committing the code. After adding new features or optimizing a function in the package, please re-build the package and run `R CMD check .` in the terminal or follow the instructions below before doing the pull request to the devel branch. To run only the tests: ```r # install.packages('rcmdcheck') # setwd('path/to/netZooR/root') # Set the working directory to netZooR root rcmdcheck::rcmdcheck(args = c("--no-manual","--ignore-vignettes"), error_on = "error", build_args="--no-build-vignettes") ``` To rebuild vignettes, documentation, and tests: ```r # document the description of function # setwd('path/to/netZooR/root') # Set the working directory to netZooR root devtools::document() # build vignettes devtools::build_vignettes() # You can skip building the vignettes if you are not contributing a vignette # build documentation website pkgdown::build_site(examples=FALSE) # Install and build the package using devtools devtools::install() # To install the dependencies devtools::build() # To build the package #devtools::build(vignettes = FALSE) # You can skip building the vignettes if you are not contributing a vignette # CMD check, if passed all tests here, it means this package is ready to pull request to the devel branch. Otherwise, fix the bug before pulling request. devtools::check() #devtools::check(vignettes = FALSE) #You can skip building the vignettes if you are not contributing a vignette ``` The master branch on github should always be in good shape, so please to pull request to the **devel** branch. If the contribution is specific to pandaR, please contribute to its separate GitHub page by [pull request]( ## License The software is free and is licensed under the GNU General License v3.0, see the file [LICENSE](LICENSE) for details. ## Code of conduct Please note that this project is released with a [Contributor Code of Conduct]( By participating in this project you agree to abide by its terms.