DAVID List Upload/Gene Conversion Tool
0
0
Entering edit mode
4 days ago
b5708137 • 0

Hello, everyone, how are you doing?

I've been trying to use DAVID to get the GO for a few proteins' genes. But, for some reason, it seems to "disagree" with the identifier type I got from BlastP, and, although I know 100% of my list is from GenBank, DAVID suggests using the Gene Conversion Tool to determine an identifier type. I did use it, even chose a species which is from the same genus as the one I'm working with, but no matter how many gene IDs I enter initially in the list tab (tried from 7 to 106) it won't successfully convert nor identify any of them. In fact most of them are considered Unique User IDs. So now I don't really imagine where is my mistake in all of this and I have no idea as to how to fix it.

I need these GO results to keep up with the work, so if you have any advice or solutions I'd really appreciate them. Also, I'm new to this kind of thing.

Thanks in advance, everyone!

edit: GenoMax advised to post examples, so here are some of the genes I've been trying to map with DAVID: XP_007820302.1, KFG84677.1, KJK74262.1, KAK8917140.1.

DAVID • 282 views
ADD COMMENT
1
Entering edit mode

Anytime you are referring to ID's, post a few examples.

If your ID's are computationally predicted (e.g. XP*) then DAVID may not be able to map them.

ADD REPLY
0
Entering edit mode

Thank you for your answer, I added the examples in the previous post. One of them starts as your example stated, so there's a probability that that's why DAVID isn't mapping them, right? Do you have any suggestions as to other platforms that I could use to map them?

ADD REPLY
1
Entering edit mode

Looks like your data is from Metarhizium anisopliae and DAVID is not able to use the ID's. Look into alternate options. Some mentioned here: for go enrichment analysis which tool do you recommend?

ADD REPLY

Login before adding your answer.

Traffic: 1597 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