You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to find the mitochondrial sequences in my assembly.
I assembled CLR PacBio reads using CANU for a mollusc genome.
As reference I used 2 mitochondrial genomes of the same species and I used the genetic code 5 (Mito Invertebrates), but Mitofinder said that it could not find mitochondrial sequence in contigs less than 25 000 bp.
Does anyone know what is happening ? Is it better to use MitoFinder on the reads for that particular case ?
Thanks for your help
Aurélien
The text was updated successfully, but these errors were encountered:
There are two possibilities here. Either CANU discarded the mitochondrial sequences due to their suspicious coverage (i.e. really high compared to genomic sequences), or some chimeric sequences have been created by CANU. In that case, you can allow MitoFinder to search for longer sequences (--max-contig-size option) and see if several mitogenomes have been concatenated during the assembly step.
Unfortunately, MitoFinder is not designed yet to handle long-reads data. Starting from reads is therefore not possible in your case. You can try to assemble your reads with an alternative assembler ...
Thanks for this I was able to fetch the contigs but MitoFinder in the raw CANU assembly. My guess is that it was probably eliminated by purge_dups because it has a filter on coverage.
however, MitoFinder could not circularize it.
I there something i can do to help the circularization ?
Hello,
I tried to find the mitochondrial sequences in my assembly.
I assembled CLR PacBio reads using CANU for a mollusc genome.
As reference I used 2 mitochondrial genomes of the same species and I used the genetic code 5 (Mito Invertebrates), but Mitofinder said that it could not find mitochondrial sequence in contigs less than 25 000 bp.
Does anyone know what is happening ? Is it better to use MitoFinder on the reads for that particular case ?
Thanks for your help
Aurélien
The text was updated successfully, but these errors were encountered: