You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running prokka version 1.13, it says prokka requires Blastp 2.2 or higher, while also saying my Blastp version is 2.12.
This is prokka 1.13
Written by Torsten Seemann <torsten.seemann@gmail.com>
Homepage is https://github.com/tseemann/prokka
Local time is Thu Jan 16 21:28:49 2025
You are a_user
Operating system is linux
You have BioPerl 1.007002
System has 20 cores.
Will use maximum of 6 cores.
Annotating as >>> Bacteria <<<
Generating locus_tag from 'a_user's_organism.fna' contents.
Creating new output folder: Prokka_Annotation
Running: mkdir -p Prokka_Annotation
Using filename prefix: PROKKA_01162025.XXX
Setting HMMER_NCPU=1
Writing log to: Prokka_Annotation/PROKKA_01162025.log
Command: /home/a_user/miniconda3/envs/prokka/bin/prokka --outdir Prokka_Annotation --cpus 6 --rnammer --genus Thermus --species aquaticus --kingdom Bacteria 'a_user's_organism.fna'
Appending to PATH: /home/a_user/miniconda3/envs/prokka/bin
Looking for 'aragorn' - found /home/a_user/miniconda3/envs/prokka/bin/aragorn
Determined aragorn version is 1.2
Looking for 'barrnap' - found /home/a_user/miniconda3/envs/prokka/bin/barrnap
Determined barrnap version is 0.8
Looking for 'blastp' - found /home/a_user/miniconda3/envs/prokka/bin/blastp
Determined blastp version is 2.12
Prokka needs blastp 2.2 or higher. Please upgrade and try again.
The text was updated successfully, but these errors were encountered:
version 1.13 had a bug where it says prokka requires blast 2.2 or higher when blast version is 2.16, but it is fixed when we install the latest version. A temporary fix if you want to use the previous version is to change MINVER of blastp and makeblastdb to 2.1 in prokka script
When running prokka version 1.13, it says prokka requires Blastp 2.2 or higher, while also saying my Blastp version is 2.12.
The text was updated successfully, but these errors were encountered: