...
- This is one alignment record, although it has been broken up below for readability.
- Notice the CIGAR string is 3S20M13S, meaning that 3 bases were soft clipped from one end (3S), and 13 from the other (13S).
- If we did the same alignment using either bowtie2 --end-to-end mode, or using bwa aln as in Exercise #1, very little of this file would have aligned.
- The 20M part of the CIGAR string says there was a block of 20 read bases that mapped to the reference.
- If we had not lowered the seed parameter of Bowtie2 bowtie2 from its default of 22, we would not have found many of the alignments like this one that only matched for 20 bases.
Such is the nature of bowtie2 – it it can be a powerful tool to sift out the alignments you want from a messy dataset with limited information, but doing so requires careful tuning of the parameters, which can take quite a few trials to figure out.
Exercise #3: BWA-MEM
...
- Human mRNA-seq
After Bowtie2 bowtie2 came out with a local alignment option, it wasn't long before BWA generated their bwa developed its own local - aligner called BWA-MEM (for Maximal Exact Matches Maximal Exact Matches). This This aligner is very, very nice because it incorporates a lot of the simplicity of using BWA with the complexities of local alignment. This functionality, while enabling the alignment of datasets like the mirbase data we just examined, also permits more complex alignments, such as that of spliced mRNAs. In a long RNA-seq experiment, reads will (at some frequency) span a splice junction themselves, or a pair of reads in a paired-end library will fall on either side of a splice junction. We want to be able to align reads that do this for many reasons, from accurate transcript quantification to novel fusion transcript discovery. Thus, our last exercise will be the alignment of a human LONG RNA-seq dataset composed (by design) almost exclusively of reads that cross splice junctions.
...