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

View of /FigTutorial/TheCycle.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.2 - (download) (as text) (annotate)
Tue Mar 25 16:16:15 2008 UTC (11 years, 7 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
Changes since 1.1: +1 -1 lines
updating figure of cycle in tutorial

<!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>The Impotance of the Annotation Cycle</title>

</head>
<body>
<h1 style="text-align: center;">Reflections on Accurate Annotations:</h1>
<div style="text-align: center;">
<h2>The Basic Cycle and Its Significance<br>
</h2>
</div>
<h2 style="text-align: center;">by Ross Overbeek</h2>
<br>
I have recently been reflecting on the status of the&nbsp;<span style="font-style: italic;"><span style="font-weight: bold;"><span style="font-style: italic;"><span style="font-style: italic;"></span></span></span></span><span style="font-weight: bold;">Project to Annotate 1000 Genomes,
</span>and in this short essay I will argue that it has been an
overwhelming success due to issues that became apparent only as the
project progressed. &nbsp;&nbsp; A
thousand more-or-less complete genomes now exist, a framework for
rapidly annotating new genomes with remarkable accuracy is now
functioning, and we are on the verge of another major shift in the
world of annotations. &nbsp; This reflection is based on an
informal note that I sent to friends on the last day of 2007, but my
thoughts have clarified somewhat since then.<br>
<br>
<h3>The Production of Accurate Annotations</h3>
The efforts required to establish a framework for high-volume, accurate
annotation are substantial. &nbsp;I believe that it is important
that we reflect on what we have learned about the factors that
determine productivity. &nbsp;So, what have we learned from the
project?<br>
<br>
First, <span style="font-weight: bold;">subsystem-based
annotation</span> <span style="font-weight: bold;">is
the key to accuracy.</span> &nbsp; While there are certainly
numerous efforts still focusing on annotation of a single genome, the
recognition that comparative analysis is the key to everything, and
that focusing on the variations of a single component of cellular
machinery as they are manifested over the entire collection of existing
genomes is the key to accuracy, are both widely accepted
&nbsp;principles at this stage. &nbsp; <span style="font-weight: bold;">Manually-based subsystem creation
and maintenance is the rate-limiting component</span> of
successful annotation efforts, and the factors that constrain this
process are at the heart of the matter. &nbsp;We have understood
this for some time now. &nbsp;<br>
<br>
However, I am going to argue a new position in this short essay: <br>
<br>
<ol>
<li>There are three distinct components that make up our
strategy for rapid accurate annotation: <span style="font-weight: bold;">subsystems-based annotation</span>,
<span style="font-weight: bold;">FIGfams</span>
as a framework for propagating the subsystems annotations, and <span style="font-weight: bold;">RAST</span> as a technology
for using FIGfams and subsystems to consistently propagate annotations
to newly-sequenced genomes.</li>
<br>
<li>These three components form a cycle (subsystems =&gt;
FIGfams =&gt; RAST technology =&gt; subsystems). &nbsp;This
cycle creates a feedback that rapidly accelerates the productivity
achievable in all three components. &nbsp;Further, failure in any
of these components impairs productivity dramatically in the others.
&nbsp;Understanding this cycle will be the key to supporting higher
productivity in&nbsp; subsystem maintenance and creation.</li>
<br>
<li>To understand the dependencies, we need to consider each of
the components:</li>
<ul>
<br>
<li><span style="font-weight: bold;">The key to
accurate FIGfam creation and maintenance is to couple it directly to
subsystem maintenance</span>.
&nbsp;Once the initial release
of the FIGfams was created, updating them&nbsp; occurs
automatically
based
on changes in the subsystem collection. &nbsp;Thus, FIGfams are
automatically split, merged&nbsp;and added as the subsystem
collection is maintained. &nbsp;There remains one area of
substantial cost in FIGfam development -- creation of family-dependent
decision procedures that are occasionally required to achieve the
required accuracy. &nbsp;At this point we have approximately 10,000
subsystem-based FIGfams, although the overall collection contains over
100,000 families (the majority containing only 2-3 members).</li>
<br>
<li><span style="font-weight: bold;">RAST has a
central dependency on FIGfams</span> for assertion of function to
newly-recognized genes. &nbsp;In this sense, the main dependency of
RAST is on the FIGfam collection. &nbsp;The more accurate the
FIGfams and their associated decision procedures, the more accurate the
assignments of function made to genes in genomes processed by RAST.</li>
<br>
<li>Finally, the central costs of maintenance of subsystems
are cleaning up errors in existing subsystems (often indicated by
multiple genes having the same function) and by adding new genomes to
existing subsystems. &nbsp;Once a subsystem has reached an
acceptable level of accuracy (and many are not there yet), <span style="font-weight: bold;">the central cost is integration
of new genomes after annotation by RAST.</span> &nbsp;The
speed with which new genomes can be added depends on how well RAST
assigns gene function (and, secondarily, on how accurately these
RAST-based annotations can be used to &nbsp;infer operational
variants of subsystems).</li>
</ul>
<br>
<li>The main costs of increasing the speed and accuracy of
annotations split into two categories: those relating to maintenance of
existing subsystems, and those relating to generation of new
subsystems.
The maintenance costs are containable, if the cycle is established and
functions smoothly. &nbsp;Otherwise, I suspect they inevitably grow
rapidly.</li>
</ol>
Let me begin by depicting the cycle pictorially:<br>
<br>
<br>
<img src="cycle_files_image.gif" v:shapes="_x0000_i1025" height="647" width="810"><br>
<br>
<br>
I have argued that the costs in achieving rapid, accurate annotations
is
limited by the rate at which subsystems can be maintained and created.
&nbsp;I place the maintenance ahead of creation at this stage.
&nbsp;As the collection grows (it now contains over 600
subsystems with over 6800 distinct functional roles), costs of
maintenance will tend to dominate. &nbsp;The
creation of new subsystems will always be a critical activity, but each
new subsystem will impact smaller sets of genomes as we "move into the
tail of the distribution". &nbsp;<br>
<br>
The costs relating to subsystem maintenance, which will quickly
dominate, depend critically on how smoothly the cycle I described
functions. &nbsp;We have just established the complete cycle.<br>
<br>
The two central costs that cannot be avoided will be creation of
FIGfam-dependent decision procedures and the creation of new
subsystems. &nbsp;The manual work on FIGfams will be necessary to
achieve near-100% accuracy on annotation of seriously ambiguous
paralogs. &nbsp;However, in the vast majority of cases, this effort
will be restricted to specific curators who are willing to spend
massive effort to get things perfect. &nbsp; The more central cost
relates to manual curation of the subsystems.&nbsp;
<br>
<h3>More Effective Integration of Existing Annotation Efforts</h3>
In the section above, I reflected on the cycle that we shall depend
upon for supporting increased volume and accuracy of our own efforts.
&nbsp;Other groups are certainly experimenting with their own
solutions, and in some cases with clear successes. &nbsp;I have no
desire to rate these competing efforts. &nbsp; I sincerely believe
that cooperative activity is the key to
enhanced achievements by everyone. &nbsp;However, effective
cooperation is often elusive. &nbsp;I think that we have put in
place an extremely important mechanism for making cooperation much
easier, and the benefits more compelling.<br>
<br>
Anyone working for one of the main annotation efforts realizes that it
is not easy to really benefit from access to the annotation efforts of
other groups. &nbsp;The efforts required to characterize
discrepancies between local annotations and those produced externally
often outweigh any benefits that result.<br>
<br>
Two events of major importance have occurred:<br>
<br>
<ol>
<li>Both PIR and the SEED Project decided to build
correspondences between IDs used by different annotation projects.
&nbsp;The PIR effort produced <a href="%28http://pir.georgetown.edu/pirwww/iprolink/biothesaurus.shtml">BioThesaurus</a>
and the SEED effort produced <a href="http://clearinghouse.nmpdr.org/aclh.cgi">the
Annotation Clearing House</a>. &nbsp;The fact that it will
become trivial to reconcile IDs between the different annotation
efforts will undoubtedly support rapid increases in cross-linking
entries. &nbsp;The SEED is working with UniProt to cross-link
proteins from all of our complete genomes, and I am sure similar
efforts are happening between the other major annotation efforts.</li>
<br>
<li>Within the Annotation Clearing House, a project to allow
experts to assert that specific annotations are reliable (using
whatever IDs they wish) has been initiated. &nbsp;This has led to
many tens of thousands of assertions that specific annotations are
highly reliable. &nbsp;PIR is preparing a list of assertions that
they consider highly reliable, and both institutions are making these
lists openly available.</li>
</ol>
<br>
To see the utility of exchanging expert assertions in a framework in
which it is easy to compare the results, let me describe how we intend
to use these assertions:<br>
<br>
<ol>
<li>We begin with a 3-column table of reliable annotations
containing <span style="font-style: italic;">[ProteinID,AssertedFunction,IDofExpert]</span></li>
<br>
<li><span style="font-style: italic;"></span>We
then take our IDs and construct a 2-column table <span style="font-style: italic;">[FIG-function,AssertedFunction].</span>
&nbsp;This table gives a correspondence between each of our <span style="font-style: italic;">functional roles</span>
and the functional roles used by the expert making the assertion of
reliability.</li>
<br>
<li>Then, we go through this correspondence table (using both
tools and manual inspection) and split it into one set in which we
believe both columns are essentially identical and a second set that we
believe represent errors (either our own or those of the expert
asserting reliability). &nbsp;We anticipate that in most cases the
expert assertion will be accurate, which is what makes this exercise so
beneficial to ourselves.</li>
<br>
<li>We take the table of "essentially the same" assertions and
distribute it as a table of synonyms (which we consider to be a very
useful resource).</li>
</ol>
<br>
We are strongly motivated to resolve differences between our
annotations and high-reliability assertions made by experts.
&nbsp;The production of the table of synonyms both reduces the
effort to redo such a comparison in the future, but is also a major
asset by itself. &nbsp;I am confident that any serious annotation
group that participates will benefit, and I believe that these
exchanges will accelerate in 2008 and 2009.<br>
<br>
<h2>Summary</h2>
I have tried to express the significance of the cycle depicted above,
but I think that I failed to really convey the epiphany, so let me
end by expressing it somewhat more emphatically. &nbsp;I believe
that there will be a very rapid acceleration in the sequencing of new,
complete genomes (although frequently the quality of the sequence wil
be far from perfect, and I am willing to say that a genome in 100
contigs is "essentially complete"). &nbsp;Groups that now try to
provide accurate integrations of all (or most) complete genomes will be
strained heavily. &nbsp;The tendency will be to go one of two
directions:<br>
<br>
<ol>
<li>Some will swing to completely automated approaches.
&nbsp;This will result in rapid propagation of errors (for those
portions of the cellular mechanisms that are not yet accurately
characterized -- which is quite a bit).</li>
<br>
<li>Others will give up any attempt at comprehensive annotation
and focus on accurate annotation of a slowly growing subset.</li>
</ol>
The problem with the second approach is that accurate annotation of new
cellular mechanisms (i.e., the introduction of new subsystems) will
increasingly depend on a comprehensive set of genomes (comparative
analysis is central to working out any of the serious difficulties, and
the larger the set of accurately annotated genomes, the better
framework for careful correction.<br>
<br>
The cycle depicted above is the only viable strategy that I know of to
handle the deluge of genomes accurately. &nbsp;I claim that as time
goes by, the SEED effort to implement the above cycle will emerge in a
continuously strengthening position. &nbsp;Other groups will be
forced to rapidly copy it, but it really was not that easy to
establish, and I believe the odds are that the SEED effort will be the
only group standing in 2-3 years (i.e., it will be the only group
claiming both accuracy and comprehensive integration).<br>
<br>
<br>
</body></html>

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3