-
Notifications
You must be signed in to change notification settings - Fork 191
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
issues with results post "--assign", single gene in multiple Orthogroups #941
Comments
Would you be able to send the following files for the --assign run that has odd results;
I'll see if I can work out what is happening |
Tar archives with full output. Links good for 6 days: |
Thanks - so if we take as an example gene Osat.NB.HPI3.Chr9.g378860.t1: In the --core run it is not assigned to an orthogroup, so ends up in unassigned genes (OG0030720) Thanks for pointing this out - i'll see if we can provide a fix for this |
I'm trying to get back into this. I need to do a large (>300 samples) orthofinder run and would prefer to use the "--assign" option for its superior performance. If the only issue is an erroneous Orthogroups_UnassignedGenes.tsv, then I'll probably run using the current version and just correct that output since that isn't very difficult. I am concerned that the issues run deeper though. I plan to do some testing to try to figure out the extent of the issues, but if you have any knowledge here, I'd love your input as well. |
I know that "orthogroups/" is considered to be deprecated in some sense, but it is still the best description of where different orthofinder results (like individual gene trees or protein msa) actually end up so it ends up being the second place I visit after Species_Tree. I've noticed some problems with the results after using the "--assign" options, specifically some interaction that is causing "orthogroups/unassigned_genes.tsv" to not be generated correctly. Consider the following two results, one from the initial orthofinder run and one from the second orthofinder run with --assign
...This is clearly a bug. I haven't dug through the source code to figure out what is going wrong exactly, but clearly a gene can't be in both OG0030720 and OG0031414
The text was updated successfully, but these errors were encountered: