-
Notifications
You must be signed in to change notification settings - Fork 3
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
VCFTOOLs site_pi and het options #62
Conversation
…de diversity and heterozygosity
Add include_positions and exclude_positions for the whole workflow.
This PR is against the
|
|
Currently nf-core vcftools module has 3 inputs, I am not sure it is a good idea to to push the patch here to them. They did mention this in the module https://github.com/nf-core/modules/blob/18cd2206622dc606bbceea533c7823feb2a251db/modules/nf-core/vcftools/main.nf#L13 |
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.
That's how I expected vcftools
to be modified. I think you can propose that to nf-core.
The thing I'm wondering: does it make sense to run vcftools on both the VCF and gVCF files ? In the small test, the outputs are identical for the individual BAM and CRAM files but not the combined file.
I'll start the "full test" to check on it too
PR checklist
nf-core lint
).nextflow run . -profile 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).