Fix SVTYPE when using IUPAC nucleotide codes #1636
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.
Fixes #1631
Motivation
When the
SVTYPE
tag is defined and the variantREF
/ALT
alleles contain non-ATCG
IUPAC nucleotide codes (such asN
andR
in the user's example), VEP 111 will try to parse theALT
allele as aSVTYPE
and fail:To avoid this issue, if the
SVTYPE
type is defined and ifALT
does not resemble one of the VCF-supported SV types inALT
(i.e., starting withINS
,DEL
,INV
,DUP
orCN
), then the SV type will be based onSVTYPE
instead ofALT
.The warning message was also changed to be clearer:
Testing
VEP should run with the following variants without returning any warnings:
The output should return that these are all intergenic variants (instead of no consequence at all).