Hello,
I've aligned Illumina paired end reads with BWA, filtered using samtools view -f 3 -F 12 ("proper pairs", both mates mapped).
I'm looking at the XT tags and see expected classes, where both mates are XT:A:U (both "unique") and XT:A:M + XT:A:U (one mate-rescued, one "unique").
However, I also find a class of paired reads where one read is XT:A:R (multiply-mapped) and the other is XT:A:U. This class of reads is a significant fraction of the total pairs (~10%) and the class persists after filtering on MAPQ > 20.
I anticipated that this class of reads would instead be classifed in the XT:A:M + XT:A:U (ie XT:A:R converted to XT:A:M), but apparently not.
Are the XT:A:R whose mate is XT:A:U mate-rescued, or something else?
Thanks.
I've aligned Illumina paired end reads with BWA, filtered using samtools view -f 3 -F 12 ("proper pairs", both mates mapped).
I'm looking at the XT tags and see expected classes, where both mates are XT:A:U (both "unique") and XT:A:M + XT:A:U (one mate-rescued, one "unique").
However, I also find a class of paired reads where one read is XT:A:R (multiply-mapped) and the other is XT:A:U. This class of reads is a significant fraction of the total pairs (~10%) and the class persists after filtering on MAPQ > 20.
I anticipated that this class of reads would instead be classifed in the XT:A:M + XT:A:U (ie XT:A:R converted to XT:A:M), but apparently not.
Are the XT:A:R whose mate is XT:A:U mate-rescued, or something else?
Thanks.
Comment