Question: Bowtie2: missing forward reads after alignment
0
gravatar for nikkihathi
3.6 years ago by
nikkihathi20
Germany
nikkihathi20 wrote:

Hello!

I have paired end exome sequence data for 50 human genes only. I have mapped the exome data to hg19 assembly using bowtie2 with default parameters.

 bowtie2 --end-to-end -x /path/to/human/genome -q -1 input1.fastq -2 input2.fastq -S output.sam

after the alignment, I used Picard samsort tool to sort the file and convert to bam file.

When I view the alignment, we found that there are some regions where only reverse reads are mapped and there were no forward reads.

The question is:

  1. In theory, Bowtie should only consider forward and reverse reads simultaneously for the mapping. However, because of some quality issue, only reverse reads are aligned. Is this true?

  2. Is this, alignment issue or trimming issue?

  3. Is this a bigger problem for interpretation of mutations (SNPs)

  4. which parameter/flag should I use to make a better alignment.

Thanks in advance

ADD COMMENTlink modified 3.6 years ago • written 3.6 years ago by nikkihathi20

Adding to my previous question:

I ran Tophat2 with the default parameters and the alignment with the same input was better and IGV showed both reads.

In principle, tophat2 implements Bowtie alignment strategy still misses some read strands.

Any suggestion or possible answer would be nice to be able to explain the difference or missing reads.

ADD REPLYlink written 3.6 years ago by nikkihathi20

I assume your input files are FASTQ, not BAM.

Anyway, to find out why this is happening, get the sequence of a few of the unaligned mates and blast them. That should give you a clue as to why they're not aligning.

ADD REPLYlink written 3.6 years ago by Devon Ryan93k

Yes you are correct, the input file is fastq not bam. Sorry for the mistake

Thanks, Do you think this could be because of the alignment strategy?

My suspicion is on --end-to-end or local alignment strategy.

ADD REPLYlink modified 3.6 years ago • written 3.6 years ago by nikkihathi20

That's worth a shot. If some of the unmapped reads align reasonably with blast then give --very-local-sensitive a try.

ADD REPLYlink written 3.6 years ago by Devon Ryan93k

You have an extra hyphen in the --end-to-end option (at least the way you are typing it in these posts).

ADD REPLYlink written 3.6 years ago by genomax75k

Is this, alignment issue or trimming issue?

Did you trim your data with a PE aware trimming program. It is possible that if you did the trimming of the PE files independently then you may have lost reads in one file (but not other). This would be a bad idea since aligners don't check to see if the reads in the input files are in proper order.
If above is true you should start this analysis over. Re-trim (this time using both files and PE aware trimmer) and then realign the data.

ADD REPLYlink written 3.6 years ago by genomax75k

No this is not a trimming issue, I double checked this.

Currently, I prefer Tophat2 instead of bowtie2 for alignment and the issue is resolved. However, I find this very interesting as tophat2 uses bowtie2 for alignment.

ADD REPLYlink written 3.6 years ago by nikkihathi20
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1018 users visited in the last hour