MEGARes and AmrPlusPlus - A comprehensive database of antimicrobial resistance genes and user-friendly pipeline for analysis of high-throughput sequencing data
I am running the main_AmrPlusPlus_v2_withRGI_Kraken.nf workflow, and I'm doing it with --host_index.
I'm not sure I'm doing things correctly, since the usage page says --index and not --host_index.
I just wanted to bring this up, because the --help says --host_index, from the script.
I would suggest a slight modification of the option, that could be easier to understand. Instead of having to declare all the index file using the * wildcard, it would be easier if people had to declare the index prefix including the path (like in bowtie2 for example).
That way, the --host option would be automatically checked for the existence of an index by checking if it has the index files with the same prefix, and the user would only have to index the FASTA reference file using bwa index ${REF}.
Hi,
I am running the
main_AmrPlusPlus_v2_withRGI_Kraken.nf
workflow, and I'm doing it with--host_index
.I'm not sure I'm doing things correctly, since the usage page says
--index
and not--host_index
.I just wanted to bring this up, because the
--help
says--host_index
, from the script.I would suggest a slight modification of the option, that could be easier to understand. Instead of having to declare all the index file using the
*
wildcard, it would be easier if people had to declare the index prefix including the path (like in bowtie2 for example).That way, the
--host
option would be automatically checked for the existence of an index by checking if it has the index files with the same prefix, and the user would only have to index the FASTA reference file usingbwa index ${REF}
.