[Bio] / FigTutorial / How_to_annotate_a_genome.html Repository:
ViewVC logotype

View of /FigTutorial/How_to_annotate_a_genome.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.1 - (download) (as text) (annotate)
Fri Dec 21 21:08:35 2007 UTC (12 years, 3 months ago) by overbeek
Branch: MAIN
CVS Tags: rast_rel_2014_0912, rast_rel_2008_06_18, rast_rel_2008_06_16, rast_rel_2008_07_21, rast_rel_2010_0928, rast_2008_0924, rast_rel_2008_09_30, rast_rel_2010_0526, rast_rel_2014_0729, rast_rel_2009_05_18, rast_rel_2009_0925, rast_rel_2010_1206, rast_rel_2010_0118, rast_rel_2009_02_05, rast_rel_2011_0119, rast_rel_2008_12_18, rast_rel_2008_10_09, rast_release_2008_09_29, rast_rel_2008_04_23, rast_rel_2008_08_07, rast_rel_2009_07_09, rast_rel_2010_0827, myrast_33, rast_rel_2011_0928, rast_rel_2008_09_29, rast_rel_2008_10_29, rast_rel_2009_03_26, rast_rel_2008_11_24, HEAD
add description of anotating a genome

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>How_to_annotate_a_genome</title></head><body><h1 style="text-align: center;">How to Annotate a Genome</h1><div style="text-align: center;"><h3>by Ross Overbeek</h3><br><div style="text-align: left;">We at the Fellowship for Interpretation of Genomes (FIG) have actively led the <span style="font-weight: bold;">Project to Annotate a 1000 Genomes</span> since its inception in 2003. &nbsp;In that effort we pioneered what we called the <span style="font-weight: bold;">subsystems approach to annotation</span>
in which experts annotated a single subsystem across the entire set of
genomes. &nbsp;This was a radically different approach than the more
usual of attempting to annotate all of the genes in a single genome.
&nbsp;The effort to develop well-curated sets of subsystems has led to
a collection of 400-600 subsystems (depending on where you choose to
impose a threshold of acceptable quality). &nbsp;We believe that the
number will continue to grow for reasons that will become apparent in
this short note.<br><br>It is time to revisit the issue of how to
annotate a specific genome of interest, since numerous biologists are
now faced with that opportunity. &nbsp; For what it is worth, here is
our advice.<br><br><h2>Begin by Identifying the Recognizable Instances of Subsystems</h2>When
you are able to annotate a complete subsystem, the individual
assignments are all somewhat more reliable. &nbsp;Most of the common
machinery can easily be identified, and this establishes a starting
point for the more difficult remaining tasks. &nbsp;The easiest way to
perform this initial stage of analysis is to proceed through two tasks:<br><ol><li>Submit the genome sequence to the RAST server maintained at Argonne National Laboratory. &nbsp;This can be done by going to the <a href="http://rast.nmpdr.org/rast.cgi">RAST server</a>,
registering yourself as a user (anyone is welcome to use the site),
uploading your sequence, and getting an initial annotation back in
about 12 hours. &nbsp;You can then download the initial annotation to
your site and work on it using any tools you prefer. &nbsp;The initial
annotation from RAST gives you three things:<br><ul><li>protein-encoding genes (CDSs),</li><li>RNA-encoding genes (tRNAs and rRNAs)</li><li>identified subsystems</li></ul></li><li>Once
you have an initial set of identified subsystems, you should manually
go through and see where RAST missed identifying active variants.
&nbsp;It is fairly conservative in its calls, so if there were a
mis-called gene (e.g., due to a frameshift) or an unusual form of a
gene (e.g., an unknown form of an enzyme) you would see almost all of
the genes in a subsystem accounted for, but not enough for RAST to say
that the subsystem is really there. &nbsp;If you do this analysis
within RAST, you can compare the metabolic reconstruction for your
genome against related genomes, focusing on the specific differences.</li></ol>If
your genome is close to a previously annotated and studied genome, we
suggest that you do a detailed analysis of what genes distinguish the
new genome from the previously annotated genome (or genomes). &nbsp;The
SEED provides a tool for easily doing such a comparison, and similar
tools are either available or becoming available from a number of
sources.<br><br>Note that this initial step can be done very rapidly -- in a few days.<br><br><h2>Fix Frameshifts, Annotate Insertion Sequences, and Process Pseudo-genes</h2>RAST
often fails to identify the functional role of a particular gene due to
frameshifts. &nbsp;This is very common in low-quality sequence or
sequence produced by 454 technology. &nbsp;It is not particularly
serious, but we do recommend that you post-process the gene calls to
clean up the frameshifts. &nbsp; Biologists are justifiably reluctant
to change sequence data without resequencing; hence, we recommend that
the actual DNA sequence remain unchanged, that the correction be
embodied in the proposed translation of the feature, and that the
discrepancy between the actual DNA sequence and the translation be
recorded with the feature. We note that you can automatically correct
obvious frameshifts using tools within the SEED environment, and we
anticipate that these will become increasingly important as larger
volumes of low-quality sequence data becomes available.<br><br>The
issue of detecting insertion sequences, mobile elements, prophages and
so forth is important for a number of reasons. &nbsp;Determining the
set of impacted genes (often pseudo-genes) is extremely time-consuming.
&nbsp;We would guess that tools to support this type of analysis will
appear soon, but for now you will need to determine how much effort you
are willing to expend on the task. &nbsp; So, this part of the effort
can take from a few days (to automatically detect and correct
frameshifts) to man-years (to characterize insertion sequences,
pseudo-genes, and prophages).<br><h2>Look at Identified Functions that are Not in Subsystems</h2>As
you scan through the genes not yet placed in subsystems that were
identified by RAST, some correspond to FIGfams, and some do not.
&nbsp;Some are closely similar to well-annotated proteins (e.g., to
Swiss Prot entries), and some are not.<br><br>We recommend that you
scan through these focusing on those that correspond to functional
roles that should be encoded into subsystems. &nbsp; &nbsp;It is
particularly important to examine those for which "functional coupling"
information exists (RAST will give you this information). &nbsp;When
strong functional coupling data exists, and when the functional role
can be identified with reasonable certainty, you have a particularly
good candidate for a new subsystem. &nbsp;If you can connect any of the
genes in the cluster (in, say, genomes that are "close" and have been
actively studied) to literature, you need to get the relevant papers
before deciding how to proceed. &nbsp;We suggest making a rapid pass
through the set of genes that have not been assigned to subsystems,
prioritizing these genes for possible use in starting new subsystems.<br><br>We
urge you to develop new subsystems when possible and to publish these
subsystems (which makes them accessible to users working on other
versions of the SEED).<br><h2>Summary</h2>So, our approximate approach to annotating a new genome would be:<br><br><ol><li>Run the genome through RAST.</li><li>Do a detailed metabolic comparison (within RAST) between your new genome and one or more of its closest relatives. &nbsp;Follow this by a general comparison of what genes distinguish it from its closest relatives.</li><li>Correct obvious frameshifts.</li><li>Decide
whether or not you are willing to spend the effort needed to identify
IS elements, prophages and other mobile elements. &nbsp;Similarly,
decide whether or not you wish to expend the effort to carfully
identify pseudo-genes.</li><li>If you have substantially changed the
gene calls, rerun your genome through RAST again (keeping the gene
calls that you have now established).</li><li>Go through the genes that
have not yet been placed into subsystems, determine whether or not it
makes sense to construct a limited set of new subsystems (especially if
they capture aspects of the genome which may have motivated the
sequencing effort in the first place).</li></ol>This can be done either
very rapidly or more time can be taken. &nbsp;It all depends on&nbsp;
the anticipated role of the genome. &nbsp; In many cases, these tasks
can be performed in a few weeks, and we believe that the overall time
will continue to drop as the quality of the RAST analysis (due to an
expanded library of subsystems) improves.</div><div style="text-align: left;"></div></div></body></html>

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3