How Does Left-Alignment Work For Indels? Does It Address All Complicated Issues With Indel Representation In Vcf File?
1
2
Entering edit mode
10.3 years ago
Duck ▴ 40

I can vaguely guess its meaning but want to know, at least, how it works in different situations. Besides, after left alignment, can we write an indel in VCF file in a unique way?

Thank you!

ngs indel vcf • 5.2k views
ADD COMMENT
0
Entering edit mode

Did you see indel left/right alignment and http://www.broadinstitute.org/gatk/gatkdocs/org_broadinstitute_sting_gatk_walkers_variantutils_LeftAlignVariants.html?

Note that this tool cannot handle anything other than bi-allelic, simple indels. Complex events are written out unchanged.

That might answer the second part of your question.

ADD REPLY
0
Entering edit mode

Thanks, Mike!

After reading your links, I learned that how left-alignment works in a deletion occurring in a repeat region. However, I guess there are more situations. For example, we could have an insertion in a repeat region: ATGATG(GCG)GCGGCGTAGTAG, where (GCG) is an insertion. How would this be handled by left-alignment?

ADD REPLY
5
Entering edit mode
7.9 years ago
Len Trigg ★ 1.6k

In terms of providing an actual answer here for people arriving from google, the short answer is no, left alignment does not address complicated issues with indel representation in VCF files. It does help somewhat, but there are plenty of cases where simple normalization tools do not produce a unique variant representation. (As a side note, left-aligning simple indels is an unstated convention in VCF, and in contrast, HGVS guidelines state that indels should be right-aligned in the context of the genetic transcript).

Since there is no easy answer to representing variants uniquely, the state of the art is to perform variant comparisons using haplotype-aware tools such as rtg vcfeval, hap.py, or vgraph.

ADD COMMENT

Login before adding your answer.

Traffic: 2670 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6