What Does The Zero Mapping Quality Mean For The Bwa Mapper?
2
4
Entering edit mode
11.9 years ago
lyz10302012 ▴ 470

In which condition, a read's mapping quality can be zero? (BWA) How can this kind of reads being used in variant calling or just be filtered out.

Thanks.

variant calling bwa mapping • 22k views
ADD COMMENT
0
Entering edit mode

Variant callers ignore reads with mapping quality zero

ADD REPLY
0
Entering edit mode

Can anyone explain why there are a lot of MQ0 reads in some particular regions (almost all reads are MQ0)?

ADD REPLY
1
Entering edit mode

if a region is duplicated then all the reads mapping there will also map elsewhere - In general please ask questions as a new standalone question rather than adding them as an answer

ADD REPLY
0
Entering edit mode

In the case of being mappable in multiple places, if it mapped slightly better to one region then would it have a mapping quality > 0?

ADD REPLY
15
Entering edit mode
11.9 years ago

Zero mapping quality indicates that the read maps to multiple locations. Note that this behavior is BWA specific.

ADD COMMENT
1
Entering edit mode

I have add the same comment twice, how can I delete one of them?

ADD REPLY
0
Entering edit mode

Would you please tell me which did know this? Is there a website link or manual about "0 mapping quality means that the read maps to multiple locations"

ADD REPLY
0
Entering edit mode

Would you please tell me which did know this? Is there a website link or manual about "0 mapping quality means that the read maps to multiple locations"

ADD REPLY
5
Entering edit mode
11.9 years ago

It has zero chance of being a uniquely mapped read, because it actually was mapped elsewhere.

ADD COMMENT
0
Entering edit mode

I agree, if the read mapped to a different chromosome, for example, the mapping quality could be 0 as well.

ADD REPLY

Login before adding your answer.

Traffic: 1734 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6