-
Notifications
You must be signed in to change notification settings - Fork 71
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
Mutation linkage #234
Comments
The file jj4_mitogenome.fasta, was it produced from the same dataset with NOVOPlasty? |
First of all, thank you for your reply, I will describe my situation specifically according to your reply. |
I checked the files you send, indeed no NUMTs were detected. There were quite a lot of possible heteroplasmy positions, although I think some could be sequencing errors. But again it is not designed to find NUMTs, so very recent NUMTs that have no sequence difference with the original mitochondrial sequence will never be detected. I also noticed that your sequencing depth is not that high, how much coverage are you expecting to have of the nuclear genome? |
My sequencing depth for the nuclear genome is 30x
…---- Replied Message ----
| From | Nicolas ***@***.***> |
| Date | 11/13/2024 16:16 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [ndierckx/NOVOPlasty] Mutation linkage (Issue #234) |
I checked the files you send, indeed no NUMTs were detected. There were quite a lot of possible heteroplasmy positions, although I think some could be sequencing errors. But again it is not designed to find NUMTs, so very recent NUMTs that have no sequence difference with the original mitochondrial sequence will never be detected.
I also noticed that your sequencing depth is not that high, how much coverage are you expecting to have of the nuclear genome?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
If that is the case there is definitely not many NUMTs, because it would have found it quite easily, 0.006 is way to loo low, NUMTs would have a much higher fraction. But if there are no ancient NUMTs, why would you expect more recent NUMTs? You can always align all the reads to mitochondrial assembly and visually inspect in IGV if there are possible NUMTs aligned.. |
Thank you very much for your reply. I think what you said makes sense. I will try using IGV or other software to assemble numt. Additionally, there is one more question that I am very curious about. In the log of this software, there are listed both aligned reads and assembled reads. If I could identify these two types of reads based on the log file and remove the assembled reads from the aligned reads, would it be better to use the newly obtained reads to assemble numt. Or I think that in the actual assembly process, some reads from numt will also participate in the assembly process (such as sequences that are very similar or even completely identical to mitochondrial homologous sequences to construct consensus sequences)
…---- Replied Message ----
| From | Nicolas ***@***.***> |
| Date | 11/13/2024 16:40 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [ndierckx/NOVOPlasty] Mutation linkage (Issue #234) |
If that is the case there is definitely not many NUMTs, because it would have found it quite easily, 0.006 is way to loo low, NUMTs would have a much higher fraction. But if there are no ancient NUMTs, why would you expect more recent NUMTs? You can always align all the reads to mitochondrial assembly and visually inspect in IGV if there are possible NUMTs aligned..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi, Aligned reads could indeed contain some NUMTs sequences, bit there not being stored so you can't retrieve them... |
Hello, I want to use novoplsty to assemble numts, but the result I got did not store numts file, the following is my configuration file and the result I got, the version I used is NOVOPlasty4.3.5.pl, what is the cause?
The text was updated successfully, but these errors were encountered: