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
Hello Lin,
I'm having some problems using the mitoz visualize --depth_file command, and would like some help.
I run the command is
mitoz visualize --gb xyx_mt_02out_xyx_mt_02out.megahit.mitogenome.fa_mitoscaf.fa.gbf --depth_file xya_depth.txt --outdir xya_test
xya_depth.txt is a file I built myself, as shown here
This two depth_file, I tried input respectively, but the resulting graph did not have the depth track.And the circos.dept.txt file in the result file is blank.
The above is the result image and the result folder. I used MitoZ3.4 and 3.5 respectively to try, and there was no depth track in the image.
I wasn't sure what was wrong and wanted help. Thank you very much!
Liuxuanzeng
The text was updated successfully, but these errors were encountered:
Hi Lin,
Thank you for your help. I tried to use the absolute path, this problem has been solved. Sorry to trouble you with such a stupid mistake. Thank you very much.
No, I am pleased that you raised the issue, I should have converted the (relative) path of input files into an absolute path in MitoZ. I will fix it at the next release.
Hello Lin,
I'm having some problems using the mitoz visualize --depth_file command, and would like some help.
I run the command is
mitoz visualize --gb xyx_mt_02out_xyx_mt_02out.megahit.mitogenome.fa_mitoscaf.fa.gbf --depth_file xya_depth.txt --outdir xya_test
xya_depth.txt is a file I built myself, as shown here
This two depth_file, I tried input respectively, but the resulting graph did not have the depth track.And the circos.dept.txt file in the result file is blank.
The above is the result image and the result folder. I used MitoZ3.4 and 3.5 respectively to try, and there was no depth track in the image.
I wasn't sure what was wrong and wanted help. Thank you very much!
Liuxuanzeng
The text was updated successfully, but these errors were encountered: