-
Notifications
You must be signed in to change notification settings - Fork 711
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
RC 3.16.0 #1395
Conversation
Co-authored-by: Matthias Zepper <[email protected]>
patch bedtools/genomecov to use quay.io to solve issue with nf-core download
|
Improve pipeline level snapshots
prepare RC 3.16.0
What do we do with #1369 ? @siddharthab made such an awesome effort, and it is essentially done - the tool is just horribly slow on transcriptomic alignments, so we are since weeks waiting that the tool's author will merge a tiny PR that fixes that. I am seriously considering forking the repo and merge it there...because I so badly want that tool in the pipeline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only thing I would say I'm unhappy with is the extremely minimal description of the input file for --kraken2_db
.
A kraken2 database is not the same as a bracken database (bracken requires multiple extra files alongside the normal kraken2 database files), and the Ben Langmead things I guess is being assumed is the ones most people use are not actually really the gold standard (there aren't any).
I would suggest improving the description of what gets supplied to that paramneter (a tar.gz) and also in usage
explain further what is accepted and when depending on if you're supplying kraken vs bracken parameters.
But otherwise everything else is self-explanatory (thus the approval)
| `Bracken` | ----------- | 2.9 | | ||
|
||
> **NB:** Dependency has been **updated** if both old and new version information is present. | ||
> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the line breaks here
> **NB:** Dependency has been **updated** if both old and new version information is present. | ||
> | ||
> **NB:** Dependency has been **added** if just the new version information is present. | ||
> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> |
}, | ||
"kraken_db": { | ||
"type": "string", | ||
"description": "Database when using Kraken2/Bracken for contaminant screening.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In what form? Should this be a directory or a tar.gz file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OR both? The Ben Langmead versions are tar.gz for example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@egreenberg7 any idea about that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll make sure to include the answer to that when we make tests for this new feature in the next release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be a tar.gz file since the nf-core Kraken2 and Bracken modules use the --gzip-compressed
option. It probably should be clarified that kraken2 and bracken databases are distinct, but they are often zipped together (as in the pre-built indices). A separate --bracken_db
option potentially could be added.
While the pre-built files are not gold standard, they provide a quick/convenient option for people who want to run contamination detection without getting into the weeds of the tools. I'll note that I did not offer the ability to make a standard database in an indexing run of the pipeline because it is so much slower than just downloading pre-built indices (and rather computationally expensive).
In any case, @jfy133 has much more experience than me with metagenomics tools, so I would defer to any changes he recommends to either the Usage tab or the input
//Check that Kraken/Bracken parameters are not provided when Kraken2 is not being used | ||
} else { | ||
if (!params.bracken_precision.equals('S')) { | ||
brackenPrecisionWithoutKrakenDBWarn() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is a function here really necessary? You only use it once...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good spot, that'll be looked after in some slight refactoring, but out of scope for this release
This was intended to be just a patch release, Kraken2/Bracken was already in so we release as #1369 will be included in the next release |
Co-authored-by: James A. Fellows Yates <[email protected]>
Fine with me. BTW: You are not very patriotic, are you? Why would you chose "Fire" as an element, if you could have chosen Francium and honor your home country 😉 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weeee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, so much ignored!
Release Candidate 3.16.0 aka Fire Ferret
Merge only once #1394 is merged
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).