-
Notifications
You must be signed in to change notification settings - Fork 90
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
100s of chimeric mitochondrial genome contigs and same region duplicated in 2 contigs #68
Comments
Hifiasm may produce different copies of mitochondria. That may be caused by heteroplasmy. However, in general, reference-based analysis may not be a good way to understand a new sample:
Also a question: are you sure the input yeast samples come from nearly identical strains? Hifiasm is so sensitive that it will put tiny differences between strains into different contigs. |
For plants I've seen even a thousand contigs being partly the chloroplast.
I reasoned that because of excessive coverage of the plastids, even common
or rare systematic errors end up in different contigs. ( among
heterogeneity in the sample itself).
The coverage according to hifiasm is mostly 0 or 1 on these contigs.
Maybe you have similar issues with the mitochondria? What if you map all
your input hifi data to a single contigs that represents the mtDNA?
…On Wed, 27 Jan 2021, 22:47 rb-commits, ***@***.***> wrote:
Thanks for the quick response. This organism is dikaryotic (i.e. they have
two separate nuclei), with a high level of heterozygosity between two
haplotypes (0.84 SNP/Kb). I was wondering if those two contigs (in the
left) are actually haplotypes (see the dot plots).
[image: image]
<https://user-images.githubusercontent.com/78109099/106058147-78af4980-60b6-11eb-95b8-332a4b9b2845.png>
There are not only 2 contigs of mitochondria but in 100s. I haven't
checked the read depth for those mitochondrial contigs. I will check it and
will let you know.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARZCFIZJB753EX3TSJWAJDS4CCY3ANCNFSM4WV4OFKQ>
.
|
The text was updated successfully, but these errors were encountered: