Skip to content
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

is kofam scan running correctly - tmp directory #18

Open
soilmicrobiome opened this issue Oct 29, 2020 · 0 comments
Open

is kofam scan running correctly - tmp directory #18

soilmicrobiome opened this issue Oct 29, 2020 · 0 comments

Comments

@soilmicrobiome
Copy link

Hi there,

I am just updated kofam 1.2 to 1.3, running on a HPC. Usually when i run the program the tmp directory that is created disappears after the job has finished. In the new version 1.3 - the job finishes but the tmp directory is still there. Is this normal? My slurm file has no debugging info so i can't check if everything completed correctly.

I complied the program on our HPC as follows:
virtualenv ~/kofamscan
module load gcc/7.3.0 nixpkgs/16.09 hmmer/3.2.1 ruby/2.6.1 parallel/20160722
source kofamscan/bin/activate

cd kofamscan/bin
wget ftp://ftp.genome.jp/pub/tools/kofam_scan/kofam_scan-1.3.0.tar.gz
tar xvzf kofam_scan-1.3.0.tar.gz
mkdir db
cd db
wget ftp://ftp.genome.jp/pub/db/kofam/ko_list.gz
wget ftp://ftp.genome.jp/pub/db/kofam/profiles.tar.gz
gunzip ko_list.gz
tar xvzf profiles.tar.gz

Edit config.yml - added paths to ko and profiles.

I am running the program as follows:
#!/bin/bash
#SBATCH --mem=xxxx
#SBATCH --nodes=1
#SBATCH --account=xxx
#SBATCH --cpus-per-task=32
#SBATCH --time=0-23:59
#SBATCH --job-name=xxx

module load gcc/7.3.0 nixpkgs/16.09 hmmer/3.2.1 ruby/2.6.1 parallel/20160722
source /home/user/kofamscan/bin/activate
/home/user/kofamscan/bin/kofam_scan-1.3.0/./exec_annotation -o /path_to_output_dir/kofamscan.txt /path_to_orf_file/xxx.faa --tmp-dir=DIR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant