Team:TU Darmstadt/solution

From 2013.igem.org

(Difference between revisions)
 
(10 intermediate revisions not shown)
Line 2: Line 2:
<style type="text/css">
<style type="text/css">
-
body
+
body  
{
{
margin:0;  
margin:0;  
Line 15: Line 15:
{
{
   background-color: white;
   background-color: white;
-
   background-image: url("/wiki/images/7/70/Hintergrund3.jpg");
+
   background-image: url("/wiki/images/5/5c/Hintergrund_Grün(ohne_Header%2C_Logo_und_Schlagschatten).jpg");
   background-attachment: scroll;
   background-attachment: scroll;
   background-position: 50% 0;
   background-position: 50% 0;
Line 26: Line 26:
{
{
     background: white;
     background: white;
-
     background-image: url('/wiki/images/2/2f/Header_(mit_Logo).jpg');
+
     background-image: url("/wiki/images/2/2f/Header_%28mit_Logo%29.jpg");
     margin: 0 auto;
     margin: 0 auto;
     height:250px ;
     height:250px ;
Line 35: Line 35:
     background-repeat: no-repeat;
     background-repeat: no-repeat;
     background-size: 100% 100% ;
     background-size: 100% 100% ;
-
     border-style: none;
+
     border-style: none;;}
-
}
+
-
 
+
#p-logo { display:none;}
#p-logo { display:none;}
.firstHeading {display:none;}
.firstHeading {display:none;}
Line 46: Line 44:
{
{
position: absolute;
position: absolute;
-
top: 240px;  
+
top: 150px;  
-
left: 200px;
+
left: 30px;
}
}
#mm_icon2
#mm_icon2
{
{
-
position: relative;
+
position: absolute;
-
top: 170px;  
+
top: 150px;  
left: 350px;
left: 350px;
}
}
Line 67: Line 65:
{
{
position: absolute;
position: absolute;
-
top: 260px;  
+
top: 150px;  
-
left: 230px;
+
left: 30px;
background:white;
background:white;
filter:alpha(opacity=83); opacity:0.83;
filter:alpha(opacity=83); opacity:0.83;
Line 80: Line 78:
{
{
position: absolute;
position: absolute;
-
top: 670px;  
+
top: 150px;  
left: 350px;
left: 350px;
background:white;
background:white;
Line 94: Line 92:
position: absolute;
position: absolute;
top: 150px;  
top: 150px;  
-
left: 700px;
+
left: 670px;
background:white;
background:white;
filter:alpha(opacity=83); opacity:0.83;
filter:alpha(opacity=83); opacity:0.83;
Line 102: Line 100:
border-radius:15px;
border-radius:15px;
}
}
-
 
#taskbar
#taskbar
Line 108: Line 105:
position:absolute;
position:absolute;
top:10px;
top:10px;
-
left:400px;
+
left:500px;
z-index: 5;
z-index: 5;
}
}
</style>
</style>
 +
 +
 +
<center>
 +
<!-- central main menu -->
 +
 +
<br>
 +
<br>
 +
<!-- Taskbar -->
<!-- Taskbar -->
Line 122: Line 127:
<img alt="Problem" src="/wiki/images/6/66/Darmstadt_green_Problem.jpg" width="100" height="30"></a>
<img alt="Problem" src="/wiki/images/6/66/Darmstadt_green_Problem.jpg" width="100" height="30"></a>
-
<a href="https://2013.igem.org/Team:TU_Darmstadt/solution">
 
-
<img alt="solution" src="/wiki/images/8/87/Darmstadt_green_Solution.jpg" width="100" height="30"></a>
 
<a href="https://2013.igem.org/Team:TU_Darmstadt/result">
<a href="https://2013.igem.org/Team:TU_Darmstadt/result">
Line 147: Line 150:
<img alt="team" src="/wiki/images/f/f3/Darmstadt_green_Labbook.jpg" width="90" height="30"></a>
<img alt="team" src="/wiki/images/f/f3/Darmstadt_green_Labbook.jpg" width="90" height="30"></a>
-
</div>
 
 +
</div>
-
<center>
 
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-
<h2><font size="6" color="#F0F8FF" face="Arial regular">The Strategy</font></h2>
 
-
<div id="all">
 
-
</div>
 
-
 
-
 
-
<font size="3" color="#F0F8FF" face="Arial regular">
 
-
<p text-aligne:left style="margin-left:50px; margin-right:50px">
 
-
 
-
To easily detect biological toxins we developed a handy device, everybody is able to operate reliably.
 
-
By altering the sensorium of E. coli with the help of synthetic biology, the bacteria would release a defined beacon when sensing mycotoxins. This treatment relies on a change of the so called Tar-receptors exterior binding site, to specifically react on mycotoxins (Derr, P. B., 2006: Changing the Specificity of a Bacterial Chemoreceptor. Journal of Molecular Biology , 923–932).
 
-
 
-
By also changing the interior impulse, an explicit beacon can be measured using the interaction of two fluorescent colorants (FRET).
 
-
Samples can be given into a self-constructed capsule containing the modified bacteria.
 
-
The light-signal inside the capsule is measured using a low-cost and open-source constructed FRET analysing system, as well developed by our team.
 
-
 
-
To illustrate the data in a clear and usable way, the construction of an Android smartphone app is the completion of our project. The application should identify the capsule and apply an online test protocol in order to visualise and compare the data with former tests and share it with customers, leaving the consumer with the opportunity to check different producers on clean manufacturing and production. Consequently, food can be checked on mycotoxins in a cheap and reliable way.
 
-
 
<br>
<br>
<br>
<br>
-
<h2><font size="6" color="#F0F8FF" face="Arial regular">Tar Receptor and CheB</font></h2>
 
-
 
-
 
-
<font size="3" color="#F0F8FF" face="Arial regular">
 
-
<p text-aligne:left style="margin-left:50px; margin-right:50px">
 
-
 
-
The Tar protein of Escherichia coli is a receptor protein, that forwards signals from outside into the cell. Its native task is to detect nutritive substances and to induce an active movement towards the source, a so called chemotaxis.
 
-
The receptor consists of two identical parts, called homologue monomers and is transmembrane.
 
-
The detection is taking place at the external part.
 
-
 
-
When detecting a substance, the receptor is switching form: a conformational change. This causes an alternation inside the cell; the receptor binds proteins transforming the signal into an inner cell cascade. Here, the first Protein binding to tar is called CheB.  These two build up the pairs needed for FRET signalling.
 
-
 
-
As the substance does not enter the cell, the Tar receptor is predestined for usage of toxin recognition.
 
-
Binding of the Tar receptor has to be absolutely specific to eliminate false positive signals. Therefore, in the external region of the receptor some amino acids have to be changed. A library, where the receptors are tested if the specification for a single toxin has improved, has to be created until a satisfactory version is found.
 
-
<br><br>
 
-
            <img alt="tar surface" src="/wiki/images/e/e6/Tar_surface_light1.png" width="50%" height="50%" align="right">
 
-
<img alt="tar binding" src="/wiki/images/7/70/Tar_top_light2.png" width="50%" height="50%" align="right">
 
-
 
<br>
<br>
<br>
<br>
-
 
-
<img alt="cheB" src="/wiki/images/3/38/CheB_surface_light2-withe.png" width="50%" height="50%" align="right">
 
-
<img alt="cheB activesite" src="/wiki/images/2/20/CheB_surface_light2_actvive.png" width="50%" height="50%" align="right">
 
-
 
<br>
<br>
-
&nbsp; &nbsp; &nbsp;
 
<br>
<br>
-
 
-
 
-
 
-
</front>
 
-
</p>
 
-
 
-
 
-
<h2><font size="6" color="#F0F8FF" face="Arial regular">FRET</font></h2>
 
-
 
-
<font size="3" color="#F0F8FF" face="Arial regular">
 
-
<p text-aligne:left style="margin-left:50px; margin-right:50px">
 
-
 
-
FRET (Förster or Flourescence energy transfer) is a technique to investigate protein interaction. The resulting data gives information about the chromophores connected to the proteins and the distance and angle to each other. The principle relies on a radiation free transition: An excited donor transfers energy to the acceptor by dipole dipole interactions. Here, the given distance between the two molecules needs to be between 0,5 nm and 10 nm for an efficient FRET.
 
-
Using the dipole dipole interactions changes in physical structure, bindings and separations can be investigated contemporarily.
 
-
 
<br>
<br>
-
<br><br>
 
<br>
<br>
-
 
+
<br>
-
</front>
+
<br>
-
</p>
+
<br>
-
 
+
<br>
-
</body>
+
<br>
-
 
+
<br>
-
</html>
+
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>

Latest revision as of 17:52, 4 October 2013


















































Retrieved from "http://2013.igem.org/Team:TU_Darmstadt/solution"