-
Notifications
You must be signed in to change notification settings - Fork 37
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
fix: parameters not resolving properly when igenomes are used #530
fix: parameters not resolving properly when igenomes are used #530
Conversation
|
@maxulysse @nvnieuwk what do you guys think? |
This does work if you work with and without igenomes? what if you supply a fasta from the cli or a params file? |
Yupe, works without igenomes as well.
|
Awesome! seems like a good solution then! |
I haven't tested using a params file, but parameters resolve fine when you supply a parameter via cli. So I don't see a reason why it wouldn't work with a params file 😄 |
PR checklist
Addresses https://nfcore.slack.com/archives/C04QR0T3G3H/p1709811356971549
Pretext: To illustrate the problem and the solution, I did a couple of test runs using the test config after setting ignore_igenomes to false. I also removed the bwa parameter from the nextflow.config, so we can see if it gets set to the value in igenomes.config.
Below is the list of resolved parameters as it enters the workflow in the current dev branch (notice the lack of bwa parameter in the list as it is not set anywhere).
Resolved parameters as it enters the workflow after the fix (notice the presence of bwa parameter in the list, and it has resolved to the right version on igenomes).
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile test_one_sample,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).