Team:Edinburgh/Modelling

From 2010.igem.org

(Difference between revisions)
Line 9: Line 9:
<style type="text/css">
<style type="text/css">
-
#content{
+
#body{
-
background-color: darkslategray;
+
background-image:url(https://static.igem.org/mediawiki/2010/a/a8/Ed10-LargePaper.jpg);
-
font-family: tahoma, arial;
+
background-repeat:repeat-y;
-
font-weight: bold;
+
-
color: ivory;
+
-
}
+
-
 
+
-
table{
+
-
text-align:justify;
+
-
background-color: darkslategray;
+
-
font-family: tahoma, arial;
+
-
font-weight: bold;
+
-
color: ivory;
+
-
}
+
-
 
+
-
A:link{
+
-
text-decoration: none;
+
-
color: darkgray;
+
-
}
+
-
 
+
-
A:visited{
+
-
text-decoration: none;
+
-
color: darkgray;
+
-
}
+
-
 
+
-
A:active{
+
-
text-decoration: none;
+
-
color: darkgray;
+
-
}
+
-
 
+
-
A:hover{
+
-
text-decoration: none;
+
-
color: #CC3333;
+
}
}
Line 49: Line 19:
<body>
<body>
 +
 +
<div id="banner"><a href="https://2010.igem.org/Team:Edinburgh"><img src="https://static.igem.org/mediawiki/2010/5/5f/Ed10-Banner.jpg" /></a></div>
<a href="top"></a>
<a href="top"></a>
-
<hr>
+
<br>
<div id="nav">
<div id="nav">
-
<ul id="nav" class="dropdown dropdown-horizontal">
+
<ul class="dropdown dropdown-horizontal">
-
  <li><a href="https://2010.igem.org/Team:Edinburgh"><img src="https://static.igem.org/mediawiki/2010/c/ce/Invertedlogo.jpg" border="0" width="40" height="40"></a></li>
+
  <li style="width:11%;"><a href="https://2010.igem.org/Team:Edinburgh/Team" class="dir">The Illuminati</a>
-
 
+
  <ul>
-
<li><a href="https://2010.igem.org/Team:Edinburgh/Team" class="dir">The Illuminati</a>
+
  <li><a href="https://2010.igem.org/Team:Edinburgh/Team/Supervisors">Supervisors</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Team/Advisors">Advisors</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Team/Students">Students</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Team/Environment">Environment</a></li>
 +
  </ul>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project" class="dir">BRIDGE: The Protocol</a>
+
  <li style="width:14%;"><a href="https://2010.igem.org/Team:Edinburgh/Project" class="dir">Genomic BRIDGEs</a>
 +
  <ul>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project">The Protocol</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project">BioBrick Parts</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project">Results</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project">Future Work</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Project">References</a></li>
 +
  </ul>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">Bacterial BRIDGEs</a>
+
  <li style="width:14%;"><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">Bacterial BRIDGEs</a>
 +
  <ul>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Core_repressilator">The Repressilator</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_sensor">Red Sensor</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_producer">Red Producer</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Blue_light_sensor">Blue Sensor</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Blue_light_producer">Blue Producer</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Green_light_sensor">Green Sensor</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Green_light_producer">Green Producer</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial">The Project</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial">BioBrick Parts</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial">Results</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial">Future Work</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial">References</a></li>
 +
  </ul>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling" class="dir">Modelling BRIDGEs</a>
+
  <li style="width:15%;"><a href="https://2010.igem.org/Team:Edinburgh/Modelling" class="dir">Modelling BRIDGEs</a>
 +
  <ul>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling">The Model</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling">Results</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling">Future Work</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling">References</a></li>
 +
  </ul>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">Human BRIDGEs</a>
+
  <li style="width:14%;"><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">Human BRIDGEs</a>
 +
  <ul>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human">Human Aspects</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human">Results</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human">Future Work</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human">References</a></li>
 +
  </ul>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook" class="dir">Notebook</a>
+
  <li style="width:10%;"><a href="https://2010.igem.org/Team:Edinburgh/Notebook" class="dir">Notebooks&nbsp;&nbsp;&nbsp;&nbsp;</a>
 +
  <ul>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Collaboration</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">BRIDGE</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Red Light</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Red Sensor</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Blue Light</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Blue Sensor</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">Protocols</a></li>
 +
  </ul>
  </li>
  </li>
   
   
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Gallery" class="dir">Gallery</a>
+
  <li style="width:10%;"><a href="https://2010.igem.org/Team:Edinburgh/Gallery" class="dir">&nbsp;&nbsp;&nbsp;&nbsp;Gallery&nbsp;&nbsp;&nbsp;&nbsp;</a>
  </li>
  </li>
-
  <li><a href="https://2010.igem.org/Team:Edinburgh/Acknowledgements" class="dir">Acknowledgements</a>
+
  <li style="width:10%;"><a href="https://2010.igem.org/Team:Edinburgh/Acknowledgements" class="dir">Acknowledgements</a>
  </li>
  </li>
Line 90: Line 108:
<br>
<br>
-
<hr>
+
<div id="body" style="padding: 0px 40px 10px 40px; height: 1356px">
-
 
+
-
<div>
+
 +
<br>
<br>
<br>
<br>
<br>
Line 99: Line 116:
<p>In order to model the core repressilator system and its attached signal transduction pathways, we are using a stochastic, agent- and rule-based language called Kappa.<p>
<p>In order to model the core repressilator system and its attached signal transduction pathways, we are using a stochastic, agent- and rule-based language called Kappa.<p>
-
<center><br><p><img src="https://static.igem.org/mediawiki/2010/1/12/KappaAgent.jpg" /></p><br></center>
+
<center><br><br><p><img src="https://static.igem.org/mediawiki/2010/5/5c/Ed10-Agent.jpg" /></p><br><br></center>
<p>In Kappa, biological entities such as proteins, DNA, and RNA are represented as agents, which are essentially named sets of sites that can be used to hold state or bind and interact with other agents. The example shown shows how a promoter BioBrick can be represented within Kappa – as a three-agent-long piece of DNA, connected via upstream and downstream sites, with binding sites for transcription factors and RNA polymerase, and a type site to keep track of its Registry code.</p>
<p>In Kappa, biological entities such as proteins, DNA, and RNA are represented as agents, which are essentially named sets of sites that can be used to hold state or bind and interact with other agents. The example shown shows how a promoter BioBrick can be represented within Kappa – as a three-agent-long piece of DNA, connected via upstream and downstream sites, with binding sites for transcription factors and RNA polymerase, and a type site to keep track of its Registry code.</p>
-
<center><br><p><img src="https://static.igem.org/mediawiki/2010/c/cb/KappaRule.jpg" /></p><br></center>
+
<center><br><br><p><img src="https://static.igem.org/mediawiki/2010/9/9e/Ed10-Rule.JPG" /></p><br><br></center>
<p>Interactions are represented by rules in the form of precondition and effect, with an associated rate of reaction that governs how frequently the interaction occurs. The example shown describes a repressor binding to an open binding site upon a promoter; note the preconditions that both promoter and repressor binding sites must be empty beforehand, and the effect that they are now bound together. In this case, the reaction is reversible; that is, there are both forward and backward reaction rates associated with binding and dissociation of the repressor upon the promoter. By combining agents with an appropriate set of rules and rates, a Kappa model can be used to simulate systems of varying complexity, from a simple MAPK cascade to the oscillating rhythm of a circadian clock.</p>
<p>Interactions are represented by rules in the form of precondition and effect, with an associated rate of reaction that governs how frequently the interaction occurs. The example shown describes a repressor binding to an open binding site upon a promoter; note the preconditions that both promoter and repressor binding sites must be empty beforehand, and the effect that they are now bound together. In this case, the reaction is reversible; that is, there are both forward and backward reaction rates associated with binding and dissociation of the repressor upon the promoter. By combining agents with an appropriate set of rules and rates, a Kappa model can be used to simulate systems of varying complexity, from a simple MAPK cascade to the oscillating rhythm of a circadian clock.</p>
-
<center><br><p><img src="https://static.igem.org/mediawiki/2010/7/7e/KappaMoodlightingV2.png" /></p><br></center>
+
</div>
 +
 
 +
<div id="body" style="padding: 0px 40px 10px 40px; height: 1356px">
 +
<br>
 +
<br>
 +
 
 +
