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
merge issues with monoallelic positions #412
Comments
Running |
Indeed, this is a bug. There is a new version of |
Thanks! Are the fixes in the experimental fork being merged back here? |
Output looks wonky. Each GT at the same position is now on it's own line. |
Apologies, the bug did not show up in my tests. This commit should fix it pd3@9746e17 RE your question about merging the fixes back into the main repository: The |
Ah, thanks. I'll use the experimental for merging. I'm still getting multiple lines for the same position. |
Major overhaul of merge to accommodate merging of gvcf files produced by the new bcftools mpileup. Update also closes a number of long standing issues. Closes #412, #408, #361, #296 and possibly resolves #401 [NEWS] Major overhaul of `bcftools merge` to allow merging of gvcf files produces by `bcftools mpileup`
Major overhaul of merge to accommodate merging of gvcf files produced by the new bcftools mpileup. Update also closes a number of long standing issues. Closes #412, #408, #361, #296 and possibly resolves #401 [NEWS] Major overhaul of `bcftools merge` to allow merging of gvcf files produces by `bcftools mpileup`
Major overhaul of merge to accommodate merging of gvcf files produced by the new bcftools mpileup. Update also closes a number of long standing issues. Closes #412, #408, #361, #296 and possibly resolves #401 [NEWS] Major overhaul of `bcftools merge` to allow merging of gvcf files produces by `bcftools mpileup`
I'm not quite sure how to deal with the following scenario.
I'm merging lots of vcf's. Some vcf's have the REF homozygotes called with no ALT specified. When merging using
-m none
, positions with no ALT don't seem to get merged properly. i.e. each observed genotype at the same position ends up on it's own line.How might I avoid this so that the merging creates one line per position. I guess this requires two pieces of logic. First that the mono-allelics get merged and second that mono-allelics can be merged with bi-allelics.
If this can't be done via merging is there a way to resolve and collapse the variants using
norm
. Conventional multi-allelics should be split across multiple lines.example output:
https://gist.github.com/655c3c579098aa41881c15c68a5aa5cd
The text was updated successfully, but these errors were encountered: