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

fix check for panel of normals and add in log #319

Merged
merged 4 commits into from
Oct 28, 2024

Conversation

sorelfitzgibbon
Copy link
Contributor

Description

Running without a panel of normals was triggering a warning. This fixes that and adds the specified panel of normals to the Mutect2 log output.

Closes #308

Testing Results

without panel of normals

NFTest a_mini-all-tools-std-input
/hot/software/pipeline/pipeline-call-sSNV/Nextflow/development/unreleased/sfitz-fix-pon-check/log-nftest-20241025T230650Z.log

with panel of normals

config: /hot/code/sfitzgibbon/GitHub/uclahs-cds/pipeline-call-sSNV/test/config/untracked/a_mini-all-tools-pon.config
yaml: /hot/code/sfitzgibbon/GitHub/uclahs-cds/pipeline-call-sSNV/test/yaml/a_mini_n2-std-input.yaml
log: /hot/software/pipeline/pipeline-call-sSNV/Nextflow/development/unreleased/sfitz-fix-pon-check/slurm-230914.out

Checklist

  • I have read the code review guidelines and the code review best practice on GitHub check-list.

  • I have reviewed the Nextflow pipeline standards.

  • The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].

  • I have set up or verified the branch protection rule following the github standards before opening this pull request.

  • I have added my name to the contributors listings in the manifest block in the nextflow.config as part of this pull request; I am listed already, or do not wish to be listed. (This acknowledgement is optional.)

  • I have added the changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.

  • I have updated the version number in the metadata.yaml and manifest block of the nextflow.config file following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)

  • I have tested the pipeline on at least one A-mini sample.

Copy link
Contributor

@yashpatel6 yashpatel6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I think the configtests need an update

Copy link

Bleep bloop, I am a robot.

Alas, some of the Nextflow configuration tests failed!

test/configtest-F16.json

@ ["params","panel_of_normals_vcf"]
+ ""

test/configtest-F32.json

@ ["params","panel_of_normals_vcf"]
+ ""

If the above changes are surprising, stop and determine what happened.

If the above changes are expected, there are two ways to fix this:

  1. Automatically: Post a comment starting with "/fix-tests" (without the quotes) and I will update the tests for you (you must review my work afterwards).
  2. Manually: Follow these steps on Confluence.

@sorelfitzgibbon
Copy link
Contributor Author

/fix-tests

Copy link

Bleep bloop, I am a robot.

I have updated all of the failing tests for you with b03b049. You must review my work before merging this pull request!

@wiz-inc-8da00b022c
Copy link

wiz-inc-8da00b022c bot commented Oct 28, 2024

Wiz Scan Summary

Scan Module Critical High Medium Low Info Total
IaC Misconfigurations 0 0 0 0 0 0
Vulnerabilities 0 0 0 0 0 0
Sensitive Data 0 0 0 0 1 1
Secrets 0 0 0 0 0 0
Total 0 0 0 0 1 1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

@sorelfitzgibbon sorelfitzgibbon merged commit 51d781a into main Oct 28, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

running without a panel of normals now elicits a WARNING
2 participants