-
Notifications
You must be signed in to change notification settings - Fork 21
Error with Phanotate (return code 1) #350
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
Comments
I have encountered the same problem. Have you resolved it,please? |
Hi @kakadaisy @Norina28 , Are you running Pharokka on entire SA (Staph aureus?) bacterial genomes? Phanotate is not designed for large bacterial sized chromosomes. If you are indeed running Pharokka on phage genome isolates, then this is certainly a big problem :) If so, would you be able to upload an example input FASTA so I can reproduce the errors? George |
Hi @gbouras13 thank you for your reply. Yes, I was running Pharokka on the complete Staph aureus genomes. Okay, then this explains a lot. ◡̈ Ele |
No problem - I'd use something like PhiSpy or Genomad :). Closing this issue now. George |
Hello, @gbouras13 thank you for your reply. I ran it after removing the genome of the host bacteria. This is the genome I used, and I uploaded my phage genome. Could you please help me check what the problem is? Thank you |
Description
I am trying to run pharokka (w/ & w/o fast option) on SA genomes but I always get this same error:
....
2024-06-27 15:15:05.043 | INFO | main:main:280 - Running Phanotate.
2024-06-27 15:15:05.046 | INFO | external_tools:run:50 - Started running phanotate.py -f fasta -o /home/ecella/ATB/SAMD00009489_pharrokka2/phanotate_out_tmp.fasta ./SAMD00009489.fa ...
2024-06-27 15:22:58.067 | ERROR | external_tools:run_tool:94 - Error calling phanotate.py -f fasta -o /home/SAMD00009489_pharrokka2/phanotate_out_tmp.fasta ./SAMD00009489.fa (return code 1)
2024-06-27 15:22:58.069 | ERROR | processes:run_phanotate:291 - Error with Phanotate
What I Did
Thank you so much
The text was updated successfully, but these errors were encountered: