-
Notifications
You must be signed in to change notification settings - Fork 16
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
Verification Report [v12.0.2] #1204
Labels
Verification Report
Report for validating minor and patch releases
Comments
ivadym
added
the
Verification Report
Report for validating minor and patch releases
label
Jul 19, 2023
Merged
10 tasks
Looks great, approved! |
Deployed:
|
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Balsamic Verification Report
Release Information
Person(s) involved in the development of new release
Summary
After adding TIDDIT tumor normal filtering, a bug was identified in ticket Ticket #248220. Consequently, there are issues processing the SV VCF with other tools.
These are the goals of this verification:
SV.somatic.<case-id>.svdb.clinical.filtered.pass.vcf.gz
) to ensure its correctness (only relevant for WGS tumor normal analyses).balsamic
andvarcall-cnvkit
containers.Changelog
S_balsamic
environmentedit_vcf_info.py
script behave as expectedvarcall-cnvkit
container behave as expectedPre-Verification Checklist
Before proceeding with the verification process, ensure that the following tasks have been completed:
Install Balsamic in stage and production environments in hasta and build its cache.
Confirm the availability of necessary resources, such as test cases.
Review the changelog and ensure all changes and updates are documented:
Set up the stage environment with the necessary software and configurations:
Verification Results
Workflow Integrity Verification Cases
acetuna
civilsole
PCT_60X=0.004532
)fleetjay
PCT_60X=0.00836
)setamoeba
unitedbeagle
uphippo
GC dropout=1.650392
andPCT_TARGET_BASES_1000X=0.861996
)equalbug
GC_DROPOUT=1.087173
andRELATEDNESS=-0.524
)Test: correctness of the SV VCF filtered file for WGS TN analysis
fleetjay
Test: pydantic version is <2.0 in
S_balsamic
environmentTest: rules using the
edit_vcf_info.py
script behave as expectedsetamoeba
{var_type}.somatic.{case_name}.vardict.research.filtered.pass.vcf.gz
and compare file-sizes past and current versionunitedbeagle
{var_type}.somatic.{case_name}.vardict.research.filtered.pass.vcf.gz
, and compare file-sizes past and current versionTest: rules using
varcall-cnvkit
container behave as expectedsetamoeba
CNVkit
dependencies, keeping the sameCNVkit
version.CNVkit
tumor-only output should remain unaffected. Output files identical to those in version12.0.1
.unitedbeagle
CNVkit
dependencies, keeping the sameCNVkit
version.CNVkit
tumor-normal output should remain unaffected. Output files identical to those in version12.0.1
.uphippo
CNVkit
dependencies, keeping the sameCNVkit
version.CNVkit
UMI tumor-only output should remain unaffected. Output files identical to those in version12.0.1
.equalbug
CNVkit
dependencies, keeping the sameCNVkit
version.CNVkit
UMI tumor-normal output should remain unaffected. Output files identical to those in version12.0.1
.Issues Identified
No issues identified.
Recommendations
Conclusion
The verification process for Balsamic v12.0.2 was conducted to ensure the integrity and correctness of the patch. The primary objective was to validate the format of the header in the SV VCF (
SV.somatic.<case-id>.svdb.clinical.filtered.pass.vcf.gz
) for WGS tumor-normal analyses and to verify the integrity of different analysis types after updating thebalsamic
andvarcall-cnvkit
containers.Furthermore, no issues were identified during the verification process. As a result, the Balsamic Version 12.0.2 patch release is ready for deployment.
Approval
Deployment
The text was updated successfully, but these errors were encountered: