When the SVTYPE tag is defined and the variant REF/ALT alleles contain non-ATCG IUPAC nucleotide codes (such as N and R in the user's example), VEP 111 will try to parse the ALT allele as a SVTYPE and fail:
WARNING: line 1 skipped (3 90699772 MantaINS:2:34291:34291:1:0:0 ANNNNN...): ATCACAAATAGGTTCTGAGAATTATTCTGTCTAGTTTTTCTAGCGCCGTTTGAGGCCTATGGTAGAAAAGGGAATATCTTCATAGAAAAACGAGACAGAATAATTCTCAGAACCTATTTGTGATTTGTGCTT type is not supported
To avoid this issue, if the SVTYPE type is defined and if ALT does not resemble one of the VCF-supported SV types in ALT (i.e., starting with INS, DEL, INV, DUP or CN), then the SV type will be based on SVTYPE instead of ALT.
The warning message was also changed to be clearer:
WARNING: line 1 skipped (3 90699772 MantaINS:2:34291:34291:1:0:0 ANNNNN...): ANN is not a supported structural variant type
Testing
VEP should run with the following variants without returning any warnings:
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).