Difference between revisions of "Team:Manchester/Model"

Line 14: Line 14:
 
     border-radius: 10px;
 
     border-radius: 10px;
 
     padding: 20px;
 
     padding: 20px;
     width: 80%;
+
     width: 90%;
 +
 
 +
}
  
 +
img.model1{
 +
    width: 60%;
 +
    border-radius: 0px;
 +
    margin-top: 50px;
 
}
 
}
  
Line 67: Line 73:
  
 
<div class="90width">
 
<div class="90width">
<center>
+
 
  
  
Line 76: Line 82:
 
  </div>
 
  </div>
  
 +
<center>
 
   <div class="column full_size frontword">
 
   <div class="column full_size frontword">
 
     <p style="font-size:1.2em;">
 
     <p style="font-size:1.2em;">
Line 90: Line 97:
  
 
</div>
 
</div>
 +
 +
</center>
 +
  
  
<div class="width90">
 
  
<div class="column full_size" >
 
<div class="column onethird_size">
 
<a href="#ross"><img style="border-radius: 0px; width:60%" class="ross" id="ross" src="https://static.igem.org/mediawiki/2016/c/c1/T--Manchester--modelling1_pic.png" alt="Ross photo"></img></a>
 
<h3 class="teammatename" style="text-align:center"> </h3>
 
</div>
 
  
 +
<!--
 
<div class="column twothird_size">
 
<div class="column twothird_size">
 
<h5 class="modelling_info2">
 
<h5 class="modelling_info2">
Line 109: Line 114:
 
</h5>
 
</h5>
 
</div>
 
</div>
 +
-->
  
  
<div  class="column onethird_size" >
 
<a href="#nick"><img style="border-radius: 0px; width:60%"  class="nick" id="nick" src="https://static.igem.org/mediawiki/2016/a/a3/T--Manchester--modelling2_pic.png" alt="Nick photo"></img></a>
 
<h3 class="teammatename" style="text-align:center"> </h3>
 
</div>
 
  
 +
<!--
 
<div class="column twothird_size">
 
<div class="column twothird_size">
 
<h5 class="modelling_info1">
 
<h5 class="modelling_info1">
Line 123: Line 126:
 
</h5>
 
</h5>
 
</div>
 
</div>
 +
-->
  
  
  
 
<div  class="column onethird_size" >
 
<a href="#marc"><img style="border-radius: 0px; width:60%"  class="marc" id="marc" src="https://static.igem.org/mediawiki/2016/4/46/T--Manchester--modelling3_pic.png" alt="Marc photo"></img></a>
 
<h3 class="teammatename" style="text-align:center"> </h3>
 
</div>
 
  
  
 +
<!--
 
<div class="column twothird_size">
 
<div class="column twothird_size">
 
<h5 class="modelling_info3">
 
<h5 class="modelling_info3">
Line 139: Line 139:
 
</h5>
 
</h5>
 
</div>
 
</div>
 
+
-->
</div>
+
 
+
  
  
 +
<center>
 +
<div class="width90">
  
 +
<center>
 +
<div class=" onethird_size">
 +
<a href="#ross"><img class="model1" src="https://static.igem.org/mediawiki/2016/c/c1/T--Manchester--modelling1_pic.png" alt="What were we modelling?"></img></a>
 +
</div>
 +
</center>
  
<p style="border-bottom: 1px black solid ;font-size:25px;text-weight:bold;display:inline-block">What were we modelling?</p>
+
<div class="modelling_info1">
 
<p>
 
<p>
 
We focused on modelling the <a href="https://2016.igem.org/Team:Manchester/Description/mechanism1">cell free mechanism</a>, see the experimental section for details. The short version is the AlcoPatch relies on Alcohol, Alcohol Oxidase (AOx), Horseradish Peroxidase (HRP) and ABTS which are mixed together producing oxidised ABTS which is colourful. The ensemble modelling process will work for any model however and this was chosen as a simpler example to demonstrate the technique, focusing on the process rather than the system itself.  
 
We focused on modelling the <a href="https://2016.igem.org/Team:Manchester/Description/mechanism1">cell free mechanism</a>, see the experimental section for details. The short version is the AlcoPatch relies on Alcohol, Alcohol Oxidase (AOx), Horseradish Peroxidase (HRP) and ABTS which are mixed together producing oxidised ABTS which is colourful. The ensemble modelling process will work for any model however and this was chosen as a simpler example to demonstrate the technique, focusing on the process rather than the system itself.  
Line 173: Line 178:
 
<a href="https://2016.igem.org/Team:Manchester/Model/HorseRadishPeroxidaseReaction">Horseradish Peroxidase</a>
 
<a href="https://2016.igem.org/Team:Manchester/Model/HorseRadishPeroxidaseReaction">Horseradish Peroxidase</a>
 
</p>
 
</p>
 +
</div>
  
  
 +
<center>
 +
<div class="onethird_size" >
 +
<a href="#nick"><img class="model1" src="https://static.igem.org/mediawiki/2016/a/a3/T--Manchester--modelling2_pic.png" alt="What is esemble modelling?"></img></a>
 +
</div>
 +
</center>
  
 
+
<div class="modelling_info1">
<p style="border-bottom: 1px black solid ;font-size:25px;text-weight:bold;display:inline-block">What is Ensemble Modelling?</p>
+
 
<p>
 
<p>
PLACEHOLDER
+
Instead of running your model once with some specific parameters (for example rate constants.), you find all the possible parameters in literature and run your model for lots of combinations sampled in a clever way. By doing this you take take into account the uncertainty in the parameters. You will create probabilistic outputs allowing you to make rigorous conclusions.
 +
            <br /><br />
 +
Following through our flow diagram blueprint should make this concept clear.
 
</p>
 
</p>
 +
</div>
  
<p style="border-bottom: 1px black solid ;font-size:25px;text-weight:bold;display:inline-block">What did our model achieve?</p>
+
 
 +
<center>
 +
<div  class="onethird_size" >
 +
<a href="#marc"><img class="model1" src="https://static.igem.org/mediawiki/2016/4/46/T--Manchester--modelling3_pic.png" alt="What does our modelling achieve?"></img></a>
 +
 
 +
</div>
 +
</center>
 +
 
 +
<div class="modelling_info1">
 
<p>
 
<p>
 
Regardless how clever, interesting or unique a model is ultimately all that matters is the results at the end. We had 2 main aims for our outputs: improving our understanding of our system and answering key questions that arouse during the Human Practices.
 
Regardless how clever, interesting or unique a model is ultimately all that matters is the results at the end. We had 2 main aims for our outputs: improving our understanding of our system and answering key questions that arouse during the Human Practices.
Line 194: Line 215:
 
Further justification for why these were chosen is given on the respective pages.
 
Further justification for why these were chosen is given on the respective pages.
 
</p>
 
</p>
 +
</div>
  
  
  
 
+
<div class="modelling_info1">
 
+
 
<center>
 
<center>
 
<p>
 
<p>
Line 204: Line 225:
 
</p>
 
</p>
 
</center>
 
</center>
 +
</div>
  
 +
</div>
 
</center>
 
</center>
 
</div>
 
</div>

Revision as of 22:12, 16 October 2016

Manchester iGEM 2016
Modelling Banner

Welcome to our modelling section. We have used a novel ensemble modeling approach, to better aid the synergy between wetalb and dry lab teams. On this page you will find short answers to the questions; What is ensemble modelling? What did we model? what did our model achieve?

For navigating the wiki you need to know that the sections on results and human practice/lab integration can be accessed in the menu bar.

Part of what we hope to achieve with this ensemble methodology is a blueprint for other igem teams. As such each step in creating and using our model is laid out in the below diagram. Clicking on a specific step will take you to a page explaining the theory. Going deeper you can access a discussion of the code. There will be a link to the relevant parts of our github (a website storing our code) Use these codes as you wish.

Link to github homepage

-->
What were we modelling?

We focused on modelling the cell free mechanism, see the experimental section for details. The short version is the AlcoPatch relies on Alcohol, Alcohol Oxidase (AOx), Horseradish Peroxidase (HRP) and ABTS which are mixed together producing oxidised ABTS which is colourful. The ensemble modelling process will work for any model however and this was chosen as a simpler example to demonstrate the technique, focusing on the process rather than the system itself.

Due to time constraints the modelling was based on an analogous system of Glucose and Glucose Oxidase (GOx) rather than Alcohol and AOx, this was chosen as the reaction network is the same and it links in with the suggestions given at the Microbiology Society Conference in the human practices that the design need not be limited for alcohol but could be used by diabetics, etc if used to detect other molecules in sweat. While the equivalent analysis was done for glucose. Rerunning the analysis for alcohol would only require the change of some constants, so the analysis acts as a sufficient proof of concept and still shows the integration of human practices.

A schematic diagram of the final scheme is given below. For more information about the steps click on the blue enzyme boxes.

Reaction Network Diagram used in the modelling

Alternatively you can click on the enzyme name below:

Glucose Oxidase
Horseradish Peroxidase

What is esemble modelling?

Instead of running your model once with some specific parameters (for example rate constants.), you find all the possible parameters in literature and run your model for lots of combinations sampled in a clever way. By doing this you take take into account the uncertainty in the parameters. You will create probabilistic outputs allowing you to make rigorous conclusions.

Following through our flow diagram blueprint should make this concept clear.

What does our modelling achieve?

Regardless how clever, interesting or unique a model is ultimately all that matters is the results at the end. We had 2 main aims for our outputs: improving our understanding of our system and answering key questions that arouse during the Human Practices.

To improve our knowledge of the system we undertook 2 main analyses:
Improving our understanding the reaction network mechanism
Investigating the relationships between the parameters in our system

To answer the questions from the human practices there was 1 main analysis:
Costing the AlcoPatch


Further justification for why these were chosen is given on the respective pages.

We found great inspiration from our human practices and guidance working both ways to the experiments. Click here to see the detail.