The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
STRING is a comprehensive database of protein-protein interactions (PPI) that in version 11.0, covers 24,584,628 proteins from 5,090 organisms. Directly quoting from their paper:
The STRING database aims to collect, score and integrate all publicly available sources of protein–protein interaction information, and to complement these with computational predictions. Its goal is to achieve a comprehensive and objective global network, including direct (physical) as well as indirect (functional) interactions.
(source: Szklarczyk, Damian, et al. “STRING v11: protein–protein association networks with increased coverage, supporting functional discovery in genome-wide experimental datasets.” Nucleic acids research 47.D1 (2019): D607-D613. )
You can find an argument named “species” in every rbioapi STRING function. Providing the species argument is not mandatory, but it has been recommended in STRING API’s documentation to always specify the species. An exception is when your input proteins’ vector length is more than 100; In such cases, the species argument is required. Otherwise, calling the function without providing the species will produce an ERROR.
Although STRING API resources will handle and recognize a variety of identifiers, it is recommended that you first map your IDs to STRING IDs before using them in other rbioapi STRING functions.
## 1 We create a variable with our genes' NCBI IDs
proteins <- c("p53", "BRCA1", "cdk2", "Q99835", "CDC42","CDK1","KIF23",
"PLK1","RAC2","RACGAP1","RHOA","RHOB", "PHF14", "RBM3")
## 2 Now we map our protein IDs
proteins_mapped <- rba_string_map_ids(ids = proteins,
species = 9606)
## 3 What we need and will use for the rest of this vignette is the `stringId` column
You can retrieve a list of interactions that the proteins in your set have with each other along with the STRING annotations of each interaction. You may filter the results by using required_score and network_type arguments.
See the ‘values’ section rba_string_interactions_network
function’s manual for information on the returned columns.
int_net <- rba_string_interactions_network(ids = proteins_mapped,
species = 9606,
required_score = 500)
In the last example, we only obtained the interaction which our proteins have among themselves, what if we wanted to get a list of every protein which interact with our protein(s)?
To do that, we can use
rba_string_interaction_partners
:
## Although we supply only one protein ID here (CD40 protein), you can provide a vector of proteins as the input
int_partners <- rba_string_interaction_partners(ids = "9606.ENSP00000361359",
species = 9606,
required_score = 900)
Let’s go back to the interaction network. As you must have seen in
the STRING webpages, STRING plots the interaction network of your
proteins with many customizations available. You can also do that with
STRING API services. rba_string_network_image
function is
very flexible and you have a variety of options; see the function’s
manual.
## Example 1:
graph_1 <- rba_string_network_image(ids = proteins_mapped,
image_format = "image",
species = 9606,
save_image = FALSE,
required_score = 500,
network_flavor = "confidence")
## Example 2:
graph_2 <- rba_string_network_image(ids = proteins_mapped,
image_format = "image",
species = 9606,
save_image = FALSE,
required_score = 500,
add_color_nodes = 5,
add_white_nodes = 5,
network_flavor = "actions")
STRING let you perform two types of enrichments. See STRING’s paper for more information.
The first type is the conventional type, which statistically tests your supplied gene sets against some sets of annotation. Currently, STRING supports Gene Ontology, KEGG pathways, UniProt Keywords, PubMed publications, Pfam domains, InterPro domains, and SMART domains. (source).
As usual, we inspect the output using the str()
function. As you can see below, the enrichment results of each category
can be found as the returned list’s elements.
str(enriched, max.level = 1)
#> List of 14
#> $ COMPARTMENTS :'data.frame': 25 obs. of 10 variables:
#> $ Component :'data.frame': 17 obs. of 10 variables:
#> $ DISEASES :'data.frame': 11 obs. of 10 variables:
#> $ Function :'data.frame': 12 obs. of 10 variables:
#> $ InterPro :'data.frame': 3 obs. of 10 variables:
#> $ KEGG :'data.frame': 45 obs. of 10 variables:
#> $ Keyword :'data.frame': 14 obs. of 10 variables:
#> $ NetworkNeighborAL:'data.frame': 5 obs. of 10 variables:
#> $ PMID :'data.frame': 100 obs. of 10 variables:
#> $ Process :'data.frame': 148 obs. of 10 variables:
#> $ RCTM :'data.frame': 59 obs. of 10 variables:
#> $ SMART :'data.frame': 1 obs. of 10 variables:
#> $ TISSUES :'data.frame': 12 obs. of 10 variables:
#> $ WikiPathways :'data.frame': 46 obs. of 10 variables:
Let us see the “DISEASES” results as an example. Below, we can see which terms of the Human Disease Ontology were over-represented:
Please Note: Other services supported by rbioapi also provide Over-representation analysis tools. Please see the vignette article Do with rbioapi: Over-Representation (Enrichment) Analysis in R (link to the documentation site) for an in-depth review.
Even without incorporating annotation data, STRING can calculate if your proteins are functionally related. Briefly, STRING accomplishes this by comparing the interactions’ distribution in your protein-set to the interactions’ distribution in the proteome. Read STRING’s paper for more information.
rba_string_enrichment_ppi(ids = proteins_mapped,
species = 9606)
#> $number_of_nodes
#> [1] 14
#>
#> $number_of_edges
#> [1] 40
#>
#> $average_node_degree
#> [1] 5.71
#>
#> $local_clustering_coefficient
#> [1] 0.694
#>
#> $expected_number_of_edges
#> [1] 19
#>
#> $p_value
#> [1] 1.35e-05
As you have seen above, STRING maps the proteins to multiple annotation sources. You can obtain any annotation associated with your proteins without performing enrichment analysis and retrieving just the significant portion.
annotations <- rba_string_annotations(ids = "9606.ENSP00000269305",
species = 9606)
## This function returns large results, so the results was not shown in this vignette.
Some rbioapi STRING functions were not covered in this vignette, please check their manuals:
rba_string_homology_intra()
rba_string_homology_inter()
rba_string_version()
To cite STRING (Please see https://string-db.org/cgi/about?footer_active_subpage=references):
To cite rbioapi:
#> R version 4.3.3 (2024-02-29 ucrt)
#> Platform: x86_64-w64-mingw32/x64 (64-bit)
#> Running under: Windows 11 x64 (build 22631)
#>
#> Matrix products: default
#>
#>
#> locale:
#> [1] LC_COLLATE=C
#> [2] LC_CTYPE=English_United States.utf8
#> [3] LC_MONETARY=English_United States.utf8
#> [4] LC_NUMERIC=C
#> [5] LC_TIME=English_United States.utf8
#>
#> time zone: Europe/Brussels
#> tzcode source: internal
#>
#> attached base packages:
#> [1] stats graphics grDevices utils datasets methods base
#>
#> other attached packages:
#> [1] rbioapi_0.8.1
#>
#> loaded via a namespace (and not attached):
#> [1] digest_0.6.35 R6_2.5.1 fastmap_1.1.1 xfun_0.43
#> [5] magrittr_2.0.3 cachem_1.0.8 knitr_1.45 htmltools_0.5.8
#> [9] png_0.1-8 rmarkdown_2.26 lifecycle_1.0.4 DT_0.32
#> [13] cli_3.6.2 grid_4.3.3 sass_0.4.9 jquerylib_0.1.4
#> [17] compiler_4.3.3 highr_0.10 httr_1.4.7 rstudioapi_0.16.0
#> [21] tools_4.3.3 curl_5.2.1 evaluate_0.23 bslib_0.6.2
#> [25] yaml_2.3.8 htmlwidgets_1.6.4 rlang_1.1.3 jsonlite_1.8.8
#> [29] crosstalk_1.2.1
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.