Questions regarding whole exome sequencing
1
0
Entering edit mode
3.9 years ago
nhaus ▴ 300

Hey everybody, I am currently informing myself about Whole exome sequencing (WES) and there are a couple of things that still confuse me:

1) I read that WES "does not permit deep sequencing". Can somebody elaborate why this is the case?

2) I checked this website to get an idea about coverage for WES and I did not understand, why it is necessary to have a much higher coverage for detecting SNV when using WES compared to whole genome sequencing (e.g. 100x vs 15x).

If anyone could answer these questions for me, I'd be very thankful!!

Thanks!

WES sequencing • 713 views
ADD COMMENT
0
Entering edit mode
3.9 years ago

1) I read that WES "does not permit deep sequencing". Can somebody elaborate why this is the case?

One can have relatively high depth of coverage even with whole genome sequencing. However, factors that limit depth of coverage include:

  • input DNA amount and concentration
  • input DNA quality
  • sequencer used and flow-cell capacity
  • number of sequencing cycles used
  • library prep used
  • reagent availability
  • et cetera

Coverage over certain regions of the genome will also always be limited due to GC content, sequence similarity, and other factors.

2) I checked this website to get an idea about coverage for WES and I did not understand, why it is necessary to have a much higher coverage for detecting SNV when using WES compared to whole genome sequencing (e.g. 100x vs 15x).

One merely requires per position read depth of ~30 in order to achieve high sensitivity to the gold standard when calling SNVs / SNPs. For somatic variants, however, high read depth is more desirable due to the fact that, in a tumour bulk biopsy, we would expect many somatic variants to only be detected at low frequencies.

Kevin

ADD COMMENT

Login before adding your answer.

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