Closed dmiller15 closed 4 years ago
Hmmm, something seems. bit off. In giving the precalc value, you got -contamination 0.009684066666666666
as what haplotype caller ends up running. When you run verifyBamID, you get -contamination 2.4251866666666667E-5
.
That precalculated value I handed in was a value from a different input here: https://cavatica.sbgenomics.com/u/kfdrc-harmonization/kf-reference-pipeline/tasks/6b6d3fed-f29f-4b26-8299-86549409336e/. I ran them concurrently so I didn't know what the value would be for this input at the outset. Wasn't too concerned about making nice data, just proving it worked.
Description
This PR creates a modern GATK HaplotypeCaller CRAM to gVCF workflow. Some features of the workflow:
Breakdown of other changes:
Closes https://github.com/d3b-center/bixu-tracker/issues/721
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
2.4251866666666667E-5
. This value matches exactly what was generated in the original harmonization process used to generate the CRAM (and ultimately its gVCF) here: https://cavatica.sbgenomics.com/u/kfdrc-harmonization/kf-reference-pipeline/tasks/e57126b9-d033-4642-8a7f-a0fd606406f3/stats/Test Configuration:
Checklist: