Nematode genome non-circularized #323
Replies: 4 comments 3 replies
-
Hi Juan, Thank you for reaching out! To ensure we're on the same page, could you please specify the file names you're visualizing when referring to the graphs? This will help clarify the context and allow for more accurate support. If a mitogenome with sufficient depth (aside from the 763 sample) does not circularize, it may be due to complex repeat structures within the genome. In such cases, GetOrganelle tends to export only the regions that are free of unresolved repeats, causing the connecting repeats to be chopped off. You should probably see them when you visualize the |
Beta Was this translation helpful? Give feedback.
-
Hi Dr. JianJun,
Thanks for your quick response.
It is my pleasure to help you clarify my case. The first graph is an attempt to assemble the mitogenome of Caenorhabditis elegans, it is 117 (C.ele.117. png).
It is a high-depth sequencing, which I used standard parameters, and as seen, Bandage visualization didn't show any repeat, like it has shown before when trying a mitogenome of a bat, or another nematode mitogenome (species 763 using standard parameters - max kmer 115).
[cid:41a65828-cb94-4c1d-8d2d-f648f79be8f3]
In this species, 763, when using the highest kmer value, 127, since I have 150 bp reads, that "repeat" disappeared:
[cid:89a62f26-f375-4a15-9363-53224069284f]
and the final fasta went from 12457 to 12469.
And as similar, with the C. elegans attempt, I don't get that "repeat" in red, and the genome is linear, and not circular.
[cid:5a559adf-e5f3-46a9-811e-0738041d4bb4]
Then, I tried the same with species 3391, using a longer kmer but the results didn't improve.
Next, I read that merging paired-end reads benefits genome assembly
https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0185056
[https://journals.plos.org/plosone/article/figure/image?id=10.1371/journal.pone.0185056.g006&size=inline]<https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0185056>
BBMerge – Accurate paired shotgun read merging via overlap<https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0185056>
journals.plos.org
So I thought that, with merged reads, perhaps it could benefit, make circularization more likely, but it didn't help much for species 763, but for 3391, the graph turned into a mess with several fragments, instead of the single one I got when using the trimmed unmerged reads:
With unmerged reads:[cid:129751da-2927-43d3-b11e-32aa93a8b76f]
(3391.115.png)
But assembly with the merged reads (3391.mrg.graph.png) it turned into a convoluted knot, with even some "repeat regions", which didn't appear when assembling using unmerged reads.
[cid:7179d232-d26c-4c57-af51-0bd9d1c8e818]
I thought that ok, for my species I might not be able to assemble a circular mitogenome because of depth, but that didn't occur with C elegans which had a depth of 232X.
I know that nematode mitogenome tend to rearrange a lot, but I don't understand why I get a circular for my longer bat mitogenome:
[cid:f1d2a80a-0617-4e0c-af16-30b072891a60]
but I get a linear for nematode.
I am eager to hear your comments and thoughts.
Sincerely & Thank you very much.
Juan Pablo Aguilar Cabezas
…________________________________
From: JianJun Jin ***@***.***>
Sent: Tuesday, April 2, 2024 3:34 PM
To: Kinggerm/GetOrganelle ***@***.***>
Cc: Aguilar Cabezas, Juan Pablo ***@***.***>; Author ***@***.***>
Subject: [External] Re: [Kinggerm/GetOrganelle] Nematode genome non-circularized (Discussion #323)
Use caution with links and attachments.
Hi Juan,
Thank you for reaching out!
To ensure we're on the same page, could you please specify the file names you're visualizing when referring to the graphs? This will help clarify the context and allow for more accurate support.
If a mitogenome with sufficient depth (aside from the 763 sample) does not circularize, it may be due to complex repeat structures within the genome. In such cases, GetOrganelle tends to export only the regions that are free of unresolved repeats, causing the connecting repeats to be chopped off. You should probably see them when you visualize the *.fastg file.
—
Reply to this email directly, view it on GitHub<#323 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJWD2VOTQHVGFBGUU43G2QTY3MI3XAVCNFSM6AAAAABFNWOXECVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSOBZGE3TG>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Let me be clear, please always specify the name of the graph file (not the sample) you loaded in Bandage along with each png image. BTW, I cannot see the image from your latest comment |
Beta Was this translation helpful? Give feedback.
-
Let me try to address your comment.
I loaded in bandage the fastg (and csv) from the longest kmer, located in the K115 or K127 folder in the extended_spades directory.
Juan Pablo Aguilar Cabezas
Ecology and Evolutionary Biology Ph.D. Candidate
Department of Biological Sciences
Ohio University, Athens OH
…________________________________
From: JianJun Jin ***@***.***>
Sent: Tuesday, April 2, 2024 9:12 PM
To: Kinggerm/GetOrganelle ***@***.***>
Cc: Aguilar Cabezas, Juan Pablo ***@***.***>; Author ***@***.***>
Subject: [External] Re: [Kinggerm/GetOrganelle] Nematode genome non-circularized (Discussion #323)
Use caution with links and attachments.
Let me be clear, please always specify the graph file you loaded in Bandage along with each png image
—
Reply to this email directly, view it on GitHub<#323 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJWD2VOIOHPVB2VCEROGVO3Y3NQR3AVCNFSM6AAAAABFNWOXECVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSOJRGE3TS>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Dear Dr. Jin,
Hope you are doing well. I am contacting you because I am working with nematodes, and I just recently found that their mitogenomes are very rearranged. I have sequenced two new families, and I have also used raw sequences with higher depth from a colleague working with C. elegans, and I was able to get the mitogenome, but while visualizing it with bandage, not of them are circular/ized.
117.get_org.log.txt
763.127.get_org.log.txt
Also, once I read, that merging reads, can benefit genome assembly stats, higher contiguity/less contigs. Thus, I tried merging PE-reads, with one of my species and got a very weird graph. It was very chaotic when I expected that the longer reads might help getting the circular genome.
Raw-reads
3391.get_org.log.txt
Merged reads
3391.mrg.get_org.log.txt
As you can see, with the merged reads, I even get a partially assembled contig, instead of an unique one. Any hint of why this behavior is happening?
I would appreciate if you could tell if you have tried a nematode before, and have succeeded getting a circular contig, and in my case, one species, the coverage isn't that high ~20X, but I was still able to get a single contig like the 117, the other species is higher (messier graph), which parameter I could try to optimize to get a circular mitogenome.
Thank you very much.
Juan Pablo
Beta Was this translation helpful? Give feedback.
All reactions