Awesome

Flye assembler

Version: 2.9.5

Flye is a de novo assembler for single-molecule sequencing reads, such as those produced by PacBio and Oxford Nanopore Technologies. It is designed for a wide range of datasets, from small bacterial projects to large mammalian-scale assemblies. The package represents a complete pipeline: it takes raw PacBio / ONT reads as input and outputs polished contigs. Flye also has a special mode for metagenome assembly.

Currently, Flye will produce collapsed assemblies of diploid genomes, represented by a single mosaic haplotype. To recover two phased haplotypes consider applying HapDup after the assembly.

If you are using Flye / metaFlye to assemble heteroztgous bacterial genomes or metagenomes, you may consider using strainy to call and quanitify heterozygosity and reveal collapsed strains.

Manuals

• Installation instructions
• Usage
• FAQ

Latest updates

Flye 2.9.5 release (27 Aug 2024)

• Python 3.12 support, Python 2 dropped

Flye 2.9.4 release (14 May 2024)

• Minor technical changes

Flye 2.9.3 release (28 November 2023)

• Disjointig step speedup for --nano-hq mode
• Improved --keep-haplotypes mode preserves more heterozygous SVs
• A few bug fixes

Flye 2.9.2 release (18 March 2023)

• Update to minimap 2.24 + using HiFi and Kit14 parameters for faster alignment
• Fixed a few small bugs and corner cases
• Polisher now outputs read depth for each base of consensus (can be used as confidence measure)

Flye 2.9.1 release (07 Aug 2022)

• New option --no-alt-contigs to remove all non-primary contigs from the assembly
• Fixed crash on MacOS with Python 3.8+
• Fixed rare artificially introduced mismatches while polishing
• Fixed slow simplification of very tangled graphs
• Various other small fixes

Flye 2.9 release (20 Aug 2021)

• Better assembly of very short sequences (e.g. plasmids or viruses). They were often missed in previous versions.
• New --nano-hq mode for ONT Guppy5+ (SUP mode) and Q20 reads (3-5% error rate)
• Optimized default parameters for HiFi (HPC error threshold 0.01 -> 0.001; increased min overlap)
• Polishing improvements: reduced number of possible clusters of errors
• Improvements in repeat detection algorithm to further limit a chance of (otherwise infrequent) misassemblies
• Scaffolding is no longer performed by default (could be enabled with --scaffold)
• Bam file input for the standalone polisher (same interface as for FASTA/Q)
• Automatically selected minimum overlap up to 10k (was 5k)
• Discontinued --plasmid option due to the improvements in short sequences assembly
• --trestle and --subassemblies modes are now deprecated, and will be removed in the future versions
• New --extra-params option to modify config-level parameters
• Contig paths output in Gfa + number of reads supporting each link (RC tag)
• Update to minimap 2.18
• Several rare bug fixes/other improvements

Repeat graph

Flye is using a repeat graph as the core data structure. Compared to de Bruijn graphs (which require exact k-mer matches), repeat graphs are built using approximate sequence matches, and can tolerate the higher noise of SMS reads.

The edges of a repeat graph represent the genomic sequence, and nodes define the junctions. Each edge is classified as unique or repetitive. The genome traverses the graph (in an unknown way), so each unique edge appears exactly once in this traversal. Repeat graphs reveal the repeat structure of the genome, which helps to reconstruct an optimal assembly.

Above is an example of the repeat graph of a bacterial assembly. Each edge is labeled with its id, length, and coverage. Repetitive edges are shown in color, and unique edges are black. Note that each edge is represented in two copies: forward and reverse complement (marked with +/- signs), therefore the entire genome is represented in two copies. This is necessary because the orientation of input reads is unknown.

In this example, there are two unresolved repeats: (i) a red repeat of multiplicity two and length 35k and (ii) a green repeat cluster of multiplicity three and length 34k - 36k. As the repeats remained unresolved, there are no reads in the dataset that cover those repeats in full. Five unique edges will correspond to five contigs in the final assembly.

Repeat graphs produced by Flye could be visualized using AGB or Bandage.

Flye benchmarks

The assemblies generated using Flye 2.9 could be downloaded from Zenodo. All datasets were run with default parameters for the corresponding read type with the following exceptions: CHM13 T2T, CHM1 and HG002 were run with --asm-coverage 50.

Note that this version of the table reflects contigs NG50, while the previous versions were referring to scaffold NG50.

Third-party

Flye package includes some third-party software:

• libcuckoo
• intervaltree
• lemon
• minimap2
• samtools

License

Flye is distributed under a BSD license. See the LICENSE file for details.

Credits

Flye is developed in Pavel Pevzner's lab at UCSD

Main code contributors:

• metaFlye: Mikhail Kolmogorov
• Repeat graph and current package maintaining: Mikhail Kolmogorov
• Trestle module and original polisher code: Jeffrey Yuan
• Original contig extension code: Yu Lin
• Short plasmids recovery module: Evgeny Polevikov

Publications

Mikhail Kolmogorov, Derek M. Bickhart, Bahar Behsaz, Alexey Gurevich, Mikhail Rayko, Sung Bong Shin, Kristen Kuhn, Jeffrey Yuan, Evgeny Polevikov, Timothy P. L. Smith and Pavel A. Pevzner "metaFlye: scalable long-read metagenome assembly using repeat graphs", Nature Methods, 2020 doi:10.1038/s41592-020-00971-x

Mikhail Kolmogorov, Jeffrey Yuan, Yu Lin and Pavel Pevzner, "Assembly of Long Error-Prone Reads Using Repeat Graphs", Nature Biotechnology, 2019 doi:10.1038/s41587-019-0072-8

Yu Lin, Jeffrey Yuan, Mikhail Kolmogorov, Max W Shen, Mark Chaisson and Pavel Pevzner, "Assembly of Long Error-Prone Reads Using de Bruijn Graphs", PNAS, 2016 doi:10.1073/pnas.1604560113

How to cite: the 2020 paper is the most relevant to metagenome assembly. For single genome assembly, use the 2019 paper as reference. The 2016 paper describes solid k-mer indexing and polishing approaches that are used as core algorithms in the current pipeline.

How to get help

A preferred way report any problems or ask questions about Flye is the issue tracker. Before posting an issue/question, consider to look through the FAQ and existing issues (opened and closed) - it is possible that your question has already been answered.

If you are reporting a problem, please include the flye.log file and provide details about your dataset.