You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2020. It is now read-only.
At the moment, expected genotype calls are {0,1,2, etc} to denote different alleles
Technically there is nothing wrong with using {A,B,C, etc} calls (other than limiting the number of alleles to < 26). These could be parsed to the default integer allele states upon file read without much re-write.
But is it right to? Again, this would limit the number of alleles. And would make Merlin's ambiguous call flag A almost indistinguishable from allele call "A".
The text was updated successfully, but these errors were encountered:
At the moment, expected genotype calls are
{0,1,2, etc}
to denote different allelesTechnically there is nothing wrong with using
{A,B,C, etc}
calls (other than limiting the number of alleles to < 26). These could be parsed to the default integer allele states upon file read without much re-write.But is it right to? Again, this would limit the number of alleles. And would make Merlin's ambiguous call flag
A
almost indistinguishable from allele call "A".The text was updated successfully, but these errors were encountered: