-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding values in annotation file #261
Comments
Hi @jfourquet2 , could you specify which version of eggnog-mapper are you using, and also an example of a results you asking about? Thank you. Best, |
Hi Carlos,
In the column |
Hi @jfourquet2 , not sure if I understand your question. I will try to answer. Besides the eggNOG OGs you have another column, best_og_name, which is the OG used to retrieve the orthologs from which annotation terms are finally obtained. So more specifically, the annotations you see should not come from COG3850@1|root and COG3850@2|Bacteria, but only from COG3850@2|Bacteria in this case. I hope this makes sense. Best, |
Hi Carlos, |
Hi Joanna, glad to help. There are different annotations separated by commas because there are different annotations in the eggnog DB for your Orthologous Group. For example, check COG3850 in http://eggnog5.embl.de/ under the "Functional profile" -> "Domains" tabs I hope this makes sense. Best, |
Hi Carlos, |
Hi Joanna, sorry for the delay answering.
It should be conceptually the same. However, when using HMMER the first hit is in fact an OG. From that OG, the query is realigned to the OG members, and the best hit is used as seed ortholog. Then, the next steps (finding the other OGs in the hierarchy, deciding which is best, etc) is the same. I guess the "only in HMM mode" was because that evalue and score from a hit to a OG is only obtained using HMMER. With diamond the evalue and score are from the alignment to the seed ortholog.
Yes, all the annotations are from the eggNOG 5.0.1 database, unless you are using --pfam_realign options, in which case the PFAM database is used directly. The PFAM database used for eggNOG 5.0.1 DB is PFAM31 currently if I recall correctly. We have plans to update all the annotations soon, but I cannot confirm when will happen. To update, so far the idea is that each eggnog-mapper version has associated an eggNOG database, and therefore when you update eggnog-mapper and you run "emapper.py --version" you should be warned if the eggnNOG DB version is not the one expected for the emapper.py version. In such case, you better run "download_eggnog_data.py" again to update the database.
I hope this makes sense. Best, |
Hi Carlos, |
Glad to be of help. |
Hi,
To be sure of my undertanding of fields in the output annotation file, are the elements into "Transferred annotations fields" are all GOs terms, EC numbers, etc of all OG presents into the column "eggNOG OGs"?
Thanks in advance for your answer !
The text was updated successfully, but these errors were encountered: