Difference between revisions of "Team:UNOTT/Model"

Line 136: Line 136:
 
  <p> The first aim is 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 </p>   
 
  <p> The first aim is 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 </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 </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 </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>
 
<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>
 
<br></br>
Line 148: Line 146:
 
   <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> 
+
 
&nbsp;
+
<p> <a href="https://2017.igem.org/Team:UNOTT/Software">Find out more about our software </a> </p>
<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 href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/tree/master/Software">Our software can be downloaded from our GitHub page</a> </p>
<p> <a href="https://2017.igem.org/Team:UNOTT/CultureModelling">Find out more about our software </a> </p>
+
<p> <a href="https://github.com/BurgundyIsAPublicEnemy/iGEMNotts2017/blob/master/LuciferA.c">This environment can be downloaded from our GitHub page</a> </p>
+
 
   </div>
 
   </div>
 
</div>
 
</div>

Revision as of 00:45, 27 October 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.

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.

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.

Modelling Aims

The first aim is 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

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

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.

Find out more about our software

Our software can be downloaded from our GitHub page

Parameters