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

mitoz3.4 annotations draw circle diagrams all have a gap, but in other annotation platforms are circular #172

Open
sanjin725 opened this issue Nov 17, 2022 · 13 comments
Labels
enhancement New feature or request

Comments

@sanjin725
Copy link

mitoz3.4 annotations draw circle diagrams all have a gap, but in other annotation platforms are circular

Problem description

Log messages from MitoZ (stdout and stderr)

@linzhi2013
Copy link
Owner

Hi sanjin,

thanks for reporting the issue, I will check it later.

All the best

@gdcfy
Copy link

gdcfy commented Jun 21, 2023

Hi sanjin,

thanks for reporting the issue, I will check it later.

All the best

Hi
I get the circular mitoz diagram with a gap, is this OK or anyother errors taken place?

circos

@linzhi2013
Copy link
Owner

Hi gdcfy,

Even when the mitogenome is complete, the current visualization seems to keep a gap between the starting point and ending point. I forgot to fix it in MitoZ 3.6 too...

@linzhi2013 linzhi2013 added the enhancement New feature or request label Jun 21, 2023
@gdcfy
Copy link

gdcfy commented Jun 21, 2023 via email

@linzhi2013
Copy link
Owner

linzhi2013 commented Jun 21, 2023

Hi @gdcfy ,

I just check MitoZ 3.6. This bug has been fixed in MitoZ 3.6. See below:

circos

Therefore, you may need to upgrade to MitoZ 3.6.

Best

@linzhi2013
Copy link
Owner

linzhi2013 commented Jun 21, 2023

Please beware that, MitoZ looks for the "circular" character in your input GenBank file.

LOCUS       k99_0                  16453 bp    DNA     circular PRI 21-JUN-2023

So, even if your mitogenome is complete, but if you don't have the "circular" on the first line of your GenBank file, MitoZ still considers it incomplete.

my $break;
foreach my $l(@lines) {
	my $a = (split/\s+/,$l)[1];
	my $topo = (split/\s+/,$l)[5];
	$topology{$a} = $topo;
	if ($topo eq 'circular') {
		$break = 0;
	}else {
		$break = "0.5r";
	}
}

@linzhi2013
Copy link
Owner

If you use MitoZ for the assembly, you can go to check the content of the tmp/mt_assembly/megahit/DM01.megahit.overlap_information file:

>k99_0 overlap between 5' and 3' are 100bp
AACAATATTCTTGGCGGCCGATTTCTAAATGTTCAACCTTGTTAGTTTTTTCTGTATGCACTGTGAAATGCAAAGTGAAAGGAAATAGAGAAAAAAAAC

If it is long enough and not a simple repeat, then your mitogenome is probably complete (i.e. circular). This information is also available in the summary.txt file:

#Seq_id        Length(bp)     Circularity    Closely_related_species
k99_0          16453          yes            Oryzias sinensis

Please refer to the wiki for more details.

@gdcfy
Copy link

gdcfy commented Jun 21, 2023 via email

@gdcfy
Copy link

gdcfy commented Jun 24, 2023

Hi, @linzhi2013
I get a problem. There is no any content in the file "tmp/mt_assembly/megahit/DM01.megahit.overlap_information", which may lead to gap of the circular diagram. But I don't know what does it caused from and how to figure it out.

<img width="318" alt="image" src="https://github.com/linzhi2013/MitoZ/assets/115930352/98c333a6-b167-4abc-8fe3-a1ade74b4f4b">

@gdcfy
Copy link

gdcfy commented Jun 24, 2023

Hi, @linzhi2013 I get a problem. There is no any content in the file "tmp/mt_assembly/megahit/DM01.megahit.overlap_information", which may lead to gap of the circular diagram. But I don't know what does it caused from and how to figure it out.

image

and I use the mitoz with version 3.6

image

@linzhi2013
Copy link
Owner

linzhi2013 commented Jun 24, 2023

Hi, @linzhi2013 I get a problem. There is no any content in the file "tmp/mt_assembly/megahit/DM01.megahit.overlap_information", which may lead to gap of the circular diagram. But I don't know what does it caused from and how to figure it out.

image and I use the mitoz with version 3.6 image

I just noticed that, according to your circos plot, the coverage along your mitogenome is quite low, except in the region around 18Kbp. PLease go to check the filemt_annotation/tmp_DM01_DM01.megahit.mitogenome.fa_mitoscaf.fa/mt_visualization/circos.depth.txt and check the exact depth of your mitogenome. If many sites have very low or even 0X, it indicates your mitogenome is not reliable.

You should check if the recovered mitogenome belongs to your target species. Please refer to https://github.com/linzhi2013/MitoZ/wiki/Tutorial#7-what-now

BTW, what kind of data did you use? and what was the MitoZ command? You might also try to use larger kmers if the mitogenome is partially wrong (especially for the region after 16Kbp), or use the mitoAssemble assembler in MitoZ.

@gdcfy
Copy link

gdcfy commented Jun 27, 2023

Hi, @linzhi2013 I get a problem. There is no any content in the file "tmp/mt_assembly/megahit/DM01.megahit.overlap_information", which may lead to gap of the circular diagram. But I don't know what does it caused from and how to figure it out.

<img width="318" alt="image" src="https://github.com/linzhi2013/MitoZ/assets/115930352/98c333a6-b167-4abc-8fe3-a1ade74b4f4b">

Hi,
According to your suggests. I figured out the problem with changing paramater.
original paramater:

mitoz all --fq1 HK170851_1.fq.gz  --fq2 HK170851_2.fq.gz  --outprefix HK  --clade Chordata  --requiring_taxa Chordata   --data_size_for_mt_assembly 5,0    --assembler megahit  --memory 50

altered paramater:

mitoz all --fq1 HK1708115_1.fq.gz  --fq2 HK1708115_2.fq.gz  --outprefix HK  --clade Chordata  --genetic_code 2   --requiring_taxa Chordata   --data_size_for_mt_assembly 5,0    --assembler megahit  --kmers_megahit 59 79 99 119 141    --memory 50 

the gap may caused by setting kmer size which problem refered as "https://github.com/linzhi2013/MitoZ/wiki/Known-issues#8-megahit-gets-very-long-sequences"

after revising the gap with the "altered paramater", there is another problem that between the starting and ending site of mitogenome. at the contig between the starting and ending site, there is low abundance, and for this problem I changed the paramater from --data_size_for_mt_assembly 5,0
to --data_size_for_mt_assembly 25,0 .
finally the problems have been solved but with much running time

@linzhi2013
Copy link
Owner

linzhi2013 commented Jun 27, 2023

Sometimes it happens. Different samples have different ratios of mitogenome-derived reads. And different regions of the mitogenome usually have coverage variations, the AT-rich region (e.g. control region) usually gets lower coverage, probably due to some experimental and sequencing bias in NGS sequencing.

If we use more input fastq data, we get more MT-reads, so the overall coverage of the mitogenome will rise up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants