Closed THYeh44 closed 4 years ago
The reason I have the wrong chromosome offset is because of the .bam files and the reference fasta file has a different chromosome order. Everything works just fine again after changing the chromosome order of the reference file to the same as .bam file.
That makes sense. It is important to make sure that the same fasta file is used for alignment and variant calling.
I've been using the same fast file for alignment and several different variants calling scripts, it's my first time having this problem.
TH Sent from my iPhone
On Dec 6, 2019, at 6:03 PM, Bansal Lab notifications@github.com wrote:
That makes sense. It is important to make sure that the same fasta file is used for alignment and variant calling.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.
The first problem is Segmentation fault which has been reported in 2015. It seems that Segfault happened stochastically in my case since sometimes it appears right after the command is entered, and sometimes it showed up after ~20-30 mins run.
Because Segfault doesn't always happen right after the run, so I'm trying to resolve this by using --region argument and that brings up the second problem: before chromosome four everything works fine, but when entering "--region V", instead of reading read chromosome five but it jumps to chromosome X (in the .vcf and .log file); and "--region X" actually reads mitochondria DNA (C. elegans genome, I-V, X, +MtDNA). Here's the command line and result when I use --region IV, --region V, --region X ,and --MtDNA.