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

Mutation linkage #234

Open
zhangqi123-gif opened this issue Nov 4, 2024 · 7 comments
Open

Mutation linkage #234

zhangqi123-gif opened this issue Nov 4, 2024 · 7 comments

Comments

@zhangqi123-gif
Copy link

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?
479faff333548d137729a3a4a809122
8620db1977bcdfc6cd9b138e92ac850

@ndierckx
Copy link
Owner

ndierckx commented Nov 5, 2024

The file jj4_mitogenome.fasta, was it produced from the same dataset with NOVOPlasty?
And are you expecting to find NUMTs, because it is not abnormal to not find NUMTs...
Because it designed to find heteroplasmy not NUMTs, so only recent NUMTs will interfere with the heteroplasmy detection and thereby detected with this method, ancient NUMTs will probaply be removed before the NUMT assembly module is activated

@zhangqi123-gif
Copy link
Author

First of all, thank you for your reply, I will describe my situation specifically according to your reply.
Yes, jj4_mitogenome.fasta was produced from the same dataset with NOVOPlasty,and I really want to find all NUMTs, especially ancient NUMTs. After reading your reply, I understand why I can't find NUMTs, which makes me a little sad.
In addition,i have two questions to confirm. First, if my jj4_mitogenome.fasta has used the same dataset but the assembly software has not used NOVOPlasty, can I also use the mitochondrial genome generated by this procedure? The second problem is that my output file should be output as a blank numtfile or no numtfile at all.

@ndierckx
Copy link
Owner

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?

@zhangqi123-gif
Copy link
Author

zhangqi123-gif commented Nov 13, 2024 via email

@ndierckx
Copy link
Owner

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..

@zhangqi123-gif
Copy link
Author

zhangqi123-gif commented Nov 17, 2024 via email

@ndierckx
Copy link
Owner

Hi,

Aligned reads could indeed contain some NUMTs sequences, bit there not being stored so you can't retrieve them...
But I don't think filtering those out will help assembling NUMTs. Maybe there even are no NUMTs...

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