-
Notifications
You must be signed in to change notification settings - Fork 49
Deepvariant subworkflow (issue #614) #651
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
base: dev
Are you sure you want to change the base?
Conversation
|
Hey @fa2k! How's this one coming along? I've got some time and can jump in if you're busy. 😄 |
Hi @ramprasadn it's nice that you're looking into this, but the subworkflow solution is proving to be a bit troublesome. DeepVariant made some large changes to the pipeline structure with version 1.8.0, but me and @fellen31 have updated the subworkflow so it works again. The work to integrate new versions was a bit too much, both for the subworkflow itself, and for the pipelines using it (none at the moment AFAIK), as they must update the ext.args config. Furthermore DeepVariant has added a "fast pipeline" with the new version, which is an alternative way to optimise the resource usage (instead of the subworkflow approach). The fast pipeline is not very user friendly at the moment, but could be improved. I'm supposed to do some benchmarking of the subworkflow vs the module, but I won't have time to do it any time soon, and I didn't plan to also include the "fast pipeline". It may be smart to wait for the next DeepVariant release, to get a feel for the amount of changes needed for the subworkflow, and whether the fast pipeline could be an alternative. |
Okay, I will just update the module to v1.8.0 so we can take advantage of the runtime reduction achieved with the small model for now. Like you said, lets wait for the for the next release to see what DeepVariant comes up with and then decide on how to move forward. |
This PR splits DeepVariant into three processes, to optimise the resource usage. (#614)
It doesn't support GPU out of the box, but I have added usage documentation for how to enable it.
PR checklist
nf-core lint
).nextflow run . -profile test,singularity --outdir <OUTDIR>
).nextflow run . -profile test_one_sample,singularity --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).