Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
BMC Genomics. 2011 Apr 12;12:184. doi: 10.1186/1471-2164-12-184.

Accurate and exact CNV identification from targeted high-throughput sequence data.

Author information

  • 1Department of Genome Sciences, University of Washington, Seattle, 98195-7720, USA. nordalex@u.washington.edu

Abstract

BACKGROUND:

Massively parallel sequencing of barcoded DNA samples significantly increases screening efficiency for clinically important genes. Short read aligners are well suited to single nucleotide and indel detection. However, methods for CNV detection from targeted enrichment are lacking. We present a method combining coverage with map information for the identification of deletions and duplications in targeted sequence data.

RESULTS:

Sequencing data is first scanned for gains and losses using a comparison of normalized coverage data between samples. CNV calls are confirmed by testing for a signature of sequences that span the CNV breakpoint. With our method, CNVs can be identified regardless of whether breakpoints are within regions targeted for sequencing. For CNVs where at least one breakpoint is within targeted sequence, exact CNV breakpoints can be identified. In a test data set of 96 subjects sequenced across ~1 Mb genomic sequence using multiplexing technology, our method detected mutations as small as 31 bp, predicted quantitative copy count, and had a low false-positive rate.

CONCLUSIONS:

Application of this method allows for identification of gains and losses in targeted sequence data, providing comprehensive mutation screening when combined with a short read aligner.

PMID:
21486468
[PubMed - indexed for MEDLINE]
PMCID:
PMC3088570
Free PMC Article

Images from this publication.See all images (4)Free text

Figure 1
Figure 2
Figure 3
Figure 4
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for BioMed Central Icon for PubMed Central
    Loading ...
    Write to the Help Desk