The nt database is already present on our cluster for various applications. I'd like to avoid re-downloading nt to build its kraken2 index to avoid having a duplicate copy of nt and also so that all our uses of nt use the same version of the database.
would it be possible to be more lenient with the kraken2-build --add-to-library command, as is the case when downloading nt with the kraken2-build --add-to-library command?
The nt database is already present on our cluster for various applications. I'd like to avoid re-downloading nt to build its kraken2 index to avoid having a duplicate copy of nt and also so that all our uses of nt use the same version of the database.
would it be possible to be more lenient with the
kraken2-build --add-to-librarycommand, as is the case when downloading nt with thekraken2-build --add-to-librarycommand?