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

The genome has been circularized, but 2 different contigs #224

Open
LiviaT93 opened this issue Feb 22, 2024 · 5 comments
Open

The genome has been circularized, but 2 different contigs #224

LiviaT93 opened this issue Feb 22, 2024 · 5 comments

Comments

@LiviaT93
Copy link

I am assembling turtles mitogenomes and in some cases the output I obtain is a "Circularized genome", actually made up of 2 non overlapping contigs: in all these cases, the interruption is in correspondence of the Val tRNA. In the end, I managed to circularized all my samples in one single contig by heightening the kmers and the genome range, but I am willing to understand why this interruption in assembly occurs and whether this might be indicative of some noticeable feature of the mitogenome in that point. Do you have any suggestion?

@ndierckx
Copy link
Owner

Could you send me your results because it is hard to tell otherwise?

@LiviaT93
Copy link
Author

LiviaT93 commented Feb 29, 2024 via email

@ndierckx
Copy link
Owner

ndierckx commented Mar 3, 2024

In this case, the AT repeat caused the assembly to stop, illumina quality and depth usually drops a lot there. If the assembly is uncertain, it will use the paired reads information to jump the problematic region and continue from there in both senses. Sometimes it merges automatically, sometimes it asks you to do manually. I guess the second contig also started with the AT repeat?

@LiviaT93
Copy link
Author

LiviaT93 commented Mar 4, 2024 via email

@ndierckx
Copy link
Owner

I can only tell why it terminated by seeing the extended log file, need to run it with that option set to 1
If the question is biologically, I can't help you there, I am not a specialist

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