Skip to content
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

categorising the result #36

Open
dikshyantg opened this issue May 13, 2021 · 3 comments
Open

categorising the result #36

dikshyantg opened this issue May 13, 2021 · 3 comments

Comments

@dikshyantg
Copy link

Hi , running the Deepgo plus with the basic command gave me result.tsv file with predicted go terms for each sequence. However, I wanted to categorise those GO terms, based on cellularcomponent , molecular function and biological process for each fasta sequence. The tsv files , I get even for one gene has large number of predicted go terms with their statistical values separated by "|". However they aren't arranged in a descending order so predicting which is the better go term is little tricky so categorising them first then looking at the highest statistical value seems like a better way for me. Would you be able to help me in this ?

Thanks!

@coolmaksat
Copy link
Contributor

Hi, thank you for raising this issue.
You can use predict.py script to get better formatted results. I've just added the GO term subontology to it.

@dikshyantg
Copy link
Author

Thanks a lot that worked. Though unlike Deepgo command , this predict.py script requires some files under data folder as zipped so that gzip could open the file. Another difference was Deepgo gave the result in tsv like GO:0032502|0.318 which means the statistical value is 0.318 but here it is given in tsv as HRE53_03560 GO:0016787 molecular_function hydrolase activity 1.34 0.208 . believe it is saying between 1.34 to 0.4208 and we choose the later (0.4208)right?

@coolmaksat
Copy link
Contributor

Hi,
yes, the last item is the prediction score. The number before is the class specificity (or information content).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants