| Literature DB >> 30423092 |
Ibrahim Numanagic1,2, Alim S Gökkaya3, Lillian Zhang1, Bonnie Berger1,2, Can Alkan3, Faraz Hach4,5.
Abstract
Motivation: Segmental duplications (SDs) or low-copy repeats, are segments of DNA > 1 Kbp with high sequence identity that are copied to other regions of the genome. SDs are among the most important sources of evolution, a common cause of genomic structural variation and several are associated with diseases of genomic origin including schizophrenia and autism. Despite their functional importance, SDs present one of the major hurdles for de novo genome assembly due to the ambiguity they cause in building and traversing both state-of-the-art overlap-layout-consensus and de Bruijn graphs. This causes SD regions to be misassembled, collapsed into a unique representation, or completely missing from assembled reference genomes for various organisms. In turn, this missing or incorrect information limits our ability to fully understand the evolution and the architecture of the genomes. Despite the essential need to accurately characterize SDs in assemblies, there has been only one tool that was developed for this purpose, called Whole-Genome Assembly Comparison (WGAC); its primary goal is SD detection. WGAC is comprised of several steps that employ different tools and custom scripts, which makes this strategy difficult and time consuming to use. Thus there is still a need for algorithms to characterize within-assembly SDs quickly, accurately, and in a user friendly manner.Entities:
Mesh:
Year: 2018 PMID: 30423092 PMCID: PMC6129265 DOI: 10.1093/bioinformatics/bty586
Source DB: PubMed Journal: Bioinformatics ISSN: 1367-4803 Impact factor: 6.937
Fig. 1.(Left) Simplified representation of a SD lifetime. Initially, a large-scale duplication forms an SD, at which point both the original region and the copy are identical. Then, both the original region and copy undergo various independent changes, such as large-scale deletions (in red), insertions (in blue), and small repeat insertions (in fuchsia). Finally, various germline mutations (in yellow) affect both regions. The resulting SD as seen today, defined as the pair , is shown in the third row. (Right) Shows the idealized Jaccard similarity between the k-mer sets X and X corresponding to the G and G, respectively. Note that some repeats also increase the proportion of shared k-mers. Colors denote same as on Left
Fig. 2.Step-by-step depiction of the SEDEF framework. Our contribution is highlighted above the steps in the dark gray boxes
Running time performance of SEDEF in single-core mode and multi-core mode on 80 Intel Xeon E7-4860 v2 cores at 2.60 GHz
| Human (hg19) | Mouse (mm8) | |||||
|---|---|---|---|---|---|---|
| Total | Seeding and extending | Chaining and aligning | Total | Seeding and extending | Chaining and aligning | |
| 1 core | 10 h 30 min | 7 h 33 min | 2 h 57 m | 13 h 7 min | 7 h 53 min | 5 h 14 min |
| 80 cores | 0 h 14 min | 0 h 10 min | 0 h 04 m | 0 h 30 min | 0 h 10 min | 0 h 20 min |
Fig. 3.(Left) Performance of SEDEF’s algorithm on simulated SDs. x-axis is the total simulated SD error rate δ, whereas y axis is the number of correctly detected SDs (total 1000 for each δ). Since SEDEF successfully detects more than 995 simulated SDs for any δ, the plot area is cropped. (Right) Venn diagram depicts the SD coverage of the human and mouse genome (in Mbp) as calculated by SEDEF and WGAC. Intersected region stands for the bases covered by both SEDEF and WGAC
SD coverage of the human genome (hg19) as reported by different tools
| Tool | Covers | Misses | Extra | Time (h: m) |
|---|---|---|---|---|
| WGAC (gold standard) | 159.5 | 0.0 | 0.0 | weeks |
| SEDEF | 218.8 | 0.6 | 60.0 | 0:36 |
| Minimap2 | 53.3 | 107.3 | 1.1 | 1:30 |
| MUMmer/nucmer | 142.6 | 30.8 | 13.9 | ≥20:00 |
| SDDetector | 30.1 | 130.8 | 1.5 | ≥1:00 |
Note: Misses and Extra are calculated with respect to the WGAC SD calls, which are currently the gold standard of SD calls. Note that we have filtered out all calls where at least one mate is composed solely of common short repeats (Minimap2, MUMmer/nucmer and SDDetector) as we did on SEDEF. All running times were adjusted for 20 CPU cores (all tools which support parallelization were run on 20 cores).
aAdjusted running time for 20 cores; in reality, SDDetector spends hours in the single threaded pre-processing stage. Furthermore, the reported running time only includes post-processing and does not include initial BLAST alignment calculations.