What is proper enrichKEGG input ids
1
2
Entering edit mode
5.2 years ago
MKM ▴ 20

Question is about function enrichKEGG. Input data is a vector of entrez gene ids. Please see, page 12 of manual at

https://bioconductor.org/packages/release/bioc/manuals/clusterProfiler/man/clusterProfiler.pdf. But for parameter keyType=entrezid is not supported. Its default value is kegg.

That means when one input data it should be in entrezgene ids but downloaded data from Kegg website will consist of kegg ids (not entrez gene ids), can it has any problem during enrichment analysis?

What is the proper command

1)

enrichKEGG( enzids , organism="mmu", keyType = "ENTREZID", use_internal_data = FALSE,
                       pAdjustMethod = "BH", pvalueCutoff  = 0.05, qvalueCutoff  = 0.1)

OR

2)

 enrichKEGG( enzids , organism="mmu", keyType = "kegg", use_internal_data = FALSE,
                       pAdjustMethod = "BH", pvalueCutoff  = 0.05, qvalueCutoff  = 0.1)
clusterProfiler R bioconductor • 4.2k views
ADD COMMENT
1
Entering edit mode
5.2 years ago
Guangchuang Yu ★ 2.5k

first of all, the tag should not contain @.


according to page 12 that you mentioned, it's very clear of the parameter keyType:

one of "kegg", ’ncbi-geneid’, ’ncib-proteinid’ and ’uniprot’

So, keyType = "ENTREZID" in command 1 is wrong and command 2 will works properly.


from the post: https://guangchuangyu.github.io/2016/05/convert-biological-id-with-kegg-api-using-clusterprofiler/.

The ‘kegg’ is the primary ID used in KEGG database. The data source of KEGG was from NCBI. A rule of thumb for the ‘kegg’ ID is entrezgene ID for eukaryote species and Locus ID for prokaryotes.

The kegg ID can be entrezgene (as in your example) or Locus or other types. Different species may use different type. We don't make assumption of it and keyType = "ENTREZID" is not accepted.

ADD COMMENT

Login before adding your answer.

Traffic: 2021 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6