What's the possible causes of strand bias in exome sequencing?
1
5
Entering edit mode
10.3 years ago
wangyi2412 ▴ 240

The strand bias here means the genotypes inferred from info presented by the forward strand and the reverse strand disagrees. For example,

read depths data at a position after mapping could be

         forward           reverse
ref      20                33
alt      19                0

which shows strong strand bias.

My question is that how come this happen? I think there might be 4 possible causes:

  1. the sample itself does not strickly base paired
  2. exome capture bias (how could this happen?)
  3. sequencing error(how could this happen?)
  4. mapping error

Am I right? Any comments is welcome!

exome NGS strand-bias • 12k views
ADD COMMENT
1
Entering edit mode

Possibility 1 is pretty low probability. You forgot #5, PCR duplication that didn't get marked.

ADD REPLY
5
Entering edit mode
10.3 years ago

Have you seen this paper: http://www.biomedcentral.com/1471-2164/13/666? They argue that this is likely to happen at option #4, mainly because of interference between local realignment and BAQ steps. The primary cause of this could be a sequencing error.

This question was also discussed in the community (http://seqanswers.com/forums/showthread.php?t=9354), which argues that a specific CCGG motif causes bases to be skipped on one strand, but not the other. As far as I remember, Illumina is likely to produce Indels in Poly-G regions, and Indels are common case for incorrect variant calling.

PS It would be also very useful if you'll specify what sequencing system, read alignment software and variant caller you're using

ADD COMMENT
0
Entering edit mode

Thank you! Sorry I reply late cause I did not have the Internet access.

Yes, the CCGG motif is a good hint! I will read it. Thank you very much!

ADD REPLY

Login before adding your answer.

Traffic: 2504 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