-
Notifications
You must be signed in to change notification settings - Fork 244
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
consensus --missing
not compatible with gvcf blocks
#2350
Comments
Thank you for the issue, this is now possible. Note, however, that the change will take effect only after samtools/htslib#1879 is merged |
samtools/htslib#1879 has now been merged, but it looks like there's an out of bounds read in |
The out of bounds read was caused by stale variant type data. See samtools/htslib#1883 for a fix. |
@pd3 Hi, thanks for the feature, it works well in many of my cases. However, when I apply
While the expected result will be
(The missing gvcf block range from position 3 to 5, while the reference segment range to 4, so two Is it possible to make it? |
bcftools version: 1.21
Doing consensus with flag
--missing
will throw error on missing (./.
) gvcf blocks. Here is a minimal reproducible example:test.vcf.gz
:Inline commands to reproduce, for your convenience
Running command
will throws error:
While the expected output is
Or is there any other way to preserve missing sites when performing consensus on gvcf files?
The text was updated successfully, but these errors were encountered: