-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add ampcombi 2.0.1 #427
Add ampcombi 2.0.1 #427
Conversation
|
@nf-core-bot fix linting |
Uhhh that's interesting... why don't we have any CI tests 😅 |
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.
AMPcombi itself is not updated in this PR, just the download script ... is that correct?
# This source code is licensed under the MIT license | ||
######################################### | ||
|
||
# TITLE: Download the DRAMP database if input db empty AND and make database compatible for diamond | ||
# TITLE: Download the reference database specified by the user. |
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.
Shouldn't this script be wrapped up within AMPcombi itself, e.g. ampcombi download ...
?
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.
It is but u remember the issue with it downloading the ref. database every time for each sample? We did that to only let it run once in the pipeline. I didnt add a submodule for downloading the database, its wrapped in parse_table sub module
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.
Also as i wrote in the PR comment, for this PR to run as it should we still need to update the module to v2.0.1, which has a sep. PR open in modules ;)
Was wondering the same, maybe because Im pushing into your branch and not the dev ? |
That shouldn't make s difference... But let's see once it's merged into the template update branch... Ping me for re-review once you've updated and we see what happens |
@nf-core-bot fix linting |
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.
@Darcy220606 where are the ampcombi 2.0 modules themselves? Or is this just the download script
@jfy133 the Ampcombi 2.0 modules are in a separate PR, here: nf-core/modules#7142 |
Ah ok! Then we can wait for them to go in and then update this PR :) |
Initial review of that just done, and back to conferencing |
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.0.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
@jfy133 All the modules are updated in the PR and the new version runs locally fine. |
Still only thre checks?! Wtf?! |
Let's assume it's OK... |
You can merge away @Darcy220606 ! |
PR checklist
This PR is dependent on ampcombi2 module update in nf-core/modules#7142, once that is approved the version bump can be done in this PR as well. This was tested locally with manual version bump.
This PR also addresses and closes issue #423.
👽👽👽👽👽👽👽👽👽 Still TODO
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).