Adjusted handling of compressed tar archive containing kraken2 database #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjusted handling of the compressed tar archive file containing the kraken2 database in the process
kraken2_db_preparation
. So far it was assumed that the name of the contained folder within the tar archive equals the base name of the compressed tar archive file. For the provided MiniKraken2 database this is not always the case, i.e. sometimes only a prefix matches but without a consistent pattern (see also https://ccb.jhu.edu/software/kraken2/index.shtml?t=downloads).Since I did not want to make any further assumptions on the folder name, I changed this to use all *.k2d in any contained folder, assuming each provided db file contains exactly one folder with *.k2d files.
Additionally I updated the links in the help and documentation to the minikraken2 database, which was recently updated.
PR checklist
nextflow run . -profile test,docker
).nf-core lint .
).docs
is updatedCHANGELOG.md
is updatedREADME.md
is updatedLearn more about contributing: https://github.com/nf-core/mag/tree/master/.github/CONTRIBUTING.md