<center><br><br><p><img src="https://static.igem.org/mediawiki/2010/9/92/Ed10-V2Results.png" /></p><br><br></center>
<p>The results of the simulation shown track the discrete counts of lambda-cI (red), TetR (blue), and LacI (yellow) in a slightly-modified version of the Elowitz repressilator described previously, for one particular stochastic trajectory (obviously, different runs of the simulation will generate different results, some more variable than others). The modification made was the addition of a red luciferase BioBrick linked to a lacI promoter; high amounts of lacI repress the production of the red luciferase, but as soon as the concentration of lacI falls, the amount of red luciferase in the system rises, as expected. Ultimately, we wish to be able to simulate and study the effects of various perturbations upon the functionality of the repressilator, with the aim of aiding in the understanding, characterisation, and possibly even the design of the system itself..</p>
<p>The results of the simulation shown track the discrete counts of lambda-cI (red), TetR (blue), and LacI (yellow) in a slightly-modified version of the Elowitz repressilator described previously, for one particular stochastic trajectory (obviously, different runs of the simulation will generate different results, some more variable than others). The modification made was the addition of a red luciferase BioBrick linked to a lacI promoter; high amounts of lacI repress the production of the red luciferase, but as soon as the concentration of lacI falls, the amount of red luciferase in the system rises, as expected. Ultimately, we wish to be able to simulate and study the effects of various perturbations upon the functionality of the repressilator, with the aim of aiding in the understanding, characterisation, and possibly even the design of the system itself..</p>
 +
 +
<br>
<p>For more information regarding Kappa and the basics of the language, please see the following resources:</p>
<p>For more information regarding Kappa and the basics of the language, please see the following resources:</p>
Line 124: Line 149:
<br>
<br>
 +
<center><a href="#top" class="dir"><img width="100" src="https://static.igem.org/mediawiki/2010/9/9f/Ed10-RTT.png"></a></center>
</div>
</div>
-
 
-
<hr>
 
-
 
-
<div id="nav">
 
-
<ul id="nav" class="dropdown dropdown-horizontal">
 
-
 
-
<li><a href="https://2010.igem.org/Team:Edinburgh"><img src="https://static.igem.org/mediawiki/2010/c/ce/Invertedlogo.jpg" border="0" width="40" height="40"></a></li>
 
-
 
-
<li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial#top" class="dir">Return to Top</a>
 
-
</li>
 
-
 
-
</ul>
 
-
</div>
 
-
 
-
<br>
 
-
<br>
 
-
<br>
 
-
 
-
<hr>
 
</body>
</body>
</html>
</html>

Revision as of 09:54, 6 August 2010








In order to model the core repressilator system and its attached signal transduction pathways, we are using a stochastic, agent- and rule-based language called Kappa.





In Kappa, biological entities such as proteins, DNA, and RNA are represented as agents, which are essentially named sets of sites that can be used to hold state or bind and interact with other agents. The example shown shows how a promoter BioBrick can be represented within Kappa – as a three-agent-long piece of DNA, connected via upstream and downstream sites, with binding sites for transcription factors and RNA polymerase, and a type site to keep track of its Registry code.





Interactions are represented by rules in the form of precondition and effect, with an associated rate of reaction that governs how frequently the interaction occurs. The example shown describes a repressor binding to an open binding site upon a promoter; note the preconditions that both promoter and repressor binding sites must be empty beforehand, and the effect that they are now bound together. In this case, the reaction is reversible; that is, there are both forward and backward reaction rates associated with binding and dissociation of the repressor upon the promoter. By combining agents with an appropriate set of rules and rates, a Kappa model can be used to simulate systems of varying complexity, from a simple MAPK cascade to the oscillating rhythm of a circadian clock.







The results of the simulation shown track the discrete counts of lambda-cI (red), TetR (blue), and LacI (yellow) in a slightly-modified version of the Elowitz repressilator described previously, for one particular stochastic trajectory (obviously, different runs of the simulation will generate different results, some more variable than others). The modification made was the addition of a red luciferase BioBrick linked to a lacI promoter; high amounts of lacI repress the production of the red luciferase, but as soon as the concentration of lacI falls, the amount of red luciferase in the system rises, as expected. Ultimately, we wish to be able to simulate and study the effects of various perturbations upon the functionality of the repressilator, with the aim of aiding in the understanding, characterisation, and possibly even the design of the system itself..


For more information regarding Kappa and the basics of the language, please see the following resources: