Skip to content
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

Inconsistent output of mitochondrial SNPs in Ancestry/23andme merge #65

Closed
GerardManning opened this issue Mar 29, 2020 · 1 comment
Closed
Milestone

Comments

@GerardManning
Copy link

Ancestry reports mitochondrial (MT/Chr26) SNPs as diploid (e.g. "GG", with two identical alleles), even though there is just one mitochondrial genome, with multiple copies. 23andme reports as haploid (e.g. "G"). When 23andme and Ancestry files are merged in lineage, the csv output has a single allele for all 23andme SNPs but two alleles for any that are present on Ancestry (including SNPs present on both).

Suggest that, for consistency, all MT SNPs be reported with a single allele, and any heterozygosity in Ancestry calls (due to heteroplasmy, which I've never yet seen) be reported as an error.

@apriha apriha transferred this issue from apriha/lineage Mar 29, 2020
@apriha
Copy link
Owner

apriha commented Mar 29, 2020

Like deduplicate_XY_chrom, this could be addressed in a similar manner with deduplicate_MT_chrom (new parameter to SNPs).

apriha added a commit that referenced this issue Jul 24, 2020
@apriha apriha added this to the 2.0.0 milestone Aug 15, 2020
@apriha apriha closed this as completed Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants