Navigation

Thoughts on sequencing strategy

Lex Nederbragt (corr) et al.

When setting up a strategy for sequencing/assembly these are valuable to know:

  • the goal of the project, e.g.
  • gene-mining
  • presence/absence of genes
  • long scaffolds for synteny
  • reference genome-standard (whatever that is)
  • strain variation/haplotying
  • genome size
  • genome complexity, i.e. repeat content and level of heterozygosity
  • number of chromosomes, extrachromosomal elements
  • can a pure sample be obtained or will there be contaminating DNA?
  • how much DNA can be obtained from a single individual/clonal line or will it be necessary to use DNA from a mix of different individuals (read: different genomes)?
  • is there sequencing data available from the same individual or species?
  • how close is the most closely related reference genome?

Previous topic

Our list of good practices in (meta)genome assembly

Next topic

Questions (and some answers) about sequencing and assembly

This Page

Navigation

LICENSE: This documentation and all textual/graphic site content is licensed under the Creative Commons - 0 License (CC0) -- fork @ github. Presentations (PPT/PDF) and PDFs are the property of their respective owners and are under the terms indicated within the presentation.

Development and posting of this material, and the associated workshop, were supported by Grant Number R25HG006243 from the National Human Genome Research Institute and an NSF OCI supplement to NSF DBI-0939454.

© Copyright 2013, Holly Bik, C. Titus Brown, Nick Loman, Lex Nederbragt, Jared Simpson. Created using Sphinx 1.1.3.

Edit this document!

This file can be edited directly through the Web. Anyone can update and fix errors in this document with few clicks -- no downloads needed.

  1. Go to Thoughts on sequencing strategy on GitHub.
  2. Edit files using GitHub's text editor in your web browser (see the 'Edit' tab on the top right of the file)
  3. Fill in the Commit message text box at the bottom of the page describing why you made the changes. Press the Propose file change button next to it when done.
  4. Then click Send a pull request.
  5. Your changes are now queued for review under the project's Pull requests tab on GitHub!

For an introduction to the documentation format please see the reST primer.