Hi Lauren,
Thanks for getting back to me.
I was actually using v0.6.1 and tested out the bowtie2 "—no-discordant" option, but that’s actually not what I was looking for. Since the output option is "--un-conc” it actually doesn’t matter whether this option is used or not from what I can tell since only reads that aligned concordantly anyway are screened out.
I was confused about what discordant read alignments are, but it’s well described in the bowtie2 manual (in case others are interested too):
'A pair that aligns with the expected relative mate orientation and with the expected range of distances between mates is said to align "concordantly". If both mates have unique alignments, but the alignments do not match paired-end expectations (i.e. the mates aren't in the expected relative orientation, or aren't within the expected distance range, or both), the pair is said to align "discordantly”.'
I was originally thinking that discordant alignments included cases where only 1 read mate aligns, but actually that’s not true, as described above. I think it would be more conservative to screen out these discordant alignments too since they could just be due to structural variants that aren’t present in the reference genome. I also think that filtering out cases where 1 mate maps and the other doesn’t would be helpful too in samples where we’re really worried about host contamination. What do you think about this?
Cheers,
Gavin