-
Notifications
You must be signed in to change notification settings - Fork 240
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
[W::vcf_parse] Extreme INFO/MPOS value encountered and set to missing at chr1:17082839 #1148
Comments
Can you show the value of INFO/MPOS at that position before and after? Also, important, what version of htslib+bcftools are you running? Make sure to test with 1.10.2 or the latest github version. |
OK! before
after
i think this is perfectly match each other. |
The error message and your data are consistent and quite clear: |
Note this is caused by a bug in Mutect2. More information and background here: The change in bcftools / htslib is that with extra validation it is not spotted these illegal values and issuing a warning. Older versions just truncated or wrapped around the data silently. |
OK! happy new year! Jeongmin. |
Hi, Happy new year!
i ran bcftools to parse tumor sample of somatic vcf.
but it returned warning message like below
my code is
bcftools view -s TNB_17_tumor TNB_17.mutect2.filtered.vcf.gz > TNB_17.mutect.tumor.vcf
i have a look input vcf and out vcf file but i don't know what is difference among them
and even at chr1:17082839 the line is same!
what is the problem?
Thanks!
The text was updated successfully, but these errors were encountered: