"constrained trio calling temporarily disabled"
https://github.com/samtools/bcftools/blob/develop/mcall.c#L1605C30-L1605C75
bcftools 1.23 released https://github.com/samtools/bcftools/releases/tag/1.23
"constrained trio calling temporarily disabled"
https://github.com/samtools/bcftools/blob/develop/mcall.c#L1605C30-L1605C75
So after much community backlash #GATK has reverted back to the ./. representation for no-calls.
The question is, will something like this occur again? and how many people have already switched away to other tools like #bcftools.
I know I have moved all my pipelines back to bcftools and honestly its brilliant.
What’s everyone’s thoughts and experience on merging large numbers of gvcf files? Currently I’m running #bcftools merge, but as a tree merge process (multiple smaller merges that then get merged together). I’ve seen there is #IMMerge which is meant to have speed improvements. Are there any other tools or hacks people are using? 🧬
G’day legends, if you are looking to just simply extract a subset of SNP positions from a VCF, bcftools -T (targets) is, by my own account, 3X faster than -R (regions). So unless you enjoy having a staring 👀 contest with your terminal, I suggest using it.
Now, before anyone jumps on the no no train 🚂 obviously, there are other functionality differences between targets & regions, but for this scenario, it does the job 👍
PR accepted ! option "--drop-genotypes" in #bcftools concat https://github.com/samtools/bcftools/pull/1911 🥳🥳