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

View of /FigTutorial/subsystems_notion.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (download) (as text) (annotate)
Sun Mar 11 00:21:50 2007 UTC (12 years, 8 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 the writeup on the notion of subsystem

<h1>Subsystems: the Notion</h1>
<h2>by Ross Overbeek</h2>

I believe that there is a need to understand precisely what is meant by the term <i>subsystem</i>.
The notion of <i>metabolic reconstructions</i> was originally
formulated by Evgeni Selkov.  There was no precise definition of what
was meant, but the essential ideas he advanced have profoundly
effected what followed.  Perhaps, the first step was made when several
systems started putting up metabolic maps and connecting genes to the
enzymatic roles.  In most cases, the connections were forged using EC
numbers.   The feeling was that it was adequate to group the genes
into small sets connected to an EC (in cases in which there were
multiple subunits or multiple copies of a single gene).  It is clear
to me that these early efforts were hugely productive and laid the
foundation for what followed.
<p>
When we began the <b>Project to Annotate 1000 Genomes (P1K)</b>, we
introduced the notion of subsystems.
<br><br>
<b>Definition: a subsystem is a collection of functional roles.</b>  A
functional role is an atomic (undefined primitive) notion.  
<br><br>
Loosely,
it corresponds to the abstract function performed by a single protein
sequence.  For example,
<ul>
<li> Holliday junction DNA helicase RuvB
<li> 1-deoxy-D-xylulose 5-phosphate synthase (EC 2.2.1.7)
<li> ATP-dependent Clp protease proteolytic subunit (EC 3.4.21.92)
<li> SSU ribosomal protein S1p
</ul>
are all functional roles used in existing subsystems.
<br><br>
We tend to think of "binding" genes to one or more functional roles as
a central component of the annotation process.  The functional role is
an abstract platonic concept; binding a gene to the functional role
amounts to an assertion that the given gene implements the designated
functional role.
<<br><br>

<b>Definition: a subsystem spreadsheet is a spreadsheet in which the
rows are genomes, the columns are functional roles, and each cell
includes IDs of genes/gene products that are believed to implement the
functional role in the specific genome. </b>
<br><br>
The spreadsheet represents precisely which genes in which organisms
implement each of the functional roles.
<br><br>
<b>Definition: a populated subsystem is a subsystem plus a subsystem
spreadsheet. </b>

<br><br>

So, how does this differ from older systems like PUMA, WIT, KEGG,
ERGO, MetaCyc, and PUMA-2?  There are two basic differences:
<ol>
<li>The primary difference is the type of thing to which genes are
bound.  In the case of these early systems, genes are bound to
reactions or enzymatic functions (this is not completely true anymore,
but in essence we believe that it still holds in most cases).  In the
case of subsystems, genes are bound to functional roles.  This gives
one more precision in the case of subsystems.  In the case of a
complex, there will usually be distinct functional roles for each
subunit.  In the case on nonenzymatic processes, one has complete
freedom in formulating the text string to represent the functional
role. 
<li> The second primary difference relates to diagrams.  In the case
of these earlier systems, diagrams played a central role.  In effect,
genes were bound to objects in a diagram.  In the case of subsystems,
there is normally an associated diagram, and that diagram usually
includes an object corresponding to a functional role; however, there
is no need to supply a diagram for the subsystem -- the thing to which
genes are bound is an abstract notion of functional role.
</ol>

<br><br>
We believe that the notion of subsystem is a significant advance.  By
providing the additional preciksion offered by functional roles, it
becomes possible to separate things like 
<ul>
<li><i>Threonine dehydratase, catabolic (EC 4.3.1.19)</i> and
<li><i>Threonine dehydratase (EC 4.3.1.19)</i>
</ul>
Different subsystems might include either or both of these functional
roles.

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3