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
hi, I install bracken v2.8 with conda/mamba (and i get source code from release source code v2.8 ) but it show info such as:
/nfs/disk7/user/lvzenglei/miniconda3/envs/mNGS/bin/bracken-build: illegal option -- -
Usage: bracken_build -k KMER_LEN -l READ_LEN -d MY_DB -x K_INSTALLATION -t THREADS
KMER_LEN kmer length used to build the kraken database (default: 35)
THREADS the number of threads to use when running kraken classification and the bracken scripts
READ_LEN read length to get all classifications for (default: 100)
MY_DB location of Kraken database
K_INSTALLATION location of the installed kraken/kraken-build scripts (default assumes scripts can be run from the user path)
**Note that this script will try to use kraken2 as default. If kraken2 is not installed, kraken will be used instead
But, I git clone this repo and it show such as :
./bracken-build: illegal option -- h
Usage: bracken_build -v -k KMER_LEN -l READ_LEN -d MY_DB -x K_INSTALLATION -y K_TYPE -t THREADS
-v Echoes the current software version and exits
KMER_LEN kmer length used to build the kraken database (default: 35)
THREADS the number of threads to use when running kraken classification and the bracken scripts
READ_LEN read length to get all classifications for (default: 100)
MY_DB location of Kraken database
K_INSTALLATION location of the installed kraken/kraken-build scripts (default assumes scripts can be run from the user path)
K_TYPE version of kraken to use (default = kraken2 - other options: kraken, krakenuniq)
I Think Maybe it should be fixed~~
The text was updated successfully, but these errors were encountered:
hi, I install bracken v2.8 with conda/mamba (and i get source code from release source code v2.8 ) but it show info such as:
But, I git clone this repo and it show such as :
I Think Maybe it should be fixed~~
The text was updated successfully, but these errors were encountered: