-
Notifications
You must be signed in to change notification settings - Fork 7
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
question about OMArk rules and omamer result #35
Comments
Hello! OMArk will automatically process the OMAmer results, while recovering some additional data from the OMAmer database. All details are described in OMArk's paper at https://www.nature.com/articles/s41587-024-02147-w . However, here is a quick overview: For completeness. OMark query the OMAmer database to extract all orthologous groups (HOGs) at the taxon of interest and select the ones present in more than 80% of species - conserved HOGs. If thoses are HOGs are also found in the OMAmer input; it reports it as present (as single or duplicate depending on the number of occurences in the file ) For the consistency part, it is slightly more complicated. Again, OMArk query the OMAmer database to obtain the list of all HOGs known to exist in the clade of interest. If the HOGs found by OMAmer for any protein it will be classified as phylogenetically Consistent (blue); the one with no match in the OMAmer file are classified as Unknown. For the structural consistency (fragment/partial mapping): OMArk uses the data provided in the OMAmer output directly. I hope this answers your question. Best wishes, |
Thank you for your answer. OMArk is a great tool that has given me some inspiration in dealing with the logic of HOG attribution for target genes and dealing with some of the problems I encountered in my project. Thanks, |
Hello, I would like to ask OMArk rules for determining gene conservation or consistency--what specific rules are used to determine these data in omamer results--have any detailed instructions? thanks.
The text was updated successfully, but these errors were encountered: