Team:Illinois-Tools/Modeling

From 2009.igem.org

(Difference between revisions)
(→The Algorithm)
 
(35 intermediate revisions not shown)
Line 1: Line 1:
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
__NOTOC__
-
!align="center"|[[Team:Illinois-Tools|Home]]
+
<div style="background-color: white; color: white">
-
!align="center"|[[Team:Illinois-Tools/Team|The Team]]
+
<html>
-
!align="center"|[[Team:Illinois-Tools/Project|The Project]]
+
<head>
-
!align="center"|[[Team:Illinois-Tools/Parts|Parts Submitted to the Registry]]
+
<style>
-
!align="center"|[[Team:Illinois-Tools/Modeling|Modeling]]
+
.firstHeading {display: none;}
-
!align="center"|[[Team:Illinois-Tools/ResearchArticles|Research Articles]]
+
table {
-
!align="center"|[[Team:Illinois-Tools/Notebook|Notebook]]
+
  background-color: #FFFFFF;
-
|}
+
  font-color: black;
 +
  color:white;
 +
}
 +
a.menu {
 +
  background-color: #FFFFFF;
 +
  color: black;
 +
  width: 12em;
 +
}
 +
 
 +
.firstHeading {
 +
  color:black;
 +
}
 +
 
 +
#bodyContent {
 +
background-color: #FFFFFF;
 +
}
 +
 
 +
#content {
 +
background-color: white;
 +
}
 +
 
 +
#footer-box {
 +
  background-color: white;
 +
}
 +
p {
 +
  color:black;
 +
}
 +
body {
 +
  background: white url(https://static.igem.org/mediawiki/2009/2/2b/IllinoisToolsBackground.gif) repeat-x;
 +
}
 +
 
 +
</style>
 +
</head>
 +
</html>
 +
[[Image:Modelingillinoistools.gif]]
 +
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 +
 
 +
<br>
 +
<head>
 +
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
 +
<style type="text/css" media="screen">
 +
#wrapper {
 +
width: 0%;
 +
}
 +
#header-wrapper {
 +
width: 965px;
 +
height: 35px;
 +
margin: 0px auto;
 +
padding: 0px;
 +
}
 +
/* Menu */
 +
 
 +
#menu {
 +
width: 965px;
 +
height: 35px;
 +
margin: 0px auto;
 +
padding-left: 20px;
 +
background: url(https://static.igem.org/mediawiki/2009/2/25/Menubarillinoistools.jpg) no-repeat left top;
 +
}
 +
 
 +
#menu ul {
 +
margin: 0px;
 +
padding: 0px;
 +
list-style: none;
 +
}
 +
 
 +
#menu li {
 +
float: left;
 +
}
 +
 
 +
#menu a {
 +
display: block;
 +
padding: 8px 20px 0px 22px;
 +
letter-spacing: -1px;
 +
text-decoration: none;
 +
font-size: 20px;
 +
font-weight: normal;
 +
color: #9ADCF8;
 +
}
 +
 
 +
#menu a:hover {
 +
text-decoration: underline;
 +
}
 +
        #menu a.active{color: #fff;}
 +
 
 +
#menu .first a {
 +
background: none;
 +
padding-left: 0px;
 +
}
 +
</style>
 +
  </head>
 +
<body>
 +
<div id="wrapper">
 +
<div id="header-wrapper">
 +
<div id="menu">
 +
<ul>
 +
<li class="first"><a href="https://2009.igem.org/Team:Illinois-Tools">Home</a></li>
 +
        <li><a href="https://2009.igem.org/Team:Illinois-Tools/Team" >The Team</a></li>
 +
        <li><a href="https://2009.igem.org/Team:Illinois-Tools/Project">The Project</a></li>
 +
                                <li><a href="https://2009.igem.org/Team:Illinois-Tools/Demo">Demo</a></li>
 +
                                <li><a href="https://2009.igem.org/Team:Illinois-Tools/Modeling"class="active">Modeling</a></li>
 +
                                <li><a href="https://2009.igem.org/Team:Illinois-Tools/Safety">Safety</a></li>
 +
                                <li><a href="https://2009.igem.org/Team:Illinois-Tools/Resources">Resources</a></li>
 +
                                <li><a href="https://2009.igem.org/Team:Illinois-Tools/Notebook">Notebook</a></li> 
 +
</ul>
 +
</div>
 +
</div>
 +
</div>
 +
</body>
 +
</html>
 +
<span style="color:#000000">
 +
 
 +
=='''Modeling'''==
 +
 
 +
The Illinois - Tools team can model any pathway, whose starting and ending compounds are stored in the Kegg database.  The algorithm developed by the team takes information from the Kegg database and finds the most optimum pathway, based on the weights selected by the user.  Examples include the pathway with the least number of steps, or the pathway that uses the least amount of ATP. 
 +
 
 +
The Illinois-Tools team also wishes to use this algorithm to help other IGEM teams in modeling their own desired pathways.  For example, the our program can help the Illinois wetlab team in modeling their pathway.  The wetlab team's project is about a binary decoder in the organism E. coli, that senses 2 inputs, such as 2 sugars, and produces one of four possible outputs, which are fluorescent proteins, based on the combination of inputs. 
 +
 
 +
Go to [https://2009.igem.org/Team:Illinois Illinois]  
 +
 
 +
A possible future expansion of their project would be to model these pathways computationally, and see if it would be experimentally feasible. Furthermore, once the protein output is obtained, they want to check if it can be used to produce useful compounds like biofuels.
 +
 
 +
To help this team reach its goals, our program, IMPtools, was able to model a pathway from D-Arabinose to Ethanol in E. coli.  The result can be seen below.  It has been optimized for E.coli, and can be further optimized when the wetlab team is ready to work on it.  The labels on the reaction are the Kegg IDs for compounds. 
 +
 
 +
[[Image:Illinoistoolsarabinosetoethanolpathway.jpg|center|]]
 +
 +
 
 +
===The Algorithm===
 +
 
 +
In modeling for other teams, a few things should be considered. The algorithm requires interactivity. It is can only optimize if you set the parameters to specify what you mean by "optimal". In that light, the user of IMPtools when modeling for a practical design application should consider how important removing excess reactants or creating biproducts could be, as well as the implications of ATP consumption. Sometimes the algorithm can return intermediate compounds that are truly only cofactors of a main reaction (these can generally be avoided by weighting against high order nodes, but also by specifically removing certain nodes). With IMPtools and a small amount of manipulation, a reasonable pathway can be returned using IMP's pathfinding algorithm. Using these results, actual experimentation is necessary to validate the pathway - perhaps, given future feedback the algorithm could account for user's successes and failures and preferentially bias results toward those experimentally validated.

Latest revision as of 03:46, 22 October 2009

Modelingillinoistools.gif

Modeling

The Illinois - Tools team can model any pathway, whose starting and ending compounds are stored in the Kegg database. The algorithm developed by the team takes information from the Kegg database and finds the most optimum pathway, based on the weights selected by the user. Examples include the pathway with the least number of steps, or the pathway that uses the least amount of ATP.

The Illinois-Tools team also wishes to use this algorithm to help other IGEM teams in modeling their own desired pathways. For example, the our program can help the Illinois wetlab team in modeling their pathway. The wetlab team's project is about a binary decoder in the organism E. coli, that senses 2 inputs, such as 2 sugars, and produces one of four possible outputs, which are fluorescent proteins, based on the combination of inputs.

Go to Illinois

A possible future expansion of their project would be to model these pathways computationally, and see if it would be experimentally feasible. Furthermore, once the protein output is obtained, they want to check if it can be used to produce useful compounds like biofuels.

To help this team reach its goals, our program, IMPtools, was able to model a pathway from D-Arabinose to Ethanol in E. coli. The result can be seen below. It has been optimized for E.coli, and can be further optimized when the wetlab team is ready to work on it. The labels on the reaction are the Kegg IDs for compounds.

Illinoistoolsarabinosetoethanolpathway.jpg


The Algorithm

In modeling for other teams, a few things should be considered. The algorithm requires interactivity. It is can only optimize if you set the parameters to specify what you mean by "optimal". In that light, the user of IMPtools when modeling for a practical design application should consider how important removing excess reactants or creating biproducts could be, as well as the implications of ATP consumption. Sometimes the algorithm can return intermediate compounds that are truly only cofactors of a main reaction (these can generally be avoided by weighting against high order nodes, but also by specifically removing certain nodes). With IMPtools and a small amount of manipulation, a reasonable pathway can be returned using IMP's pathfinding algorithm. Using these results, actual experimentation is necessary to validate the pathway - perhaps, given future feedback the algorithm could account for user's successes and failures and preferentially bias results toward those experimentally validated.

Retrieved from "http://2009.igem.org/Team:Illinois-Tools/Modeling"