-
Notifications
You must be signed in to change notification settings - Fork 27
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
Error in step 3. Combining and annotating the blast files with orthogroup info ... #148
Comments
I meet same problem with @htorrado, dose it has any suggestion? |
What version are y'all using? This is an error that popped up every now and then with duplicated gene IDs in <v1.1, but I had hoped I'd resolved it. |
I'm using GENESPACE v1.3.1 in R 4.1.2 Thanks for your help! |
I'm using GENESPACE v1.3.1 and R 4.2.0. I have tried to filter fragment scaffolds and now it seemed run successfully, does it could be this reason? |
@jkfo002 thanks for troubleshooting that. GENESPACE should deal with these without an issue. This is clearly a bug and needs to be fixed. Would you mind sharing your input /bed and /peptide directories from the run that caused the error? If so, please send me an email and we'll set up a private data transfer. email: jlovell[at]hudsonalpha[dot]org |
@jtlovell Sorry for late reply, I have sent the data to you. By the way, could GENESPACE construct gene synteny in local region for multiple genome? |
np. I'll try to get to it next week. |
Actually....no, I think I need a zoom in on the small region of chromosome and see the synteny of gene cluster (maybe). @jtlovell |
I have the same issue. Any luck? |
For me, I have the error in the test example as well. Here is a tail of the output. Thank you!
|
What orthofinder version are you using? I've seen this issue pop up from other users but have been unable to recreate it myself. |
Hello jtlovell,
Thanks for all your work on this package!
I'm using GENESPACE v1.3.1 in a conda environment with R 4.1.2 and have it successfully for your test dataset so it should all be working as intended.
When I use my own dataset, it all starts off well, e.g. all geneIDS are recognized (all exactly match), etc. but then in step 3, I receive the error message below and was hoping you may have any ideas or suggestions how I could resolve this and proceed.
When I try to run it with just one core the error becomes:
The second error message seems related with the merge on step 2.3 on the annotate_blast command (merge with bed information). I tried to add "allow.cartesian" to that merge function but the full R session gets killed if it's just 1 core and if it's parallelized (using 10 cores) I receive the following error message:
This may lead to a merge file that is not compatible with some of your code below... ?
Thank you very much in advance!!
Best,
Héctor
The text was updated successfully, but these errors were encountered: