-
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
Consistent error: if (is.na(gsParam$synteny$hogs)) { : argument is of length zero #174
Comments
hmm. before we try anything else, can you do this:
|
Thanks for getting back so quickly. This finds the N0.tsv file and puts it in
|
Hmm ... so when you run Can you run this:
|
Correct no errors with I ran the above code:
|
Thanks for the help troubleshooting Noah ... I'll communicate with you via email and post a resolution here when we reach one. |
Hi, thanks for such a great program. I am getting the same issue as #75 and #165
I am having exactly the same issue when using
orthofinder 2.5.5
withR 4.4.2
andGENESPACE 1.3.1
via WSL. I am running orthofinder outside of Genespace and then copying the results into thewd/
.run_genespace()
was working the first time when testing on 3 genomes and continues to work if I run with the original orthofinder output.Now I am doing a much larger run with 43 genomes and a new orthofinder run (which completed successfully) I'm consistently getting
if (is.na(gsParam$synteny$hogs)) { : argument is of length zero
This is the full error for context:
1. Running orthofinder (or parsing existing results) Checking for existing orthofinder results ... [1] FALSE ... found existing run, not re-running orthofinder Error in if (is.na(gsParam$synteny$hogs)) { : argument is of length zero
I have tried:
N0.tsv
directly to thewd/results
I understand running on 43 genomes is alot and I have not seen any other people using it for that many genomes. I am less interested in the plots and more in pan_genes outputs.
If you have any suggestions to how to work around this error I would really appreciate it.
The text was updated successfully, but these errors were encountered: