-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gVCF vs VCF variant indexing #1620
Comments
Hi, I would need to see the actual records to comment, but what do you mean by "index"? |
with index what I meant is that the coordinates for the gVCF record look like is spanning two bases vs one base in the VCF. |
Records look like this! VCF: gVCF: |
I think this is normal for a gVCF, in this case the reference is 2 bases and one of the alleles is the generic <NON_REF>, which could be anything, so the variant site covers 2 bases. In the regular VCF there is only 1 alternate allele, and the actual variant can be non-ambiguously interpreted as the deletion of the "T". @lbergelson knows more about this than I do and might have a comment. |
Hi, I see some differences in how variants look when VCF vs gVCF are explored in IGV.
See example in the attached screenshot, positions look exactly in the actual record but index looks different for gVCF. Is this expected?
IGV version is 2.18.4
The text was updated successfully, but these errors were encountered: