shasta icon indicating copy to clipboard operation
shasta copied to clipboard

[MOVED] Moved to paoloshasta/shasta. De novo assembly from Oxford Nanopore reads

Shasta long read assembler


The complete user documentation is available here.

For quick start information see here.

See Shafin et al., Nature Biotechnology 2020 for error analysis of the Shasta assembler and more. Reads from this paper are available here. The assembly results are here.

ℹ️ Example assemblies, user guides, FAQ and more can be found on the Shasta Docs site.

Requests for help: please file GitHub issues to report problems, request help, or ask questions. Please keep each issue on a single topic when possible.


The goal of the Shasta long read assembler is to rapidly produce accurate assembled sequence using DNA reads generated by Oxford Nanopore flow cells as input.

Computational methods used by the Shasta assembler include:

  • Using a run-length representation of the read sequence. This makes the assembly process more resilient to errors in homopolymer repeat counts, which are the most common type of errors in Oxford Nanopore reads.

  • Using in some phases of the computation a representation of the read sequence based on markers, a fixed subset of short k-mers (k ≈ 10).

As currently implemented, Shasta can run an assembly of a human genome at coverage around 60x in about 3 hours using a single, large machine (AWS instance type x1.32xlarge, with 128 virtual processors and 1952 GB of memory). The compute cost of such an assembly is around $20 at AWS spot market or reserved prices.

Shasta assembly quality is comparable or better than assembly quality achieved by other long read assemblers - see Shafin et al., Nature Biotechnology 2020 for an extensive analysis. However, adjustments of assembly parameters are generally necessary to achieve optimal assembly results. A set of sample configuration files is provided (in the conf directory) to assist with this process.

Acknowledgments

The Shasta software uses various external software packages. See here for more information.

Reporting Security Issues

Please note: If you believe you have found a security issue, please responsibly disclose it by contacting [email protected].


The complete user documentation is available here.

For quick start information see here.

For even more information see here.