Why reads not match to the genome? too many wrong bases to the genome
Dear all,
I am very new in this field. I faced problems that I could not find the answer.
- I used IGV to see the mapped reads to the Arabidopsis genome. However, I found this.
Why reads mapped to the wrong position ? or the genome reference is a problem.
Does it suggest something wrong with the mapping procedure?
Why can reads be mapped to the position with so many different bases?
The following is tophat code.
tophat -p 12 -o 20170905_tophat_WT -G /usr1/thhuang/index/TAIR10_GFF3_genes_transposons.gff /usr1/thhuang/index/TAIR10_chr Trim_WT.fastq.gz
Hope to find a solution
Thank you all in advance
• 2,989 views
•
link
written
by
maple964 •
2 answers
You are most likely visualizing the alignments against a different genomic build than what the aligner used.
Ensure that the reference genomes are the same in both cases.
• 0 views
•
link
written
by
Istvan Albert
Thank you all for the reply! I am appreciated. I downloaded a new reference and did the mapping using tophat again. The results showed normal.
• 0 views
•
link
written
by
maple964 •
Log in to answer this question.
More posts like this
-
Mapping Phred+64 encoded reads with Bowtie2
written by Denis
-
IGV alignment explanation
written by David
-
HTseq: Error occured when reading beginning of SAM/BAM file.
written by maple964 •
-
Tophat multiple or unique mapping criteria
written by maple964 •
-
Mapping to a single Chromosome Tophat
written by benjyrolls
-
Tophat & IGV viewing
written by aleka
-
Tophat does not map reads in some locations on reference genome but bowtie does
written by heshamgibriel •
-
Very short reads (20-22) , bowtie and tophat not doing gapped alignment
written by manekineko
-
What causes this message in IGV?
written by Y Tb
-
How to create a genome from hg19.fa file and GTF file from ensembl to be use to visualize mapped da…
written by Y Tb
Looks like you mapped against a different genome than you're using in IGV.
While the command line and the image say
TAIR10there is certainly the possibility that something is wrong as far as the genome build is concerned.Surprising that IGV still allows one to select an incorrect genome.
This is because of the oversimplification in SAM spec where the mismatch is reported as an
Mso we can only figure the mismatches from the MD tag. But the MD tag is optional hence, by default, the SAM spec does not require the aligner to report how many mismatches the alignment contains...let's just think about that for a second...If the MD tag does not match what IGV sees then there is a discrepancy. Now it becomes a user interface issue. How many mistakes until you show the error. If it is too strict it just brings about another set of problems.