Skip to content
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

Merged
merged 10 commits into from
Nov 16, 2023
Merged

VCFTOOLs site_pi and het options #62

merged 10 commits into from
Nov 16, 2023

Conversation

gq1
Copy link
Member

@gq1 gq1 commented Nov 7, 2023

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

Copy link

github-actions bot commented Nov 7, 2023

This PR is against the main branch ❌

  • Do not close this PR
  • Click Edit and change the base to dev
  • This CI test will remain failed until you push a new commit

Hi @gq1,

It looks like this pull-request is has been made against the sanger-tol/variantcalling main branch.
The main branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to main are only allowed if they come from the sanger-tol/variantcalling dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

Copy link

github-actions bot commented Nov 7, 2023

nf-core lint overall result: Passed ✅

Posted for pipeline commit 1882fef

+| ✅ 126 tests passed       |+
#| ❔  26 tests were ignored |#

❔ Tests ignored:

  • files_exist - File is ignored: CODE_OF_CONDUCT.md
  • files_exist - File is ignored: assets/nf-core-variantcalling_logo_light.png
  • files_exist - File is ignored: docs/images/nf-core-variantcalling_logo_light.png
  • files_exist - File is ignored: docs/images/nf-core-variantcalling_logo_dark.png
  • files_exist - File is ignored: .github/ISSUE_TEMPLATE/config.yml
  • files_exist - File is ignored: .github/workflows/awstest.yml
  • files_exist - File is ignored: .github/workflows/awsfulltest.yml
  • files_exist - File is ignored: assets/multiqc_config.yml
  • files_exist - File is ignored: conf/igenomes.config
  • nextflow_config - Config variable ignored: manifest.name
  • nextflow_config - Config variable ignored: manifest.homePage
  • files_unchanged - File ignored due to lint config: LICENSE or LICENSE.md or LICENCE or LICENCE.md
  • files_unchanged - File ignored due to lint config: .github/CONTRIBUTING.md
  • files_unchanged - File ignored due to lint config: .github/ISSUE_TEMPLATE/bug_report.yml
  • files_unchanged - File does not exist: .github/ISSUE_TEMPLATE/config.yml
  • files_unchanged - File ignored due to lint config: .github/PULL_REQUEST_TEMPLATE.md
  • files_unchanged - File ignored due to lint config: .github/workflows/branch.yml
  • files_unchanged - File ignored due to lint config: .github/workflows/linting.yml
  • files_unchanged - File ignored due to lint config: assets/email_template.html
  • files_unchanged - File ignored due to lint config: assets/sendmail_template.txt
  • files_unchanged - File does not exist: assets/nf-core-variantcalling_logo_light.png
  • files_unchanged - File does not exist: docs/images/nf-core-variantcalling_logo_light.png
  • files_unchanged - File does not exist: docs/images/nf-core-variantcalling_logo_dark.png
  • files_unchanged - File ignored due to lint config: lib/NfcoreTemplate.groovy
  • actions_awstest - 'awstest.yml' workflow not found: /home/runner/work/variantcalling/variantcalling/.github/workflows/awstest.yml
  • multiqc_config - 'assets/multiqc_config.yml' not found

✅ Tests passed:

Run details

  • nf-core/tools version 2.8
  • Run at 2023-11-16 09:49:57

@gq1 gq1 changed the base branch from main to dev November 7, 2023 21:46
@gq1
Copy link
Member Author

gq1 commented Nov 8, 2023

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.
It seems they have coped with all the output (big list) but not all the input yet.
https://nf-co.re/modules/vcftools

They did mention this in the module https://github.com/nf-core/modules/blob/18cd2206622dc606bbceea533c7823feb2a251db/modules/nf-core/vcftools/main.nf#L13

Copy link
Member

@muffato muffato left a 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

@muffato muffato added enhancement Improvement of the existing features feature Requests for new features user request Requests made by users and public labels Nov 10, 2023
@muffato muffato added this to the 1.1.0 milestone Nov 10, 2023
This was linked to issues Nov 10, 2023
@gq1
Copy link
Member Author

gq1 commented Nov 10, 2023

nf-core/modules#4319

@gq1 gq1 merged commit 3b3a745 into dev Nov 16, 2023
6 checks passed
@gq1 gq1 deleted the vcftools_site_pi_het branch November 16, 2023 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of the existing features feature Requests for new features user request Requests made by users and public
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Per site nucleotide diversity Add calculation for heterozygosity
2 participants