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
Hello,
When I submit the checkm2 command on the cluster using sbatch, I encounter different errors each time, such asERROR: Make sure prodigal is on your system path. or ERROR: File does not exist: input_5751.gff.4. Sometimes I also receive the error sh: fork: retry: No child processes. However, when I log into a compute node and run the command directly, I do not experience any issues.
Another issue is that when I specify the number of threads, it seems that checkm2 generates a number of sub-threads that exceed this value. Why is this happening?
Sometimes the software gets stuck at Calling genes in 1000 bins with 32 threads:, and then when I try to input protein sequences, it gets stuck at Calculating metadata for 10000 bins with 36 threads:.
[03/07/2024 02:22:25 PM] INFO: Running CheckM2 version 1.0.1
[03/07/2024 02:22:25 PM] INFO: Running quality prediction workflow with 32 threads.
[03/07/2024 02:23:07 PM] INFO: Calling genes in 1000 bins with 32 threads:
[03/07/2024 02:23:07 PM] ERROR: Make sure prodigal is on your system path.
[03/07/2024 02:23:07 PM] ERROR: Make sure prodigal is on your system path.
The text was updated successfully, but these errors were encountered:
Interestingly, although it indicated that prodigal could not be found, a portion of the proteins was successfully predicted, and then the program froze.
Does checkm2 testrun complete successfully? Was this installed via conda? It sounds like perhaps file permission issues might be playing a role, but it's hard to say with such generic errors.
Hello,
When I submit the checkm2 command on the cluster using
sbatch
, I encounter different errors each time, such asERROR: Make sure prodigal is on your system path.
orERROR: File does not exist: input_5751.gff.4
. Sometimes I also receive the errorsh: fork: retry: No child processes
. However, when I log into a compute node and run the command directly, I do not experience any issues.Another issue is that when I specify the number of threads, it seems that checkm2 generates a number of sub-threads that exceed this value. Why is this happening?
Sometimes the software gets stuck at
Calling genes in 1000 bins with 32 threads:
, and then when I try to input protein sequences, it gets stuck atCalculating metadata for 10000 bins with 36 threads:
.Many thanks for your time and your help,
Here is some additional information.
checkm2 command:
source activate checkm2 checkm2 predict -x fa -t 32 --tmpdir ckm2.tmp --input bin_dir --output-directory ckm2 --remove_intermediates --force
node info:
ps xf
checkm2.log
[03/07/2024 02:22:25 PM] INFO: Running CheckM2 version 1.0.1 [03/07/2024 02:22:25 PM] INFO: Running quality prediction workflow with 32 threads. [03/07/2024 02:23:07 PM] INFO: Calling genes in 1000 bins with 32 threads: [03/07/2024 02:23:07 PM] ERROR: Make sure prodigal is on your system path. [03/07/2024 02:23:07 PM] ERROR: Make sure prodigal is on your system path.
The text was updated successfully, but these errors were encountered: