-
Notifications
You must be signed in to change notification settings - Fork 127
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
migration to DSL2 #104
migration to DSL2 #104
Conversation
fix docs
Markdown linting is failingTo keep the code consistent with lots of contributors, we run automated code consistency checks.
Once you push these changes the test should pass, and you can hide this comment 👍 We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help! Thanks again for your contribution! |
YAML linting is failingTo keep the code consistent with lots of contributors, we run automated code consistency checks.
Once you push these changes the test should pass, and you can hide this comment 👍 We highly recommend setting up yaml-lint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help! Thanks again for your contribution! |
…skipping now defaults to false for all steps
…orced directory path type for some parameters cited as paths
… bisects JSON display problem
…N display problem
…sects JSON display problem
…re before further debugging
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
Co-authored-by: Kevin <klkeys@users.noreply.github.com>
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.
Huge work, very nice! 😄
Most of my comments are related to the new way of reporting versions, although there are some others related to more general stuff.
Also, I was wondering whether some of the local modules (e.g. bowtie/build and bowtie/align) could not be used from nf-core modules instead, but might be that I am not aware of all the details and that it is not possible to use them in this pipeline.
Almost there 🚀
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.
Great work!! 🚀 Just a couple of minor things, mostly regarding versioning (which I see now also Jose has reviewed already). I think adding the citations would be fairly important too.
params.samtools_stats_options = [:] | ||
params.table_merge_options = [:] | ||
|
||
include { PARSE_FASTA_MIRNA as PARSE_MATURE |
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.
Maybe align for readability
I will wait until Joses / Frederikes requests are accepted / discussed & then have a look afterwards - please ping me then here directly or via Slack 👍🏻 |
Co-authored-by: Jose Espinosa-Carrasco <kadomu@gmail.com>
Co-authored-by: Jose Espinosa-Carrasco <kadomu@gmail.com>
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
Co-authored-by: Jose Espinosa-Carrasco <kadomu@gmail.com>
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
Thanks @apeltzer. Some modules are local even if nf-core has similar modules because there is something unique to smrnaseq and it would take some evaluation to do the adaptation. I am leaving the versioning, so @JoseEspinosa can make the first change to use the YAML format, and I can then modify all the local modules to that format as well. The plan was to merge, and the @JoseEspinosa will make another PR with the versioning and I will work on top of that. I hope that is ok for everybody else. As well, there is a final module to add, but I need to do the docker containers, so I am skipping it here. (EDGER module in mirna_quant.nf) Thanks! |
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.
Looks good :) Great work 🥳 , and as discussed remaining things can go on top of the versioning PR
include { saveFiles; initOptions; getSoftwareName } from './functions' | ||
|
||
params.options = [:] | ||
options = initOptions(params.options) |
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.
Commit this?
PR checklist
When merging, the test config files need to point to the main branch of the datatest repository and for that this PR needs to be merged: nf-core/test-datasets#363
Note that the versions are still in TXT format because I wasn't sure on how to get it working with YML but maybe that could be another PR if it is the only thing...
scrape_software_versions.py
nf-core lint .
).nextflow run . -profile test,docker
).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).