At the moment, the core haplotype calling algorithm considers only a collection of explicitly designated SNPs. But there is often rare/cryptic variation at non-target sites within the locus. This thread is a placeholder and a reminder to come back at some time in the future and implement features for calling SNPs (or maybe even small indels) at all sites in the reference.
Some folks argue that variant calls or perhaps even the entire locus sequence are the MH alleles of the future. I’m sympathetic on a philosophical level, but there are practical obstacles to actualizing that glorious future. What I propose here would be an incremental step in that direction, providing complete backwards and forwards compatibility for markers whose SNP definitions may change over time, but providing data to begin experimenting with comprehensive variant call sets at each locus.
For now, we’ll probably want to store variant calls separately from the MH allele tallies, along with the marker reference sequence.
At the moment, the core haplotype calling algorithm considers only a collection of explicitly designated SNPs. But there is often rare/cryptic variation at non-target sites within the locus. This thread is a placeholder and a reminder to come back at some time in the future and implement features for calling SNPs (or maybe even small indels) at all sites in the reference.
Some folks argue that variant calls or perhaps even the entire locus sequence are the MH alleles of the future. I’m sympathetic on a philosophical level, but there are practical obstacles to actualizing that glorious future. What I propose here would be an incremental step in that direction, providing complete backwards and forwards compatibility for markers whose SNP definitions may change over time, but providing data to begin experimenting with comprehensive variant call sets at each locus.
For now, we’ll probably want to store variant calls separately from the MH allele tallies, along with the marker reference sequence.