"
Team:TU Darmstadt
From 2013.igem.org
| Line 51: | Line 51: | ||
position: absolute; | position: absolute; | ||
top: 150px; | top: 150px; | ||
| - | left: | + | left: 30px; |
z-index: 1; | z-index: 1; | ||
} | } | ||
| Line 59: | Line 59: | ||
position: absolute; | position: absolute; | ||
top: 150px; | top: 150px; | ||
| - | left: | + | left: 350px; |
z-index: 1; | z-index: 1; | ||
} | } | ||
| Line 67: | Line 67: | ||
position: absolute; | position: absolute; | ||
top: 150px; | top: 150px; | ||
| - | left: | + | left: 670px; |
z-index: 1; | z-index: 1; | ||
} | } | ||
| Line 86: | Line 86: | ||
<a href="https://2013.igem.org/Team:TU_Darmstadt/problem" > | <a href="https://2013.igem.org/Team:TU_Darmstadt/problem" > | ||
<div id="mm_icon1"> | <div id="mm_icon1"> | ||
| - | <img alt="Darmstadt_Grafik_1" src="/wiki/images/9/92/Darmstadt_Grafik_1..jpg" width=" | + | <img alt="Darmstadt_Grafik_1" src="/wiki/images/9/92/Darmstadt_Grafik_1..jpg" width="290" height="290"></br> |
| - | <font size=" | + | <font size="6" color="#F0F8FF">Problem</font> |
</div> | </div> | ||
</a> | </a> | ||
| Line 93: | Line 93: | ||
<a href="https://2013.igem.org/Team:TU_Darmstadt/solution"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/solution"> | ||
<div id="mm_icon2"> | <div id="mm_icon2"> | ||
| - | <img alt="Darmstadt_Grafik_4" src="/wiki/images/2/29/Darmstadt_Grafik_4..jpg" width=" | + | <img alt="Darmstadt_Grafik_4" src="/wiki/images/2/29/Darmstadt_Grafik_4..jpg" width="290" height="290"></br> |
| - | <font size=" | + | <font size="6" color="#F0F8FF">Solution</font> |
</div> | </div> | ||
</a> | </a> | ||
| Line 100: | Line 100: | ||
<a href="https://2013.igem.org/Team:TU_Darmstadt/result"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/result"> | ||
<div id="mm_icon3"> | <div id="mm_icon3"> | ||
| - | <img alt="Darmstadt_Grafik_6" src="/wiki/images/f/f3/Darmstadt_Grafik_6..jpg" width=" | + | <img alt="Darmstadt_Grafik_6" src="/wiki/images/f/f3/Darmstadt_Grafik_6..jpg" width="290" height="290"></br> |
| - | <font size=" | + | <font size="6" color="#F0F8FF">Result</font> |
</div> | </div> | ||
</a> | </a> | ||
| + | <br> | ||
| + | <br> | ||
| + | <br> | ||
| + | <br> | ||
| + | <br> | ||
| + | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
Revision as of 21:50, 6 September 2013
Problem
Solution
Result
Mycotoxins produced by mould fungus are present in our daily life and are harmful for humans as well as for animals. The danger of contamination of gain and other natural products has fatal consequences for the economy and the supply of whole nations. The mycotoxins which are permanently formed by the fungus, can be used as biomarkers to detect contamination. We want to develop a handy device which allows an easy and reliable detection of mycotoxins. To achieve this goal our team uses various methods from the fields of synthetic biology, electrical engineering and information processing. The detection system relies on E.coli with modified aspartate receptors (TAR) which interact with specific mycotoxins. If these are present in the reviewed sample they will bind to the receptor and induce a conformational change and thereby generates a measurable FRET-beacon by bringing two flourophores in close distance to each other. The modified E.coli will be embedded in interchangeable capsules. Together with a handheld-device they will guarantee that measurements can be done quickly, easy to operate and secure. The data will be transferred from the handheld system to an Android smartphone app which will be able to analyze, illustrate and store the test results for the user.
