Open sapuizait opened 3 years ago
Hi @sapuizait ,
I hope someone more expert on this could comment also. I will just give my 2 cents. I guess that you get 2 KOs because the relationship between eggNOG OGs and KEGG OGs is not one-2-one, unfortunately.
Depending on your data, analysis, goals you could either discard those, use only one of them or use both. Personally, I would introduce both in KEGGmapper, although I have very little experience with this.
Good luck!
Best, Carlos
Hey Carlos
Thanks a lot. I have ended up using a version where i introduce everything and one that i eliminate anything that has more than 1 (pretty rare). At the end of the day it makes no huge difference as pathways that are not complete continue to be incomplete...
Thanks AGAIN P
I think it was a good idea.
Thanks to you! Feel free to leave the issue open just in case someone else could give advice.
Best, Carlos
Dear all
This is not an issue, its more of a question about the results i get when I run the eggnog emapper. At the output table, when i look at the KEGGs, sometimes there are more than one KEGG IDs in the same row (1 row = the result of 1 querry). For example, even though most of the results/look like this:
meaning there is only one KEGG id assigned to the querry, the K07729
sometimes I get results like this
which have two KOs assigned K01802,K03768
and even though usually these KEGGs are orthologs or have very similar function they kind of flork up my pathway reconstruction because either KEGGmapper does not recognize the comma separated KOs or if I split them I feel like I am pushing it because I assume the similarities werent good enough to give me a single ID in the first place...
Thus I am leaning towards the "get rid of them" solution but what do you think? How do you usually deal with these type of situations?