Update GATK to 4.6.0.0 in sv_pipeline_docker #719
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the version of GATK to 4.6.0.0 in
sv_pipeline_docker
. Note this is not the same asgatk_docker
, asgatk
is needed in some tasks that use GATK-SV code (e.g. svtk) and so it is built into thesv_base_docker
image.This addresses #81, but also the current commit has rotted with a dependency error, preventing new builds of
sv_base_docker
.Note that the newer version of
PrintSVEvidence
produces an index file with 0-based indexing. This required changing/moving sometabix
commands in the WDLs for consistency and to avoid wastefully regenerating the index. The 0-based indexing also caused problems with thesr-count
call inGenotypeBatch
, since the queries were off by 1 and this is the only place where tabix-based evidence queries require single-base precision.Tested
GenotypeBatch
against v0.28.1-beta with the "bwa-melt" test cohort. Discrepancies in the output were minor and could be explained by recent PRs (e.g. #618). Also testedGatherBatchEvidence
,GenerateBatchMetrics
,ResolveComplexVariants
, andGenotypeComplexVariants
which passed sanity checks.