Question: good CIGAR value but poor MAPQ value
0
gravatar for cpak1981
17 months ago by
cpak1981100
cpak1981100 wrote:

I was a bit confused by the output of a bwa read-alignment. I have observations that return a good CIGAR value but poor MAPQ value. This alignment was obtained from converting a BAM file -> BED file that was generated with bwa mem.

chr1    142536052       142536087       336_1362_95     0       -       16      35M     *       0       0       CACTCCAGACTCGGTGACAGAGTGAGATCCTGTCG  8?@?.:/@@@@@@@@@@@@@@@>?@@@@?@@>@=@     NM:i:1  MD:Z:8T26       AS:i:30 XS:i:29

I thought CIGAR values and MAPQ value should be correlated but this breaks my intuition. Any insights would be super helpful. Thanks!

bwa • 602 views
ADD COMMENTlink modified 17 months ago by WouterDeCoster37k • written 17 months ago by cpak1981100
2
gravatar for WouterDeCoster
17 months ago by
Belgium
WouterDeCoster37k wrote:

The cigar string tells you how well the alignment matches the reference. That doesn't mean the nucleotide match, but that's not the point here.

The mapping quality tells you how likely this location is indeed the correct location for this read. A read matching perfectly to a repetitive element will have a low mapping quality because you are unsure about its exact location, it's a multi-mapping read.

ADD COMMENTlink written 17 months ago by WouterDeCoster37k

Thanks for the reply. This was my first thought but I didn't see a secondary alignment tag, such as XA:Z:chr1,-24263422,35M,1; which is present in other reads of my file. Does that dissuade from the possibility it is multi-mapping?

ADD REPLYlink written 17 months ago by cpak1981100

I just blatted your sequence and it's clear that this is part of an Alu element and therefore occurs very often in the genome.

ADD REPLYlink written 17 months ago by WouterDeCoster37k

Great, thank you for the help!

ADD REPLYlink written 17 months ago by cpak1981100
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: 1172 users visited in the last hour