|
a |
|
b/man/getMultiOmicsFeatures.Rd |
|
|
1 |
% Generated by roxygen2: do not edit by hand |
|
|
2 |
% Please edit documentation in R/feature_processing.R |
|
|
3 |
\name{getMultiOmicsFeatures} |
|
|
4 |
\alias{getMultiOmicsFeatures} |
|
|
5 |
\title{Collect feature mapping for user given databases and omics layer.} |
|
|
6 |
\usage{ |
|
|
7 |
getMultiOmicsFeatures( |
|
|
8 |
dbs = c("all"), |
|
|
9 |
layer = c("all"), |
|
|
10 |
returnTranscriptome = "SYMBOL", |
|
|
11 |
returnProteome = "SYMBOL", |
|
|
12 |
returnMetabolome = "HMDB", |
|
|
13 |
organism = "hsapiens", |
|
|
14 |
useLocal = TRUE |
|
|
15 |
) |
|
|
16 |
} |
|
|
17 |
\arguments{ |
|
|
18 |
\item{dbs}{List of databases that should be queried for pathways. Default: |
|
|
19 |
all available databases} |
|
|
20 |
|
|
|
21 |
\item{layer}{List of omics layer that should be addressed. Default: all three |
|
|
22 |
layer (transcriptome, proteome, metabolome)} |
|
|
23 |
|
|
|
24 |
\item{returnTranscriptome}{String specifying the returned gene ID format. |
|
|
25 |
Default: SYMBOL Options: SYMBOL, ENTREZID, UNIPROT, ENSEMBL, REFSEQ} |
|
|
26 |
|
|
|
27 |
\item{returnProteome}{String specifying the returned protein ID format. |
|
|
28 |
Default: SYMBOL Options: SYMBOL, ENTREZID, UNIPROT, ENSEMBL, REFSEQ} |
|
|
29 |
|
|
|
30 |
\item{returnMetabolome}{String specifying the returned metabolite ID format. |
|
|
31 |
Default: HMDB Options: HMDB, CAS, DTXCID, DTXSID, SID, CID, ChEBI, KEGG, Drugbank} |
|
|
32 |
|
|
|
33 |
\item{organism}{String specifying the organism of interest. This has direct |
|
|
34 |
influence on the available pathway databases. Default: "hsapiens" |
|
|
35 |
Options: see \code{\link[multiGSEA]{getOrganisms}}} |
|
|
36 |
|
|
|
37 |
\item{useLocal}{Boolean to use local pathway/feature descriptions. In case |
|
|
38 |
useLocal is set to FALSE, pathway definitions and feature extraction |
|
|
39 |
will be recalculated. This could take several minutes depending on the |
|
|
40 |
database used. Pathbank, for example, contains nearly 50000 pathway |
|
|
41 |
definition that have to be re-mapped. useLocal has no effect when |
|
|
42 |
pathway definitions are retrieved for the first time. Default: TRUE} |
|
|
43 |
} |
|
|
44 |
\value{ |
|
|
45 |
Nested list with extracted and mapped pathway features. |
|
|
46 |
} |
|
|
47 |
\description{ |
|
|
48 |
The functions makes use of the graphite R package to collect pathways from |
|
|
49 |
user specified databases. Depending on the omics layer specified, the |
|
|
50 |
function extracts either annotated genes/proteins (for transcriptome, |
|
|
51 |
proteome layer) or metabolites (for metabolite layer). The data structure |
|
|
52 |
that is returned is mandatory to calculate the multi-omics pathway |
|
|
53 |
enrichment. |
|
|
54 |
} |
|
|
55 |
\examples{ |
|
|
56 |
|
|
|
57 |
getMultiOmicsFeatures( |
|
|
58 |
dbs = c("kegg"), |
|
|
59 |
layer = c("transcriptome", "proteome"), |
|
|
60 |
organism = "hsapiens" |
|
|
61 |
) |
|
|
62 |
\donttest{ |
|
|
63 |
getMultiOmicsFeatures( |
|
|
64 |
dbs = c("kegg", "reactome"), |
|
|
65 |
layer = c("transcriptome", "metabolome"), |
|
|
66 |
organism = "mmusculus" |
|
|
67 |
) |
|
|
68 |
|
|
|
69 |
getMultiOmicsFeatures( |
|
|
70 |
dbs = c("reactome"), |
|
|
71 |
layer = c("proteome"), |
|
|
72 |
organism = "rnorvegicus", |
|
|
73 |
returnProteome = "ENTREZID" |
|
|
74 |
) |
|
|
75 |
} |
|
|
76 |
} |