Team:Edinburgh/Modelling

From 2010.igem.org

(Difference between revisions)
 
(12 intermediate revisions not shown)
Line 46: Line 46:
   <ul>
   <ul>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Protocol">the protocol</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Protocol">the protocol</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/BioBricks">submitted parts</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Genomic">submitted parts</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Results">results</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Genomic">results</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Future">future work</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Future">the future</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/References">references</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Project/References">references</a></li>
   </ul>
   </ul>
Line 55: Line 55:
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">bacterial BRIDGEs</a>
  <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">bacterial BRIDGEs</a>
   <ul>
   <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/Core_repressilator">the project</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_producer">red light</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_producer">red light</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_sensor">red sensor</a></li>
Line 62: Line 62:
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Green_light_producer">green light</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Green_light_producer">green light</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_sensor">green sensor</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/BioBricks">submitted parts</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Bacterial">submitted parts</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Results">results</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Bacterial">results</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Future">future work</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Future">the future</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/References">references</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/References">references</a></li>
   </ul>
   </ul>
Line 75: Line 75:
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Bacterial">the bacterial model</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Bacterial">the bacterial model</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Signalling">the signalling model</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Signalling">the signalling model</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Results">results</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Tools">tools</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">future work</a></li>
+
  <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Modelling">results</a></li>
 +
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">the future</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/References">references</a></li>
   <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/References">references</a></li>
   </ul>
   </ul>
Line 83: Line 84:
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">human BRIDGEs</a>
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">human BRIDGEs</a>
   <ul>
   <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/Communication">communication of science</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/Branding">iGEM survey</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/Conversations">conversations</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Human">references</a></li>
+
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human/Epic">the epic</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human/FutureApps">future applications</a></li>
 +
   <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Human">further thoughts</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Human/References">references</a></li>
   </ul>
   </ul>
  </li>
  </li>
Line 92: Line 96:
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook" class="dir">lab notes&nbsp;&nbsp;&nbsp;</a>
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook" class="dir">lab notes&nbsp;&nbsp;&nbsp;</a>
   <ul>
   <ul>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">collaboration</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Collaboration">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/Attribution">attribution</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/BRIDGE">BRIDGE</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/Red_light_producer">red light</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/Red_light_sensor">red sensor</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/Blue_light_producer">blue light</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">green light</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Blue_light_sensor">blue sensor</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">green sensor</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Green_light_producer">green light</a></li>
-
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook">safety</a></li>
+
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Green_light_sensor">green sensor</a></li>
 +
   <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Modelling">modelling</a></li>
 +
  <li><a href="https://2010.igem.org/Team:Edinburgh/Notebook/Safety">safety</a></li>
   <li><a href="http://www.openwetware.org/wiki/French_Lab">protocols</a></li>
   <li><a href="http://www.openwetware.org/wiki/French_Lab">protocols</a></li>
   </ul>
   </ul>
Line 114: Line 120:
<br>
<br>
-
<div id="body" style="padding: 0px 40px 10px 40px; height: 998px">
+
<div id="body" style="padding: 0px 60px 10px 60px; height: 998px">
<br>
<br>
Line 120: Line 126:
<br>
<br>
-
<a name="Introduction" id="Introduction"></a><h2>Modelling in Synthetic Biology</h2>
+
<a name="Introduction" id="Introduction"></a><h2>Modelling BRIDGEs</h2>
<br>
<br>
-
<p>An integral part of the engineering approach to biology is the use of modelling techniques that attempt to predict and understand the behaviour of complex biological systems before they are actually fabricated. One of the greatest advantages of models is that they can present an abstract picture of the activity of a part or device long before the actual biology - limited by the time needed for protocols such as PCR and transformation - can. Furthermore, they can help to simplify the mind-boggling amount and complexity of data and interactions involved into a more concise form with some measure of predictive ability.</p>
+
<p>An <b>integral</b> part of the engineering <b>approach</b> to biology is the use of modelling <b>techniques</b> that attempt to <b>predict</b> and <b>understand</b> the behaviour of complex biological systems before they are actually fabricated. One of the greatest advantages of models is that they can present an <b>abstract picture</b> of the activity of a part or device long before the actual biology - limited by the time needed for <b>protocols</b> such as PCR and transformation - can. Furthermore, they can help to <b>simplify</b> the mind-boggling amount and complexity of data and interactions involved into a more <b>concise</b> form with some measure of <b>predictive</b> ability.</p>
-
<p>On the other hand, modelling remains very much a guessing game. Abstractions and assumptions are made at every stage of the process, and even then the finished model will fail to capture all the intricacies of working in biology: interference between various parts and devices, the host not always being a benevolent chassis, and so forth. The extraction of meaningful biological data upon which to base the model, for example kinetic rate parameters, is an extremely time-consuming process, fraught with difficulty and inaccuracy .</p>
+
<p>On the other hand, modelling remains very much a <b>guessing game</b>. <b>Abstractions and assumptions</b> are made at every stage of the process, and even then the finished model will fail to capture all the intricacies of working in biology: interference between various parts and devices, the host not always being a benevolent chassis, and so forth. The extraction of meaningful biological data upon which to base the model, for example kinetic rate parameters, is an extremely time-consuming <b>process</b>, fraught with difficulty and inaccuracy .</p>
-
<p>Hence, biological modelling can be considered to be a little bit of a black art. If you're good, it will give you an answer; if you're very good, it might even be close to the truth.</p>
+
<p>Hence, biological modelling can be considered to be a little bit of a <b>black art</b>. If you're good, it will give you an answer; if you're very good, it might even be close to the truth.</p>
-
<p>Still, in order to effect in the future the rational design and engineering of biological systems, advances in modelling techniques remain crucial. As happened in chemistry in the 1940s and 1950s, capturing the enormous complexity of such processes in a way useful for applications can lead to the establishment of new and useful disciplines. It is our fervent hope that this section of our project has made at least some small progress in this direction.</p><br>
+
<p>Still, in order to effect in the future the <b>rational design and engineering</b> of biological systems, <b>advances</b> in modelling techniques remain crucial. As happened in chemistry in the 1940s and 1950s, <b>capturing</b> the enormous complexity of such processes in a way useful for <b>applications</b> can lead to the establishment of new and useful <b>disciplines</b>. It is our fervent hope that this section of our project has made at least some small <b>progress</b> in this direction.</p><br>
<br>
<br>
<a name="Project" id="Project"></a><h2>Our Project</h2>
<a name="Project" id="Project"></a><h2>Our Project</h2>
<br>
<br>
-
<p>Our primary goal was to ensure that all of our endeavours in the wet lab had a corresponding modelling element, including but not limited to a model for simulating the BRIDGE protocol, a model for the core repressilator system, and a model for each of the light sensor pathways and how they responded to stimulation by light of the appropriate wavelength.</p>
+
<p>Our primary <b>goal</b> was to ensure that all of our <b>endeavours</b> in the wet lab had a corresponding modelling element, including but not limited to a <a href="https://2010.igem.org/Team:Edinburgh/Modelling/Genomic">model for simulating the BRIDGE protocol</a>, <a href="https://2010.igem.org/Team:Edinburgh/Modelling/Bacterial#Repressilator">a model for the core repressilator system</a>, <a href="https://2010.igem.org/Team:Edinburgh/Modelling/Bacterial">a model for each of the light sensor pathways and how they responded to stimulation by light of the appropriate wavelength</a>, and <a href="https://2010.igem.org/Team:Edinburgh/Modelling/Signalling">a model for attempting to simulate a colony communicating as one via light</a>.</p>
-
<p>On the other hand, we didn't want to model just for the sake of modelling; in our opinion, modelling should always have a clear objective, aiding and adding to the biology in some way. For example, by highlighting possible problems or inefficiencies in the biological systems in question, or by testing two separate designs against one another to determine which of them would be more efficient in achieving the desired outcome, we would be able to solve theoretical conundrums and help our wet-lab team to eliminate unnecessary time and work. Although the time and feasibility constraints of the project and the setbacks we suffered along the way meant that this was not always possible, work continued throughout on refining and rebuilding the model to flexibly adapt to the continually evolving needs of our system.</p><br>
+
<p>On the other hand, we didn't want to model just for the sake of modelling; in our opinion, modelling should always have a clear <b>objective</b>, aiding and adding to the biology in some way. For example, by <b>highlighting</b> possible problems or inefficiencies in the biological systems in question, or by <b>testing</b> two separate designs against one another to determine which of them would be more efficient in achieving the desired outcome, we would be able to <b>solve</b> theoretical conundrums and <b>help</b> our wet-lab team to eliminate unnecessary time and work. Although the time and feasibility constraints of the project and the setbacks we suffered along the way meant that this was not always possible, work continued throughout on <b>refining</b> and <b>rebuilding</b> the model to flexibly <b>adapt</b> to the continually evolving needs of our system.</p><br>
<br>
<br>
Line 151: Line 157:
  </li>
  </li>
  <li>
  <li>
-
<a href="https://2010.igem.org/Team:Edinburgh/Modelling/Results">A summary of what we achieved through the construction and analysis of our models.</a>
+
<a href="https://2010.igem.org/Team:Edinburgh/Modelling/Tools">Some of the tools that we used during the modelling process, and an explanation for them.</a>
  </li>
  </li>
  <li>
  <li>
-
<a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">Our vision of the future, and where we would like to go next.</a>
+
<a href="https://2010.igem.org/Team:Edinburgh/Results#Modelling">A summary of what we achieved through the construction and analysis of our models.</a>
 +
</li>
 +
<li>
 +
<a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">Our vision of the future of the modelling process, and where we would like to go next.</a>
  </li>
  </li>
  <li>
  <li>
Line 166: Line 175:
<center><a href="#top" class="dir"><img width="100" src="https://static.igem.org/mediawiki/2010/9/9f/Ed10-RTT.png"></a></center>
<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 id="windowbox" style="border: .2em solid #660000; padding: 5px; position:fixed; top:50%; right:30px; width:8%;">
 +
<span style="color:ivory;">Throughout this wiki there are words in <b>bold</b> that indicate a relevance to <b>human aspects</b>. It will become obvious that <b>human aspects</b> are a part of almost everything in <b>iGEM</b>.</span>
</div>
</div>

Latest revision as of 15:13, 8 January 2011







Modelling BRIDGEs


An integral part of the engineering approach to biology is the use of modelling techniques that attempt to predict and understand the behaviour of complex biological systems before they are actually fabricated. One of the greatest advantages of models is that they can present an abstract picture of the activity of a part or device long before the actual biology - limited by the time needed for protocols such as PCR and transformation - can. Furthermore, they can help to simplify the mind-boggling amount and complexity of data and interactions involved into a more concise form with some measure of predictive ability.

On the other hand, modelling remains very much a guessing game. Abstractions and assumptions are made at every stage of the process, and even then the finished model will fail to capture all the intricacies of working in biology: interference between various parts and devices, the host not always being a benevolent chassis, and so forth. The extraction of meaningful biological data upon which to base the model, for example kinetic rate parameters, is an extremely time-consuming process, fraught with difficulty and inaccuracy .

Hence, biological modelling can be considered to be a little bit of a black art. If you're good, it will give you an answer; if you're very good, it might even be close to the truth.

Still, in order to effect in the future the rational design and engineering of biological systems, advances in modelling techniques remain crucial. As happened in chemistry in the 1940s and 1950s, capturing the enormous complexity of such processes in a way useful for applications can lead to the establishment of new and useful disciplines. It is our fervent hope that this section of our project has made at least some small progress in this direction.



Our Project


Our primary goal was to ensure that all of our endeavours in the wet lab had a corresponding modelling element, including but not limited to a model for simulating the BRIDGE protocol, a model for the core repressilator system, a model for each of the light sensor pathways and how they responded to stimulation by light of the appropriate wavelength, and a model for attempting to simulate a colony communicating as one via light.

On the other hand, we didn't want to model just for the sake of modelling; in our opinion, modelling should always have a clear objective, aiding and adding to the biology in some way. For example, by highlighting possible problems or inefficiencies in the biological systems in question, or by testing two separate designs against one another to determine which of them would be more efficient in achieving the desired outcome, we would be able to solve theoretical conundrums and help our wet-lab team to eliminate unnecessary time and work. Although the time and feasibility constraints of the project and the setbacks we suffered along the way meant that this was not always possible, work continued throughout on refining and rebuilding the model to flexibly adapt to the continually evolving needs of our system.



Table of Contents





Throughout this wiki there are words in bold that indicate a relevance to human aspects. It will become obvious that human aspects are a part of almost everything in iGEM.