Difference between revisions of "Team:UNOTT/Model"

 
(40 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{:Team:UNOTT/Template/NavBarTest}}
 
{{:Team:UNOTT/Template/NavBarTest}}
 
+
</DIV>
  
 
<html>
 
<html>
  
 
<head>
 
<head>
  <center> <h1 class="box_header1"> Modelling </h1> </center>
+
<br> </br>
 +
  <center> <h1 class="box_header1"> Modelling  
 +
&nbsp; <span style="color: #ffffff;">&nbsp;</span>
 +
</h1> </center>
 +
<span style="color: #ffffff;">&nbsp;</span>
 +
<p><span style="color: #ffffff;">&nbsp;</span></p>
 +
 
 
   <link href="https://fonts.googleapis.com/css?family=Montserrat" rel="stylesheet">
 
   <link href="https://fonts.googleapis.com/css?family=Montserrat" rel="stylesheet">
 
   <link href="https://fonts.googleapis.com/css?family=Karla" rel="stylesheet">
 
   <link href="https://fonts.googleapis.com/css?family=Karla" rel="stylesheet">
Line 12: Line 18:
 
     <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/meyer-reset/2.0/reset.min.css">
 
     <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/meyer-reset/2.0/reset.min.css">
 
<style>
 
<style>
 +
table, th, td {
 +
    border: 1px solid black;
 +
}
  
 
body {
 
body {
Line 90: Line 99:
 
   margin-bottom: 10px;
 
   margin-bottom: 10px;
 
}
 
}
 
+
li {
 +
  color: #000000;
 +
  margin-bottom: 10px;
 +
}
 
.ad {
 
.ad {
 
   color: #fff;
 
   color: #fff;
Line 98: Line 110:
 
.white-bg{
 
.white-bg{
 
     background-color: #ffffff;
 
     background-color: #ffffff;
     padding-left: 350px;
+
     padding-left: 5%;
     padding-right: 350px;
+
     padding-right: 5%;
 
}
 
}
  
Line 106: Line 118:
 
</head>
 
</head>
  
<body>
+
 
 
<div class="white-bg";>
 
<div class="white-bg";>
  
Line 113: Line 125:
 
    
 
    
 
<div class="box_content">
 
<div class="box_content">
 +
 
<p>When developing <i> Key. coli</i>, we found it was important to mathematically model possible situations in order to investigate the effects of different situations that we might encounter throughout different stages of development as well as during implementation. </p>
 
<p>When developing <i> Key. coli</i>, we found it was important to mathematically model possible situations in order to investigate the effects of different situations that we might encounter throughout different stages of development as well as during implementation. </p>
<p> Software was developed to compare the fluorescence levels of the key colony with the mother colony to check if there was a high enough degree of similarity.</p>
+
 
<p> This information was used by the wet lab to assist them by informing them in what to expect. This was done through the use of programming to create visual graphs and simulations, as well as development of tools to allow for comparison between fluorescence levels without needing to actually create more synthetic organisms. Another advantage is that this is far quicker than creating these results in the lab. </p>
+
<p>A major problem the project faced is that the comparison process of the fluorescence proteins wouldn't be possible to be investigated with all combinations as it would take too long. </p>
<p> <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/Tellurium%20-%20Python%20Models%20for%20IGEM%20NOTTS%202017">The source code for these models can be accessed from our GitHub page</a> </p>
+
<p> To answer this problem, the team attempted to model the fluorescence spectra over time expressed by each different protein. First, the type of gene expression was identified and then, the model was refined to take into account gene inhibition (whether the gene is expressed or not) and finally, applied over time to see how much expression would occur at a certain time period. The team used mathematical modelling such as Ordinary Differential Equations because they were easy to convert into programming in order to build components for the simulation.</p>
<p> The models were not perfect at first: refinement from lab results helped to optimize and correct the models.</p>
+
 
 +
<p> This information was used by the wet lab to assist them by informing them in what to expect. This was done through the use of programming to create visual graphs and simulations, as well as development of tools to allow for comparison between fluorescence levels without needing to actually create more synthetic organisms. One advantage of this was it allowed for data to be easily read and understood by the team, rather than reading a wall of numbers. Another advantage is that this is far quicker than creating these results in the lab. </p>
 +
 
 +
<p> One limitation of models the team found out that they were too high level to accurately predict and represent all the processes that would be undertaken during the random constructions of the fluorescent proteins. This is an issue because this means the models weren't perfect to describe the real life, which however, suggests, they could undergo more refining and improving. </p>
 +
 
 +
<p> Software was developed to compare the fluorescence levels of the key colony with the mother colony to check if there was a high enough degree of similarity. The mother colony is defined as the colony of bacteria that is securely kept within the facility and whose fluorescence acts as a verification for the key colony, which is defined as the bacteria which is taken from the mother colony and given to a person who own's a Key.Coli container. </p>
 +
 
 +
<p> As a side project, the team investigated into whether our method is random and unique by investigating how many combinations we could make and whether we could accurately predict which combination will occur. </p>
  
 
   </div>
 
   </div>
Line 125: Line 145:
 
<div class="box">
 
<div class="box">
 
   <h3 class="box_header">Modelling Aims </h3>
 
   <h3 class="box_header">Modelling Aims </h3>
   <div class="box_content">
+
   <div class="box_content">
<p> <li> To assist the processes within the wet lab by informing them and allowing for simulations. This would be especially useful when predicting the required fluorescence </li> </p>
+
<p> The first aim is to assist the processes within the wet lab by informing them of what spectra they can expect through the use of simulations. This would be especially useful when predicting the required fluorescence </p>
<p> <li> Test our biological systems with conditions that might not be possible to replicate in a lab environment. This allows us to future proof our methods as well as identify any vulnerabilities </li> </p>
+
<p> The second is to test our biological systems with conditions that might not be possible to replicate in a lab environment. This allows us to future proof our methods as well as identify any vulnerabilities further down the line as well as save time and money on testing these conditions, if we were to. </p>  
&nbsp;
+
<p>In order to achieve these aims, we decided on an end goal of writing a Simulation for measuring Fluorescence Intensity when given parameters such as protein concentrations and wavelengths of lasers. </p>
 
+
<br></br>
<p>In order to achieve these aims, we created a simulation for measuring fluorescence intensity when given parameters such as protein concentrations and wavelengths of lasers. </p>
+
<p style="text-align: center;" > <a href="https://2017.igem.org/Team:UNOTT/Modelling">Find out more about our modeling</a> </p>
<p><a href="https://2017.igem.org/Team:UNOTT/Modelling">Find out more about our modeling</a> </p>
+
<p style="text-align: center;" > <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/tree/master/Models">The source code for these models can be accessed from our GitHub page</a> </p>
<p><a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/LuciferA.c">This simulation can be downloaded from our GitHub page.</a> </p>
+
 
+
 
   </div>
 
   </div>
 
</div>
 
</div>
Line 140: Line 158:
 
   <h3 class="box_header">Software Aims</h3>
 
   <h3 class="box_header">Software Aims</h3>
 
   <div class="box_content">
 
   <div class="box_content">
<li> To check between fluorescence levels during implementation of Key.Coli between the mother colony and the Key.Coli capsules. </li>
+
<p> The main objective of software was to check between fluorescence levels during implementation of Key.Coli between the mother colony and the Key.Coli capsules. </p>
<li> Develop an internal development environment to help next year's iGEM team quickly develop models as well as software.</li>
+
<p> In order to achieve this objective, the team decided to investigate into image comparison and raw data comparison with data from the fluorescence reader. These were programmed using data from the models and a threshold value was set using data from the wet lab to ensure not just any file being compared would get verified. </p>
&nbsp;
+
 
<p>In order to achieve these aims, we created an image comparing software as well as an internal development environment where members can easily add their own code as well as access other code made by others and other files. </p>
+
<p> A strong emphasis was placed on effectiveness of the software and efficiency; we wanted the software to run on low end hardware but still be useful without compromises. </p>
<p> <a href="https://2017.igem.org/Team:UNOTT/CultureModelling">Find out more about our software </a> </p>
+
<br> </br>
<p> <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/LuciferA.c">This environment can be downloaded from our GitHub page</a> </p>
+
<p style="text-align: center;" > <a href="https://2017.igem.org/Team:UNOTT/Software">Find out more about our software </a> </p>
 +
<p style="text-align: center;" > <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/tree/master/Software">Our software can be downloaded from our GitHub page</a> </p>
 
   </div>
 
   </div>
 
</div>
 
</div>
  
 
<div class="box">
 
<div class="box">
   <h3 class="box_header">Species</h3>
+
   <h3 class="box_header">Parameters</h3>
 
   <div class="box_content">
 
   <div class="box_content">
<p>Species hi!</p>
+
 
 +
<p> Inputs and Outputs </p>  
 +
<table style="width:100%">
 +
  <tr>
 +
    <th>Parameter</th>
 +
    <th>Unit</th>
 +
  </tr>
 +
  <tr>
 +
    <td>Protein Concentration</td>
 +
    <td>ug / mol </td>
 +
  </tr>
 +
  <tr>
 +
    <td>mRNA Concentration</td>
 +
    <td>ug / mol </td>
 +
  </tr>
 +
  <tr>
 +
    <td>Fluorescence</td>
 +
    <td>RFU (Relative Fluorescence Unit) </td>
 +
  </tr>
 +
  <tr>
 +
    <td>Time</td>
 +
    <td>Hours / Hrs</td>
 +
  </tr>
 +
</table>
 +
 
 +
<p> Rates of change </p>
 +
<table style="width:100%">
 +
  <tr>
 +
    <th>Parameter</th>
 +
    <th>Unit</th>
 +
  </tr>
 +
  <tr>
 +
    <td>Protein Degradation</td>
 +
    <td>Nanograms per microlitre per minute</td>
 +
  </tr>
 +
<tr>
 +
    <td>mRNA Degradation</td>
 +
    <td>Nanograms per microlitre per minute</td>
 +
  </tr>
 +
<tr>
 +
    <td>Translation </td>
 +
    <td>Number of protein molecules produced per mRNA molecule, per unit of time</td>
 +
  </tr>
 +
<tr>
 +
    <td>Transcription </td>
 +
    <td>Number of mRNA molecules produced per gene, per unit of time.</td>
 +
  </tr>
 +
</table>
 +
 
 
   </div>
 
   </div>
 
</div>
 
</div>
Line 167: Line 234:
  
 
{{:Team:UNOTT/Template/Footer}}
 
{{:Team:UNOTT/Template/Footer}}
 
<!--
 
 
{{:Team:UNOTT/Template/NavBarTest}}
 
<html>
 
<style>
 
input, button, submit
 
{
 
  border:none;
 
  background  : none;
 
}
 
 
</style>
 
 
<body>
 
<div class="column full_size" style="background:#dbffd8">
 
<center>
 
<br> </br>
 
<h1>Overview</h1>
 
&nbsp;
 
&nbsp;
 
<div id="clear">
 
<head>
 
 
 
</head>
 
<p>When developing <i> Key. coli</i>, we found it was important to mathematically model possible situations in order to investigate the effects of different situations that we might encounter throughout different stages of development as well as during implementation. </p>
 
<p> Software was developed to compare the fluorescence levels of the key colony with the mother colony to check if there was a high enough degree of similarity.</p>
 
<br></br>
 
<p> This information was used by the wet lab to assist them by informing them in what to expect. This was done through the use of programming to create visual graphs and simulations, as well as development of tools to allow for comparison between fluorescence levels without needing to actually create more synthetic organisms. Another advantage is that this is far quicker than creating these results in the lab. </p>
 
<a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/Tellurium%20-%20Python%20Models%20for%20IGEM%20NOTTS%202017">The source code for these models can be accessed from our GitHub page</a>
 
The models were not perfect at first: refinement from lab results helped to optimize and correct the models.</h5>
 
&nbsp;
 
</center>
 
</div>
 
</div>
 
</div>
 
 
<script>
 
  var toggle3 = function() {
 
  var mydiv = document.getElementById('clear3');
 
  if (mydiv.style.display === 'block' || mydiv.style.display === '')
 
    mydiv.style.display = 'none';
 
  else
 
    mydiv.style.display = 'block'
 
  }
 
</script>
 
 
<div class="column full_size"  style="background:#d8fff7">
 
<center>
 
<h2><button onclick="toggle3();">Modelling Aims </button></h2>
 
<div id="clear3" style="display: none;">
 
<ol><div id="demoFont">
 
<li> To assist the processes within the wet lab by informing them and allowing for simulations. This would be especially useful when predicting the required fluorescence </li>
 
<li> Test our biological systems with conditions that might not be possible to replicate in a lab environment. This allows us to future proof our methods as well as identify any vulnerabilities </li> 
 
&nbsp;
 
&nbsp;
 
<p>In order to achieve these aims, we created a simulation for measuring fluorescence intensity when given parameters such as protein concentrations and wavelengths of lasers. </li>
 
<p><a href="https://2017.igem.org/Team:UNOTT/Modelling">Find out more about our modeling</a>
 
<p><a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/LuciferA.c">This simulation can be downloaded from our GitHub page.</a>
 
</div>
 
</center>
 
</div>
 
 
<script>
 
  var toggled = function() {
 
  var mydiv = document.getElementById('cleard');
 
  if (mydiv.style.display === 'block' || mydiv.style.display === '')
 
    mydiv.style.display = 'none';
 
  else
 
    mydiv.style.display = 'block'
 
  }
 
</script>
 
 
<div class="column full_size"  style="background:#d8ecff">
 
<center>
 
<h2><button onclick="toggled();">Software Aims </button></h2>
 
<div id="cleard" style="display: none;"><div id="demoFont">
 
<ol>
 
<li> To check between fluorescence levels during implementation of Key.Coli between the mother colony and the Key.Coli capsules. </li>
 
<li> Develop an internal development environment to help next year's iGEM team quickly develop models as well as software.</li> 
 
&nbsp;
 
&nbsp;
 
<p>In order to achieve these aims, we created an image comparing software as well as an internal development environment where members can easily add their own code as well as access other code made by others and other files.
 
<p> <a href="https://2017.igem.org/Team:UNOTT/CultureModelling">Find out more about our software </a>
 
<p> <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/LuciferA.c">This environment can be downloaded from our GitHub page</a>
 
</div>
 
</center>
 
</div>
 
 
 
<script>
 
  var toggle1 = function() {
 
  var mydiv = document.getElementById('clear2');
 
  if (mydiv.style.display === 'block' || mydiv.style.display === '')
 
    mydiv.style.display = 'none';
 
  else
 
    mydiv.style.display = 'block'
 
  }
 
</script>
 
 
<div class="column full_size"  style="background:#e9d8ff">
 
<center>
 
<h2><button onclick="toggle1();">Species</button></h2>
 
<div id="clear2" style="display: none;">
 
<h5>Species okay. </h5>
 
&nbsp;
 
&nbsp;
 
</div>
 
</center>
 
</div>
 
 
<div id="footer">
 
<div class="container">
 
&nbsp;
 
&nbsp;
 
 
</div>
 
</div>
 
</body>
 
 
</html>
 
{{:Team:UNOTT/Template/Footer}}
 
!-->
 

Latest revision as of 02:29, 2 November 2017

</DIV>



Modelling    

 

 

Overview

When developing Key. coli, we found it was important to mathematically model possible situations in order to investigate the effects of different situations that we might encounter throughout different stages of development as well as during implementation.

A major problem the project faced is that the comparison process of the fluorescence proteins wouldn't be possible to be investigated with all combinations as it would take too long.

To answer this problem, the team attempted to model the fluorescence spectra over time expressed by each different protein. First, the type of gene expression was identified and then, the model was refined to take into account gene inhibition (whether the gene is expressed or not) and finally, applied over time to see how much expression would occur at a certain time period. The team used mathematical modelling such as Ordinary Differential Equations because they were easy to convert into programming in order to build components for the simulation.

This information was used by the wet lab to assist them by informing them in what to expect. This was done through the use of programming to create visual graphs and simulations, as well as development of tools to allow for comparison between fluorescence levels without needing to actually create more synthetic organisms. One advantage of this was it allowed for data to be easily read and understood by the team, rather than reading a wall of numbers. Another advantage is that this is far quicker than creating these results in the lab.

One limitation of models the team found out that they were too high level to accurately predict and represent all the processes that would be undertaken during the random constructions of the fluorescent proteins. This is an issue because this means the models weren't perfect to describe the real life, which however, suggests, they could undergo more refining and improving.

Software was developed to compare the fluorescence levels of the key colony with the mother colony to check if there was a high enough degree of similarity. The mother colony is defined as the colony of bacteria that is securely kept within the facility and whose fluorescence acts as a verification for the key colony, which is defined as the bacteria which is taken from the mother colony and given to a person who own's a Key.Coli container.

As a side project, the team investigated into whether our method is random and unique by investigating how many combinations we could make and whether we could accurately predict which combination will occur.

Modelling Aims

The first aim is to assist the processes within the wet lab by informing them of what spectra they can expect through the use of simulations. This would be especially useful when predicting the required fluorescence

The second is to test our biological systems with conditions that might not be possible to replicate in a lab environment. This allows us to future proof our methods as well as identify any vulnerabilities further down the line as well as save time and money on testing these conditions, if we were to.

In order to achieve these aims, we decided on an end goal of writing a Simulation for measuring Fluorescence Intensity when given parameters such as protein concentrations and wavelengths of lasers.



Find out more about our modeling

The source code for these models can be accessed from our GitHub page

Software Aims

The main objective of software was to check between fluorescence levels during implementation of Key.Coli between the mother colony and the Key.Coli capsules.

In order to achieve this objective, the team decided to investigate into image comparison and raw data comparison with data from the fluorescence reader. These were programmed using data from the models and a threshold value was set using data from the wet lab to ensure not just any file being compared would get verified.

A strong emphasis was placed on effectiveness of the software and efficiency; we wanted the software to run on low end hardware but still be useful without compromises.



Find out more about our software

Our software can be downloaded from our GitHub page

Parameters

Inputs and Outputs

Parameter Unit
Protein Concentration ug / mol
mRNA Concentration ug / mol
Fluorescence RFU (Relative Fluorescence Unit)
Time Hours / Hrs

Rates of change

Parameter Unit
Protein Degradation Nanograms per microlitre per minute
mRNA Degradation Nanograms per microlitre per minute
Translation Number of protein molecules produced per mRNA molecule, per unit of time
Transcription Number of mRNA molecules produced per gene, per unit of time.