OmnipathR: utility functions to work with OmniPath in R
27 October 2020
Abstract
This vignette describes how to use the OmnipathR package to retrieve information from the OmniPath database: https://omnipathdb.org/. In addition, it includes some utility functions to filter, analyse and visualize the data.Package
OmnipathR 2.0.0
Contents
1 Introduction
OmnipathR is an R package built to provide easy access to the data stored in the OmniPath webservice (Türei, Korcsmáros, and Saez-Rodriguez 2016):
The webservice implements a very simple REST style API. This package make requests by the HTTP protocol to retreive the data. Hence, fast Internet access is required for a proper use of OmnipathR.
1.1 Query types
OmnipathR can retrieve five different types of data:
- Interactions: protein-protein interactions organized in different datasets:
- omnipath: the OmniPath data as defined in the original publication (Türei, Korcsmáros, and Saez-Rodriguez 2016) and collected from different databases.
- pathwayextra: activity flow interactions without literature reference.
- kinaseextra: enzyme-substrate interactions without literature reference.
- ligrecextra: ligand-receptor interactions without literature reference.
- tfregulons: transcription factor (TF)-target interactions from DoRothEA (Garcia-Alonso et al. 2019).
- tf-miRNA: transcription factor-miRNA interactions
- miRNA-target: miRNA-mRNA interactions.
- lncRNA-mRNA: lncRNA-mRNA interactions.
Post-translational modifications (PTMs): It provides enzyme-substrate reactions in a very similar way to the aforementioned interactions. Some of the biological databases related to PTMs integrated in OmniPath are Phospho.ELM (Dinkel et al. 2010) and PhosphoSitePlus [Hornbeck et al. (2014)}.
Complexes: it provides access to a comprehensive database of more than 22000 protein complexes. This data comes from different resources such as: CORUM (Giurgiu et al. 2018) or Hu.map (Drew et al. 2017).
Annotations: it provides a large variety of data regarding different annotations about proteins and complexes. These data come from dozens of databases covering different topics such as: The Topology Data Bank of Transmembrane Proteins (TOPDB) (Dobson et al. 2014) or ExoCarta (Keerthikumar et al. 2016), a database collecting the proteins that were identified in exosomes in multiple organisms.
Intercell: it provides information on the roles in inter-cellular signaling. For instance. if a protein is a ligand, a receptor, an extracellular matrix (ECM) component, etc. The data does not come from original sources but combined from several databases by us. The source databases, such as CellPhoneDB (Vento-Tormo et al. 2018) or Receptome (Ben-Shlomo et al. 2003), are also referred for each reacord.
Figure 1 shows an overview of the resources featured in OmniPath. For more detailed information about the original data sources integrated in Omnipath, please visit:
Figure 1: Overview of the resources featured in OmniPath
Causal resources (including activity-flow and enzyme-substrate resources) can provide direction (*) or sign and direction (+) of interactions.
1.2 Mouse and rat
Excluding the miRNA interactions, all interactions and PTMs are available for human, mouse and rat. The rodent data has been translated from human using the NCBI Homologene database. Many human proteins do not have known homolog in rodents, hence rodent datasets are smaller than their human counterparts.
In case you work with mouse omics data you might do better to translate your dataset to human (for example using the pypath.homology module, https://github.com/saezlab/pypath/) and use human interaction data.
2 Installation of the OmnipathR package
First of all, you need a current version of R. OmnipathR is a freely available package deposited on Bioconductor and GitHub. You can install it by running the following commands on an R console:
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("OmnipathR")We also load here the required packages to run the code in this vignette.
library(OmnipathR)
library(tidyr)
library(dnet)
library(gprofiler2)3 Usage Examples
In the following paragraphs, we provide some examples to describe how to use the OmnipathR package to retrieve different types of information from Omnipath webserver. In addition, we play around with the data aiming at obtaining some biological relevant information.
Noteworthy, the sections complexes, annotations and intercell are linked. We explore the annotations and roles in inter-cellular communications of the proteins involved in a given complex. This basic example shows the usefulness of integrating the information available in the different Omnipath resources.
3.1 Interactions
Proteins interact among them and with other biological molecules to perform cellular functions. Proteins also participates in pathways, linked series of reactions occurring inter/intra cells to transform products or to transmit signals inducing specific cellular responses. Protein interactions are therefore a very valuable source of information to understand cellular functioning.
We here download the original OmniPath human interactions (Türei, Korcsmáros, and Saez-Rodriguez 2016). To do so, we first check the different source databases and select some of them. Then, we print some of the downloaded interactions (“+” means activation, “-” means inhibition and “?” means undirected interactions or inconclusive data).
## We check some of the different interaction databases
get_interaction_resources()## [1] "ABS" "ACSN"
## [3] "ACSN_SignaLink3" "ARACNe-GTEx_DoRothEA"
## [5] "ARN" "Adhesome"
## [7] "AlzPathway" "BEL-Large-Corpus_ProtMapper"
## [9] "Baccin2019" "BioGRID"
## [11] "BioGRID_ICELLNET" "CA1"
## [13] "CancerCellMap" "CellPhoneDB"
## [15] "CellPhoneDB_ICELLNET" "DEPOD"
## [17] "DIP" "DOMINO"
## [19] "DeathDomain" "Dinarello2013_ICELLNET"
## [21] "DoRothEA" "DoRothEA-reviews_DoRothEA"
## [23] "ELM" "EMBRACE"
## [25] "ENCODE-distal" "ENCODE-proximal"
## [27] "ENCODE_tf-mirna" "FANTOM4_DoRothEA"
## [29] "Fantom5_LRdb" "GO-lig-rec_ICELLNET"
## [31] "Guide2Pharma" "Guide2Pharma_CellPhoneDB"
## [33] "Guide2Pharma_ICELLNET" "Guide2Pharma_LRdb"
## [35] "HOCOMOCO_DoRothEA" "HPMR"
## [37] "HPMR_ICELLNET" "HPMR_LRdb"
## [39] "HPRD" "HPRD-phos"
## [41] "HPRD_KEA" "HPRD_LRdb"
## [43] "HPRD_MIMP" "HTRIdb"
## [45] "HTRIdb_DoRothEA" "HuRI"
## [47] "I2D_CellPhoneDB" "ICELLNET"
## [49] "IMEx_CellPhoneDB" "InnateDB"
## [51] "InnateDB-All_CellPhoneDB" "InnateDB_CellPhoneDB"
## [53] "InnateDB_ICELLNET" "InnateDB_SignaLink3"
## [55] "IntAct" "IntAct_CellPhoneDB"
## [57] "IntAct_DoRothEA" "JASPAR_DoRothEA"
## [59] "KEA" "KEGG-MEDICUS"
## [61] "Kinexus_KEA" "Kirouac2010"
## [63] "Kirouac2010_ICELLNET" "LMPID"
## [65] "LRdb" "Li2012"
## [67] "Lit-BM-17" "LncRNADisease"
## [69] "MIMP" "MINT_CellPhoneDB"
## [71] "MPPI" "Macrophage"
## [73] "Macrophage_ICELLNET" "MatrixDB"
## [75] "MatrixDB_CellPhoneDB" "NCI-PID_ProtMapper"
## [77] "NFIRegulomeDB_DoRothEA" "NRF2ome"
## [79] "NetPath" "NetworKIN_KEA"
## [81] "ORegAnno" "ORegAnno_DoRothEA"
## [83] "PAZAR" "PAZAR_DoRothEA"
## [85] "PhosphoNetworks" "PhosphoPoint"
## [87] "PhosphoSite" "PhosphoSite_KEA"
## [89] "PhosphoSite_MIMP" "PhosphoSite_ProtMapper"
## [91] "PhosphoSite_noref" "ProtMapper"
## [93] "REACH_ProtMapper" "RLIMS-P_ProtMapper"
## [95] "Ramilowski2015" "Ramilowski2015_Baccin2019"
## [97] "Ramilowski2015_ICELLNET" "ReMap_DoRothEA"
## [99] "Reactome_ICELLNET" "Reactome_LRdb"
## [101] "Reactome_ProtMapper" "Reactome_SignaLink3"
## [103] "RegNetwork_DoRothEA" "SIGNOR"
## [105] "SIGNOR_ICELLNET" "SIGNOR_ProtMapper"
## [107] "SPIKE" "SPIKE_ICELLNET"
## [109] "STRING_ICELLNET" "SignaLink3"
## [111] "SignaLink3_ICELLNET" "Sparser_ProtMapper"
## [113] "TCRcuration_SignaLink3" "TFactS_DoRothEA"
## [115] "TFe_DoRothEA" "TRED_DoRothEA"
## [117] "TRIP" "TRRD_DoRothEA"
## [119] "TRRUST_DoRothEA" "TransmiR"
## [121] "UniProt_CellPhoneDB" "UniProt_LRdb"
## [123] "Wang" "dbPTM"
## [125] "iPTMnet" "iTALK"
## [127] "lncrnadb" "miR2Disease"
## [129] "miRDeathDB" "miRTarBase"
## [131] "miRecords" "ncRDeathDB"
## [133] "phosphoELM" "phosphoELM_KEA"
## [135] "phosphoELM_MIMP"## The interactions are stored into a data frame.
interactions <-
import_omnipath_interactions(resources=c("SignaLink3","PhosphoSite",
"SIGNOR"))## Downloaded 14001 interactions.## We visualize the first interactions in the data frame.
print_interactions(head(interactions))## source interaction target n_resources n_references
## 6 TRPM7 (Q96QT4) ==( + )==> ANXA1 (P04083) 10 9
## 3 SRC (P12931) ==( + )==> TRPV1 (Q8NER1) 5 6
## 2 PRKG1 (Q13976) ==( - )==> TRPC6 (Q9Y210) 4 5
## 1 PRKG1 (Q13976) ==( - )==> TRPC3 (Q13507) 8 2
## 4 PTPN1 (P18031) ==( - )==> TRPV6 (Q9H1D0) 6 2
## 5 RACK1 (P63244) ==( - )==> TRPM6 (Q9BX84) 2 13.1.1 Protein-protein interaction networks
Protein-protein interactions are usually converted into networks. Describing protein interactions as networks not only provides a convenient format for visualization, but also allows applying graph theory methods to mine the biological information they contain.
We convert here our set of interactions to a network/graph (igraphobject). Then, we apply two very common approaches to extract information from a biological network:
- Shortest Paths: finding a path between two nodes (proteins) going
through the minimum number of edges. This can be very useful to track
consecutive reactions within a given pathway. We display below the shortest
path between two given proteins and all the possible shortests paths between
two other proteins. It is to note that the functions
print_path\_esandprint_path\_vsdisplay very similar results, but the first one takes as an input an edge sequence and the second one a node sequence.
## We transform the interactions data frame into a graph
OPI_g <- interaction_graph(interactions = interactions)
## Find and print shortest paths on the directed network between proteins
## of interest:
print_path_es(shortest_paths(OPI_g,from = "TYRO3",to = "STAT3",
output = 'epath')$epath[[1]],OPI_g)## source interaction target n_resources n_references
## 1 TYRO3 (Q06418) ==( + )==> GRB2 (P62993) 2 1
## 2 GRB2 (P62993) ==( + )==> EGFR (P00533) 11 57
## 3 EGFR (P00533) ==( + )==> STAT3 (P40763) 12 24## Find and print all shortest paths between proteins of interest:
print_path_vs(all_shortest_paths(OPI_g,from = "DYRK2",
to = "MAPKAPK2")$res,OPI_g)## Pathway 1: DYRK2 -> TBK1 -> AKT3 -> PEA15 -> MAPK3 -> MAPKAPK2## Pathway 2: DYRK2 -> TBK1 -> AKT2 -> PEA15 -> MAPK3 -> MAPKAPK2## Pathway 3: DYRK2 -> TBK1 -> AKT1 -> PEA15 -> MAPK3 -> MAPKAPK2## Pathway 4: DYRK2 -> TBK1 -> AKT3 -> PPP1CA -> MAPK3 -> MAPKAPK2## Pathway 5: DYRK2 -> TBK1 -> AKT2 -> PPP1CA -> MAPK3 -> MAPKAPK2## Pathway 6: DYRK2 -> TBK1 -> AKT1 -> PPP1CA -> MAPK3 -> MAPKAPK2## Pathway 7: DYRK2 -> TP53 -> RPS6KA5 -> CDC25A -> MAPK3 -> MAPKAPK2## Pathway 8: DYRK2 -> TP53 -> RPS6KA4 -> CDC25A -> MAPK3 -> MAPKAPK2## Pathway 9: DYRK2 -> TP53 -> RPS6KA3 -> CDC25A -> MAPK3 -> MAPKAPK2## Pathway 10: DYRK2 -> TP53 -> RPS6KA2 -> CDC25A -> MAPK3 -> MAPKAPK2## Pathway 11: DYRK2 -> TP53 -> RPS6KA1 -> CDC25A -> MAPK3 -> MAPKAPK2## Pathway 12: DYRK2 -> TBK1 -> AKT3 -> PEA15 -> MAPK1 -> MAPKAPK2## Pathway 13: DYRK2 -> TBK1 -> AKT2 -> PEA15 -> MAPK1 -> MAPKAPK2## Pathway 14: DYRK2 -> TBK1 -> AKT1 -> PEA15 -> MAPK1 -> MAPKAPK2## Pathway 15: DYRK2 -> TBK1 -> AKT3 -> PPP1CA -> MAPK1 -> MAPKAPK2## Pathway 16: DYRK2 -> TBK1 -> AKT2 -> PPP1CA -> MAPK1 -> MAPKAPK2## Pathway 17: DYRK2 -> TBK1 -> AKT1 -> PPP1CA -> MAPK1 -> MAPKAPK2## Pathway 18: DYRK2 -> TP53 -> RPS6KA3 -> DAPK1 -> MAPK1 -> MAPKAPK2## Pathway 19: DYRK2 -> TP53 -> RPS6KA5 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 20: DYRK2 -> TP53 -> RPS6KA4 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 21: DYRK2 -> TP53 -> RPS6KA3 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 22: DYRK2 -> TP53 -> RPS6KA2 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 23: DYRK2 -> TP53 -> RPS6KA1 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 24: DYRK2 -> TBK1 -> AKT3 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 25: DYRK2 -> TBK1 -> AKT2 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 26: DYRK2 -> TBK1 -> AKT1 -> GSK3B -> MAPK14 -> MAPKAPK2## Pathway 27: DYRK2 -> TBK1 -> AKT3 -> MAP2K4 -> MAPK14 -> MAPKAPK2## Pathway 28: DYRK2 -> TBK1 -> AKT2 -> MAP2K4 -> MAPK14 -> MAPKAPK2## Pathway 29: DYRK2 -> TBK1 -> AKT1 -> MAP2K4 -> MAPK14 -> MAPKAPK2## Pathway 30: DYRK2 -> TBK1 -> AKT3 -> MAP3K5 -> MAPK14 -> MAPKAPK2## Pathway 31: DYRK2 -> TBK1 -> AKT2 -> MAP3K5 -> MAPK14 -> MAPKAPK2## Pathway 32: DYRK2 -> TBK1 -> AKT1 -> MAP3K5 -> MAPK14 -> MAPKAPK2- Clustering: grouping nodes (proteins) in such a way that nodes belonging to the same group (called cluster) are more connected in the network to each other than to those in other groups (clusters). Since proteins interact to perform their functions, proteins within the same cluster are likely to be implicated in similar biological tasks. Figure ?? shows the subgraph containing the proteins and interactions of a specifc protein, ERBB2 The igraph package contains functions to apply sevaral different cluster methods on graphs (visit https://igraph.org/r/doc/ for detailed information.)
## We apply a clustering algorithm (Louvain) to group proteins in
## our network. We apply here Louvain which is fast but can only run
## on undirected graphs. Other clustering algorithms can deal with
## directed networks but with longer computational times,
## such as cluster_edge_betweenness. These cluster methods are directly
## available in the igraph package.
OPI_g_undirected <- as.undirected(OPI_g, mode=c("mutual"))
OPI_g_undirected <- simplify(OPI_g_undirected)
cl_results <- cluster_fast_greedy(OPI_g_undirected)
## We extract the cluster where a protein of interest is contained
cluster_id <- cl_results$membership[which(cl_results$names == "ERBB2")]
module_graph <- induced_subgraph(OPI_g_undirected,
V(OPI_g)$name[which(cl_results$membership == cluster_id)]){r fig2, fig.width=10, fig.height=5, dpi=300, echo = FALSE, fig.cap="ERBB2 associated cluser. Subnetwork extracted from the interactions graph representing the cluster where we can find the gene *ERBB2* (yellow node)"} ## We print that cluster with its interactions. par(mar=c(0.1,0.1,0.1,0.1)) plot(module_graph, vertex.label.color="black",vertex.frame.color="#ffffff", vertex.size= 15, edge.curved=.2, vertex.color = ifelse(igraph::V(module_graph)$name == "ERBB2","yellow", "#00CCFF"), edge.color="blue",edge.width=0.8)
3.2 Other interaction datasets
We used above the interactions from the dataset described in the original OmniPath publication (Türei, Korcsmáros, and Saez-Rodriguez 2016). In this section, we provide examples on how to retry and deal with interactions from the remaining datasets. The same functions can been applied to every interaction dataset.
3.2.1 Pathway Extra
In the first example, we are going to get the interactions from the pathwayextra dataset, which contains activity flow interactions without literature reference. We are going to focus on the mouse interactions for a given gene in this particular case.
## We query and store the interactions into a dataframe
interactions <-
import_pathwayextra_interactions(resources=c("BioGRID","STRING"),
organism = 10090)## Warning in omnipath_check_param(param): The following resources are not
## available: STRING. Check the resource names for spelling mistakes.## Downloaded 995 interactions.## We select all the interactions in which Amfr gene is involved
interactions_Amfr <- dplyr::filter(interactions, source_genesymbol == "Amfr" |
target_genesymbol == "Amfr")
## We print these interactions:
print_interactions(interactions_Amfr)## source interaction target n_resources n_references
## 1 Amfr (Q9R049) ==( + )==> Vcp (Q01853) 6 203.2.2 Kinase Extra
Next, we download the interactions from the kinaseextra dataset, which contains enzyme-substrate interactions without literature reference. We are going to focus on rat reactions targeting a particular gene.
## We query and store the interactions into a dataframe
interactions <-
import_kinaseextra_interactions(resources=c("PhosphoPoint",
"PhosphoSite"), organism = 10116)## Downloaded 3727 interactions.## We select the interactions in which Dpysl2 gene is a target
interactions_TargetDpysl2 <- dplyr::filter(interactions,
target_genesymbol == "Dpysl2")
## We print these interactions:
print_interactions(interactions_TargetDpysl2)## source interaction target n_resources n_references
## 1 Gsk3b (P18266) ==(+/-)==> Dpysl2 (P47942) 11 32
## 4 Cdk5 (Q03114) ==( + )==> Dpysl2 (P47942) 5 26
## 2 Rock2 (Q62868) ==( + )==> Dpysl2 (P47942) 10 6
## 5 Rock1 (Q63644) ==( ? )==> Dpysl2 (P47942) 6 2
## 3 Fer (P09760) ==( ? )==> Dpysl2 (P47942) 2 23.2.3 Ligand-receptor Extra
In the following example we are going to work with the ligrecextra dataset, which contains ligand-receptor interactions without literature reference. Our goal is to find the potential receptors associated to a given ligand, CDH1 (Figure ??).
## We query and store the interactions into a dataframe
interactions <- import_ligrecextra_interactions(resources=c("iTALK",
"Baccin2019"), organism=9606)## Downloaded 2852 interactions.## Receptors of the CDH1 ligand.
interactions_ADM2 <- dplyr::filter(interactions, source_genesymbol == "ADM2")
## We transform the interactions data frame into a graph
OPI_g <- interaction_graph(interactions = interactions_ADM2)
## We induce a network with these genes
Induced_Network <- dNetInduce(g=OPI_g,
nodes_query=as.character( V(OPI_g)$name), knn=0,
remove.loops=FALSE, largest.comp=FALSE){r fig3, dpi=300, echo = FALSE, fig.cap="Ligand-receptor interactions for the ADM2 ligand."} ## We print the induced network par(mar=c(0.1,0.1,0.1,0.1)) plot(Induced_Network, vertex.label.color="black", vertex.frame.color="#ffffff",vertex.size= 20, edge.curved=.2, vertex.color = ifelse(igraph::V(Induced_Network)$name %in% c("ADM2"), "yellow","#00CCFF"), edge.color="blue",edge.width=0.8)
3.2.4 DoRothEA Regulons
Another very interesting interaction dataset also available in OmniPath is DoRothEA (Garcia-Alonso et al. 2019). It contains transcription factor (TF)-target interactions with confidence score, ranging from A-E, being A the most confident interactions. In the code chunk shown below, we select and print the most confident interactions for a given TF.
## We query and store the interactions into a dataframe
interactions <- import_dorothea_interactions(
resources=c("DoRothEA"),
dorothea_levels = 'A',
organism=9606
)## Downloaded 6245 interactions.## We select the most confident interactions for a given TF and we print
## the interactions to check the way it regulates its different targets
interactions_A_GLI1 <- dplyr::filter(interactions, dorothea_level=="A",
source_genesymbol == "GLI1")
print_interactions(interactions_A_GLI1)## source interaction target n_resources n_references
## 5 GLI1 (P08151) ==( + )==> PTCH1 (Q13635) 1 0
## 1 GLI1 (P08151) ==( + )==> BCL2 (P10415) 0 0
## 2 GLI1 (P08151) ==( + )==> CCND2 (P30279) 0 0
## 3 GLI1 (P08151) ==( - )==> EGR2 (P11161) 0 0
## 4 GLI1 (P08151) ==( + )==> IGFBP6 (P24592) 0 0
## 6 GLI1 (P08151) ==( + )==> SFRP1 (Q8N474) 0 0
## 7 GLI1 (P08151) ==( - )==> SLIT2 (O94813) 0 03.2.5 miRNA-target dataset
The last dataset describing interactions is mirnatarget. It stores miRNA-mRNA and TF-miRNA interactions. These interactions are only available for human so far. We next select the miRNA interacting with the TF selected in the previous code chunk, GLI1. The main function of miRNAs seems to be related with gene regulation. It is therefore interesting to see how some miRNA can regulate the expression of a TF which in turn regulates the expression of other genes. Figure ?? shows a schematic network of the miRNA targeting GLI1 and the genes regulated by this TF.
## We query and store the interactions into a dataframe
interactions <-
import_mirnatarget_interactions(resources=c("miRTarBase","miRecords"))## Downloaded 5962 interactions.## We select the interactions where a miRNA is interacting with the TF
## used in the previous code chunk and we print these interactions.
interactions_miRNA_GLI1 <-
dplyr::filter(interactions, target_genesymbol == "GLI1")
print_interactions(interactions_miRNA_GLI1)## source interaction target n_resources
## 2 hsa-miR-324-5p (MIMAT0000761) ==( ? )==> GLI1 (P08151) 3
## 1 hsa-miR-125b-5p (MIMAT0000423) ==( ? )==> GLI1 (P08151) 2
## 3 hsa-miR-326 (MIMAT0000756) ==( ? )==> GLI1 (P08151) 2
## 4 hsa-miR-202-3p (MIMAT0002811) ==( ? )==> GLI1 (P08151) 1
## 5 hsa-miR-133b (MIMAT0000770) ==( ? )==> GLI1 (P08151) 1
## n_references
## 2 2
## 1 1
## 3 1
## 4 1
## 5 1## We transform the previous selections to graphs (igraph objects)
OPI_g_1 <-interaction_graph(interactions = interactions_A_GLI1)
OPI_g_2 <-interaction_graph(interactions = interactions_miRNA_GLI1){r fig4, dpi=300, echo = FALSE, fig.cap="miRNA-TF-target network. Schematic network of the miRNA (red square nodes) targeting \textit{GLI1} (yellow node) and the genes regulated by this TF (blue round nodes)."} ## We print the union of both previous graphs par(mar=c(0.1,0.1,0.1,0.1)) plot(OPI_g_1 %u% OPI_g_2, vertex.label.color="black", vertex.frame.color="#ffffff",vertex.size= 20, edge.curved=.25, vertex.color = ifelse(grepl("miR",igraph::V(OPI_g_1 %u% OPI_g_2)$name), "red",ifelse(igraph::V(OPI_g_1 %u% OPI_g_2)$name == "GLI1", "yellow","#00CCFF")), edge.color="blue", vertex.shape = ifelse(grepl("miR",igraph::V(OPI_g_1 %u% OPI_g_2)$name), "vrectangle","circle"),edge.width=0.8)
3.3 Post-translational modifications (PTMs)
Another query type available is PTMs which provides enzyme-substrate reactions in a very similar way to the aforementioned interactions. PTMs refer generally to enzymatic modification of proteins after their synthesis in the ribosomes. PTMs can be highly context-specific and they play a main role in the activation/inhibition of biological pathways.
In the next code chunk, we download the PTMs for human. We first check the different available source databases, even though we do not perform any filter. Then, we select and print the reactions involving a specific enzyme-substrate pair. Those reactions lack information about activation or inhibition. To obtain that information, we match the data with OmniPath interactions. Finally, we show that it is also possible to build a graph using this information, and to retrieve PTMs from mouse or rat.
## We check the different PTMs databases
get_enzsub_resources()## [1] "BEL-Large-Corpus_ProtMapper" "DEPOD"
## [3] "HPRD" "HPRD_MIMP"
## [5] "KEA" "Li2012"
## [7] "MIMP" "NCI-PID_ProtMapper"
## [9] "PhosphoNetworks" "PhosphoSite"
## [11] "PhosphoSite_MIMP" "PhosphoSite_ProtMapper"
## [13] "ProtMapper" "REACH_ProtMapper"
## [15] "RLIMS-P_ProtMapper" "Reactome_ProtMapper"
## [17] "SIGNOR" "SIGNOR_ProtMapper"
## [19] "Sparser_ProtMapper" "dbPTM"
## [21] "phosphoELM" "phosphoELM_MIMP"## We query and store the ptms into a dataframe. No filtering by
## databases in this case.
ptms <- import_omnipath_enzsub()## Downloaded 39201 enzyme-substrate relationships.## We can select and print the reactions between a specific kinase and
## a specific substrate
print_interactions(dplyr::filter(ptms,enzyme_genesymbol=="MAP2K1",
substrate_genesymbol=="MAPK3"))## enzyme interaction substrate modification n_resources
## 1 MAP2K1 (Q02750) ====> MAPK3_Y204 (P27361) phosphorylation 8
## 2 MAP2K1 (Q02750) ====> MAPK3_T202 (P27361) phosphorylation 8
## 3 MAP2K1 (Q02750) ====> MAPK3_Y210 (P27361) phosphorylation 2
## 4 MAP2K1 (Q02750) ====> MAPK3_T207 (P27361) phosphorylation 2
## 5 MAP2K1 (Q02750) ====> MAPK3_T80 (P27361) phosphorylation 1
## 6 MAP2K1 (Q02750) ====> MAPK3_Y222 (P27361) phosphorylation 1## In the previous results, we can see that ptms does not contain sign
## (activation/inhibition). We can generate this information based on the
## protein-protein OmniPath interaction dataset.
interactions <- import_omnipath_interactions()## Downloaded 41419 interactions.ptms <- get_signed_ptms(ptms, interactions)
## We select again the same kinase and substrate. Now we have information
## about inhibition or activation when we print the ptms
print_interactions(dplyr::filter(ptms,enzyme_genesymbol=="MAP2K1",
substrate_genesymbol=="MAPK3"))## enzyme interaction substrate modification n_resources
## 5 MAP2K1 (Q02750) ==( + )==> MAPK3_Y204 (P27361) phosphorylation 8
## 1 MAP2K1 (Q02750) ==( + )==> MAPK3_T202 (P27361) phosphorylation 8
## 2 MAP2K1 (Q02750) ==( + )==> MAPK3_T207 (P27361) phosphorylation 2
## 4 MAP2K1 (Q02750) ==( + )==> MAPK3_Y210 (P27361) phosphorylation 2
## 3 MAP2K1 (Q02750) ==( + )==> MAPK3_Y222 (P27361) phosphorylation 1
## 6 MAP2K1 (Q02750) ==( + )==> MAPK3_T80 (P27361) phosphorylation 1## We can also transform the ptms into a graph.
ptms_g <- ptms_graph(ptms = ptms)
## We download PTMs for mouse
ptms <- import_omnipath_enzsub(resources=c("PhosphoSite", "SIGNOR"),
organism=10090)## Downloaded 13866 enzyme-substrate relationships.3.4 Complexes
Some studies indicate that around 80% of the human proteins operate in complexes, and many proteins belong to several different complexes (Berggård, Linse, and James 2007). These complexes play critical roles in a large variety of biological processes. Some well-known examples are the proteasome and the ribosome. Thus, the description of the full set of protein complexes functioning in cells is essential to improve our understanding of biological processes.
The complexes query provides access to more than 20000 protein complexes. This comprehensive database has been created by integrating different resources. We now download these molecular complexes filtering by some of the source databases. We check the complexes where a couple of specific genes participate. First, we look for the complexes where any of these two genes participate. We then identify the complex where these two genes are jointly involved. Finally, we perform an enrichment analysis with the genes taking part in that complex. You should keep an eye on this complex since it will be used again in the forthcoming sections.
## We check the different complexes databases
get_complex_resources()## [1] "CFinder" "CORUM" "CellPhoneDB" "Compleat"
## [5] "ComplexPortal" "Guide2Pharma" "HPMR" "Havugimana2012"
## [9] "ICELLNET" "KEGG-MEDICUS" "NetworkBlast" "PDB"
## [13] "SIGNOR" "Signor" "hu.MAP"## We query and store complexes from some sources into a dataframe.
complexes <- import_omnipath_complexes(resources=c("CORUM", "hu.MAP"))## Downloaded 7215 protein complexes.## We check all the molecular complexes where a set of genes participate
query_genes <- c("WRN","PARP1")
## Complexes where any of the input genes participate
complexes_query_genes_any <- unique(get_complex_genes(complexes,query_genes,
total_match=FALSE))
## We print the components of the different selected components
head(complexes_query_genes_any$components_genesymbols,6)## [1] "NCAPD2_NCAPG_NCAPH_PARP1_SMC2_SMC4_XRCC1"
## [2] "CCNA2_CDK2_LIG1_PARP1_POLA1_POLD1_POLE_RFC1_RFC2_RPA1_RPA2_RPA3_TOP1"
## [3] "CCNA2_CCNB1_CDK1_PARP1_POLA1_POLD1_POLE_RFC1_RFC2_RPA1_RPA2_RPA3_TOP1"
## [4] "MRE11_PARP1_RAD50_TERF2_TERF2IP_XRCC5_XRCC6"
## [5] "TERF2_WRN"
## [6] "CALR_DHX30_H2AFX_HIST3H2BB_HSPA5_NPM1_PARP1"## Complexes where all the input genes participate jointly
complexes_query_genes_join <- unique(get_complex_genes(complexes,query_genes,
total_match=TRUE))
## We print the components of the different selected components
complexes_query_genes_join$components_genesymbols## [1] "PARP1_WRN_XRCC5_XRCC6"genes_complex <-
unlist(strsplit(complexes_query_genes_join$components_genesymbols, "_"))
## We can perform an enrichment analyses with the genes in the complex
EnrichmentResults <- gost(genes_complex, significant = TRUE,
user_threshold = 0.001, correction_method = c("fdr"),
sources=c("GO:BP","GO:CC","GO:MF"))
## We show the most significant results
EnrichmentResults$result %>%
dplyr::select(term_id, source, term_name,p_value) %>%
dplyr::top_n(5,-p_value)## term_id source term_name p_value
## 1 GO:0010332 GO:BP response to gamma radiation 5.669890e-08
## 2 GO:0032392 GO:BP DNA geometric change 3.671620e-07
## 3 GO:0032508 GO:BP DNA duplex unwinding 3.671620e-07
## 4 GO:0010212 GO:BP response to ionizing radiation 6.700327e-07
## 5 GO:0000781 GO:CC chromosome, telomeric region 3.392756e-073.5 Annotations
Biological annotations are statements, usually traceable and curated, about the different features of a biological entity. At the genetic level, annotations describe the biological function, the subcellular situation, the DNA location and many other related properties of a particular gene or its gene products.
The annotations query provides a large variety of data about proteins and complexes. These data come from dozens of databases and each kind of annotation record contains different fields. Because of this, here we have a record_id field which is unique within the records of each database. Each row contains one key value pair and you need to use the record_id to connect the related key-value pairs (see examples below).
Now, we focus in the annotations of the complex studied in the previous section. We first inspect the different available databases in the omnipath webserver. Then, we download the annotations for our complex itself as a biological entity. We find annotations related to the nucleus and transcriptional control, which is in agreement with the enrichment analysis results of its individual components.
## We check the different annotation databases
get_annotation_resources()## [1] "Adhesome" "Almen2009" "Baccin2019"
## [4] "CORUM_Funcat" "CORUM_GO" "CSPA"
## [7] "CSPA_celltype" "CancerGeneCensus" "CancerSEA"
## [10] "CellCellInteractions" "CellPhoneDB" "CellPhoneDB_complex"
## [13] "ComPPI" "DGIdb" "DisGeNet"
## [16] "EMBRACE" "Exocarta" "GO_Intercell"
## [19] "GPCRdb" "Guide2Pharma" "HGNC"
## [22] "HPA_secretome" "HPA_subcellular" "HPA_tissue"
## [25] "HPMR" "HPMR_complex" "ICELLNET"
## [28] "ICELLNET_complex" "IntOGen" "Integrins"
## [31] "KEGG-PC" "Kirouac2010" "LOCATE"
## [34] "LRdb" "MCAM" "MSigDB"
## [37] "Matrisome" "MatrixDB" "Membranome"
## [40] "NetPath" "OPM" "Phobius"
## [43] "Phosphatome" "Ramilowski2015" "Ramilowski_location"
## [46] "SIGNOR" "SignaLink_function" "SignaLink_pathway"
## [49] "Surfaceome" "TCDB" "TFcensus"
## [52] "TopDB" "UniProt_family" "UniProt_keyword"
## [55] "UniProt_location" "UniProt_tissue" "UniProt_topology"
## [58] "Vesiclepedia" "Zhong2015" "iTALK"
## [61] "kinase.com"## We can further investigate the features of the complex selected
## in the previous section.
## We first get the annotations of the complex itself:
annotations <- import_omnipath_annotations(proteins=paste0("COMPLEX:",
complexes_query_genes_join$components_genesymbols))## Downloaded 42 annotation records.head(dplyr::select(annotations,source,label,value),10)## source label value
## 1 MSigDB collection reactome_pathways
## 2 MSigDB geneset REACTOME_DNA_REPAIR
## 3 MSigDB collection chemical_and_genetic_perturbations
## 4 MSigDB geneset KAUFFMANN_DNA_REPAIR_GENES
## 5 MSigDB collection chemical_and_genetic_perturbations
## 6 MSigDB geneset PUJANA_CHEK2_PCC_NETWORK
## 7 MSigDB collection chemical_and_genetic_perturbations
## 8 MSigDB geneset COLLIS_PRKDC_SUBSTRATES
## 9 MSigDB collection reactome_pathways
## 10 MSigDB geneset REACTOME_DNA_DOUBLE_STRAND_BREAK_REPAIRAfterwards, we explore the annotations of the individual components of the complex in some databases. We check the pathways where these proteins are involved. Once again, we also find many nucleus related annotations when checking their cellular location.
## Then, we explore some annotations of its individual components
## Pathways where the proteins belong:
annotations <- import_omnipath_annotations(proteins=genes_complex,
resources=c("NetPath"))## Downloaded 7 annotation records.dplyr::select(annotations,genesymbol,value)## genesymbol value
## 1 PARP1 TNF-related weak inducer of apoptosis (TWEAK)
## 2 PARP1 Oncostatin-M (OSM)
## 3 PARP1 Androgen receptor (AR)
## 4 PARP1 Tumor necrosis factor (TNF) alpha
## 5 PARP1 Corticotropin-releasing hormone (CRH)
## 6 XRCC5 Androgen receptor (AR)
## 7 XRCC6 Androgen receptor (AR)## Cellular localization of our proteins
annotations <-import_omnipath_annotations(proteins=genes_complex,
resources=c("ComPPI"))## Downloaded 28 annotation records.## Since we have same record_id for some results of our query, we spread
## these records across columns
spread(annotations, label, value) %>%
dplyr::arrange(desc(score)) %>%
dplyr::top_n(10, score)## uniprot genesymbol entity_type source record_id location
## 1 P12956 XRCC6 protein ComPPI 2978 nucleus
## 2 P09874 PARP1 protein ComPPI 11269 nucleus
## 3 Q14191 WRN protein ComPPI 16137 nucleus
## 4 P13010 XRCC5 protein ComPPI 13407 nucleus
## 5 P13010 XRCC5 protein ComPPI 13408 membrane
## 6 P12956 XRCC6 protein ComPPI 2977 cytosol
## 7 P13010 XRCC5 protein ComPPI 13406 cytosol
## 8 Q14191 WRN protein ComPPI 16138 cytosol
## 9 P12956 XRCC6 protein ComPPI 2979 membrane
## 10 P12956 XRCC6 protein ComPPI 2981 extracellular
## 11 P13010 XRCC5 protein ComPPI 13409 extracellular
## score
## 1 0.99999997629184
## 2 0.999999887104
## 3 0.9999996544
## 4 0.99999868288
## 5 0.972
## 6 0.958
## 7 0.958
## 8 0.94
## 9 0.8600000000000001
## 10 0.8600000000000001
## 11 0.86000000000000013.6 Intercell
Cells perceive cues from their microenvironment and neighboring cells, and respond accordingly to ensure proper activities and coordination between them. The ensemble of these communication process is called inter-cellular signaling (intercell).
Intercell query provides information about the roles of proteins in inter-cellular signaling (e.g. if a protein is a ligand, a receptor, an extracellular matrix (ECM) component, etc.) This query type is very similar to annotations. However, intercell data does not come from original sources, but combined from several databases by us into categories (we also refer to the original sources).
We first inspect the different categories available in the OmniPath webserver. Then, we focus again in our previously selected complex and we check its the location of its individual components in the inter-cellular context. We can however see that the components of this particular complex are intracellular.
## We check some of the different intercell categories
get_intercell_generic_categories()## Downloaded 1108 records.## [1] "plasma_membrane" "transmembrane"
## [3] "peripheral" "transmembrane_predicted"
## [5] "receptor" "adhesion"
## [7] "ligand" "cell_surface_ligand"
## [9] "ecm" "secreted"
## [11] "ion_channel" "cell_surface"
## [13] "transporter" "ligand_regulator"
## [15] "receptor_regulator" "plasma_membrane_transmembrane"
## [17] "cell_adhesion" "extracellular"
## [19] "matrix_adhesion" "secreted_receptor"
## [21] "plasma_membrane_peripheral" "plasma_membrane_regulator"
## [23] "secreted_enzyme" "cell_surface_enzyme"
## [25] "matrix_adhesion_regulator" "secreted_peptidase"
## [27] "intracellular" "cell_surface_peptidase"
## [29] "extracellular_peptidase" "secreted_peptidase_inhibitor"
## [31] "secreted_enyzme" "desmosome"
## [33] "ecm_regulator" "gap_junction"
## [35] "sparc_ecm_regulator" "intracellular_intercellular_related"
## [37] "adherens_junction" "ion_channel_regulator"
## [39] "tight_junction"## We import the intercell data into a dataframe
intercell <- import_omnipath_intercell(scope = 'generic',
aspect = 'locational')## Downloaded 200201 intercellular communication role records.## We check the intercell annotations for the individual components of
## our previous complex. We filter our data to print it in a good format
dplyr::filter(intercell,genesymbol %in% genes_complex) %>%
dplyr::distinct(genesymbol, parent, .keep_all = TRUE) %>%
dplyr::select(category, genesymbol, parent) %>%
dplyr::arrange(genesymbol)## category genesymbol parent
## 1 intracellular PARP1 intracellular
## 2 intracellular WRN intracellular
## 3 intracellular XRCC5 intracellular
## 4 intracellular XRCC6 intracellular## We close graphical connections
while (!is.null(dev.list())) dev.off()4 Conclusion
OmnipathR provides access to the wealth of data stored in the OmniPath webservice http://omnipathdb.org/ from the R enviroment. In addition, it contains some utility functions for visualization, filtering and analysis. The main strength of OmnipathR is the straightforward transformation of the different OmniPath data into commonly used R objects, such as dataframes and graphs. Consequently, it allows an easy integration of the different types of data and a gateway to the vast number of R packages dedicated to the analysis and representaiton of biological data. We highlighted these abilities in some of the examples detailed in previous sections of this document.
Session info
## R version 4.0.3 (2020-10-10)
## Platform: x86_64-pc-linux-gnu (64-bit)
## Running under: Ubuntu 18.04.5 LTS
##
## Matrix products: default
## BLAS: /home/biocbuild/bbs-3.12-bioc/R/lib/libRblas.so
## LAPACK: /home/biocbuild/bbs-3.12-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] stats graphics grDevices utils datasets methods base
##
## other attached packages:
## [1] gprofiler2_0.2.0 dnet_1.1.7 supraHex_1.28.0 hexbin_1.28.1
## [5] tidyr_1.1.2 knitr_1.30 ggraph_2.0.3 OmnipathR_2.0.0
## [9] jsonlite_1.7.1 igraph_1.2.6 ggplot2_3.3.2 dplyr_1.0.2
## [13] BiocStyle_2.18.0
##
## loaded via a namespace (and not attached):
## [1] viridis_0.5.1 httr_1.4.2 tidygraph_1.2.0
## [4] viridisLite_0.3.0 assertthat_0.2.1 BiocManager_1.30.10
## [7] highr_0.8 stats4_4.0.3 yaml_2.2.1
## [10] ggrepel_0.8.2 pillar_1.4.6 lattice_0.20-41
## [13] glue_1.4.2 digest_0.6.27 polyclip_1.10-0
## [16] colorspace_1.4-1 htmltools_0.5.0 Matrix_1.2-18
## [19] pkgconfig_2.0.3 magick_2.5.0 bookdown_0.21
## [22] purrr_0.3.4 scales_1.1.1 tweenr_1.0.1
## [25] ggforce_0.3.2 tibble_3.0.4 generics_0.0.2
## [28] farver_2.0.3 ellipsis_0.3.1 withr_2.3.0
## [31] BiocGenerics_0.36.0 lazyeval_0.2.2 cli_2.1.0
## [34] magrittr_1.5 crayon_1.3.4 evaluate_0.14
## [37] fansi_0.4.1 nlme_3.1-150 MASS_7.3-53
## [40] graph_1.68.0 tools_4.0.3 data.table_1.13.2
## [43] hms_0.5.3 lifecycle_0.2.0 stringr_1.4.0
## [46] plotly_4.9.2.1 munsell_0.5.0 compiler_4.0.3
## [49] rlang_0.4.8 grid_4.0.3 RCurl_1.98-1.2
## [52] htmlwidgets_1.5.2 bitops_1.0-6 labeling_0.4.2
## [55] rmarkdown_2.5 gtable_0.3.0 curl_4.3
## [58] graphlayouts_0.7.1 R6_2.4.1 gridExtra_2.3
## [61] utf8_1.1.4 readr_1.4.0 Rgraphviz_2.34.0
## [64] ape_5.4-1 stringi_1.5.3 parallel_4.0.3
## [67] Rcpp_1.0.5 vctrs_0.3.4 png_0.1-7
## [70] tidyselect_1.1.0 xfun_0.18References
Ben-Shlomo, I., S. Yu Hsu, R. Rauch, H. W. Kowalski, and A. J. W. Hsueh. 2003. “Signaling Receptome: A Genomic and Evolutionary Perspective of Plasma Membrane Receptors Involved in Signal Transduction.” Science Signaling 2003 (187). American Association for the Advancement of Science (AAAS):re9–re9. https://doi.org/10.1126/stke.2003.187.re9.
Berggård, Tord, Sara Linse, and Peter James. 2007. “Methods for the Detection and Analysis of Proteinprotein Interactions.” PROTEOMICS 7 (16). Wiley:2833–42. https://doi.org/10.1002/pmic.200700131.
Dinkel, H., C. Chica, A. Via, C. M. Gould, L. J. Jensen, T. J. Gibson, and F. Diella. 2010. “Phospho.ELM: A Database of Phosphorylation Sites–Update 2011.” Nucleic Acids Research 39 (Database). Oxford University Press (OUP):D261–D267. https://doi.org/10.1093/nar/gkq1104.
Dobson, László, Tamás Langó, István Reményi, and Gábor E. Tusnády. 2014. “Expediting Topology Data Gathering for the TOPDB Database.” Nucleic Acids Research 43 (D1). Oxford University Press (OUP):D283–D289. https://doi.org/10.1093/nar/gku1119.
Drew, Kevin, Chanjae Lee, Ryan L Huizar, Fan Tu, Blake Borgeson, Claire D McWhite, Yun Ma, John B Wallingford, and Edward M Marcotte. 2017. “Integration of over 9, 000 Mass Spectrometry Experiments Builds a Global Map of Human Protein Complexes.” Molecular Systems Biology 13 (6). EMBO:932. https://doi.org/10.15252/msb.20167490.
Garcia-Alonso, Luz, Christian H. Holland, Mahmoud M. Ibrahim, Denes Turei, and Julio Saez-Rodriguez. 2019. “Benchmark and Integration of Resources for the Estimation of Human Transcription Factor Activities.” Genome Research 29 (8). Cold Spring Harbor Laboratory:1363–75. https://doi.org/10.1101/gr.240663.118.
Giurgiu, Madalina, Julian Reinhard, Barbara Brauner, Irmtraud Dunger-Kaltenbach, Gisela Fobo, Goar Frishman, Corinna Montrone, and Andreas Ruepp. 2018. “CORUM: The Comprehensive Resource of Mammalian Protein Complexes2019.” Nucleic Acids Research 47 (D1). Oxford University Press (OUP):D559–D563. https://doi.org/10.1093/nar/gky973.
Hornbeck, Peter V., Bin Zhang, Beth Murray, Jon M. Kornhauser, Vaughan Latham, and Elzbieta Skrzypek. 2014. “PhosphoSitePlus, 2014: Mutations, PTMs and Recalibrations.” Nucleic Acids Research 43 (D1). Oxford University Press (OUP):D512–D520. https://doi.org/10.1093/nar/gku1267.
Keerthikumar, Shivakumar, David Chisanga, Dinuka Ariyaratne, Haidar Al Saffar, Sushma Anand, Kening Zhao, Monisha Samuel, et al. 2016. “ExoCarta: A Web-Based Compendium of Exosomal Cargo.” Journal of Molecular Biology 428 (4). Elsevier BV:688–92. https://doi.org/10.1016/j.jmb.2015.09.019.
Türei, Dénes, Tamás Korcsmáros, and Julio Saez-Rodriguez. 2016. “OmniPath: Guidelines and Gateway for Literature-Curated Signaling Pathway Resources.” Nature Methods 13 (12). Springer Science; Business Media LLC:966–67. https://doi.org/10.1038/nmeth.4077.
Vento-Tormo, Roser, Mirjana Efremova, Rachel A. Botting, Margherita Y. Turco, Miquel Vento-Tormo, Kerstin B. Meyer, Jong-Eun Park, et al. 2018. “Single-Cell Reconstruction of the Early Maternalfetal Interface in Humans.” Nature 563 (7731). Springer Nature:347–53. https://doi.org/10.1038/s41586-018-0698-6.