Team:TU Darmstadt/safety
From 2013.igem.org
(34 intermediate revisions not shown) | |||
Line 15: | Line 15: | ||
{ | { | ||
background-color: white; | background-color: white; | ||
- | background-image: url("/wiki/images/ | + | 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( | + | background-image: url("/wiki/images/2/2f/Header_%28mit_Logo%29.jpg"); |
margin: 0 auto; | margin: 0 auto; | ||
height:250px ; | height:250px ; | ||
Line 36: | Line 36: | ||
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 105: | Line 104: | ||
{ | { | ||
position:absolute; | position:absolute; | ||
- | top: | + | top:10px; |
- | left: | + | left:500px; |
- | z-index: | + | z-index: 5; |
} | } | ||
Line 123: | Line 122: | ||
<div id="taskbar"> | <div id="taskbar"> | ||
<a href="https://2013.igem.org/Team:TU_Darmstadt"> | <a href="https://2013.igem.org/Team:TU_Darmstadt"> | ||
- | <img alt="Home_ausgewählt" src="/wiki/images/ | + | <img alt="Home_ausgewählt" src="/wiki/images/e/ef/Darmstadt_green_Home.jpg" width="70" height="30"></a> |
<a href="https://2013.igem.org/Team:TU_Darmstadt/problem"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/problem"> | ||
- | <img alt="Problem" src="/wiki/images/ | + | <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/result"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/result"> | ||
- | <img alt="result" src="/wiki/images/ | + | <img alt="result" src="/wiki/images/2/2c/Darmstadt_green_Result.jpg" width="80" height="30"></a> |
<a href="https://2013.igem.org/Team:TU_Darmstadt/safety"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/safety"> | ||
- | <img alt="safety" src="/wiki/images/ | + | <img alt="safety" src="/wiki/images/a/a4/05._Safety_(angewählt).jpg" width="90" height="30"></a> |
<a href="https://2013.igem.org/Team:TU_Darmstadt/team"> | <a href="https://2013.igem.org/Team:TU_Darmstadt/team"> | ||
- | <img alt="team" src="/wiki/images/ | + | <img alt="team" src="/wiki/images/a/a4/Darmstadt_green_Team.jpg" width="70" height="30"></a> |
+ | <br> | ||
+ | |||
+ | <a href="https://2013.igem.org/Team:TU_Darmstadt/strategy"> | ||
+ | <img alt="team" src="/wiki/images/a/a0/Darmstadt_green_Strategy.jpg" width="100" height="30"></a> | ||
+ | |||
+ | <a href="https://2013.igem.org/Team:TU_Darmstadt/humanpractice"> | ||
+ | <img alt="team" src="/wiki/images/4/4f/Darmstadt_green_Human_Practice.jpg" width="150" height="30"></a> | ||
+ | |||
+ | <a href="https://2013.igem.org/Team:TU_Darmstadt/modelling"> | ||
+ | <img alt="team" src="/wiki/images/0/06/Darmstadt_green_Modelling.jpg" width="110" height="30"></a> | ||
+ | |||
+ | <a href="https://2013.igem.org/Team:TU_Darmstadt/labbook"> | ||
+ | <img alt="team" src="/wiki/images/f/f3/Darmstadt_green_Labbook.jpg" width="90" height="30"></a> | ||
+ | |||
+ | |||
+ | |||
+ | |||
</div> | </div> | ||
+ | <br><br> <br> <br> | ||
<h2><font size="6" color="#F0F8FF" face="Arial regular">Why biosafety?</font></h2> | <h2><font size="6" color="#F0F8FF" face="Arial regular">Why biosafety?</font></h2> | ||
Line 150: | Line 165: | ||
<img alt="safety" src="/wiki/images/8/80/Biosafteyy.png" width="150" height="131" align="right"> | <img alt="safety" src="/wiki/images/8/80/Biosafteyy.png" width="150" height="131" align="right"> | ||
- | One key issue for the implementation Synthetic Biology in everyday life is safety. Since genetically modified organisms (GMOs) can interact with natural organisms | + | One key issue for the implementation of Synthetic Biology in everyday life is safety. Since genetically modified organisms (GMOs) can interact with natural organisms as well as evolve and adapt to their environment, completely new approaches are needed to address scientific and public safety concerns. Safety measurements have to work independently from the operator’s skills or background knowledge. |
</p></font> | </p></font> | ||
Line 163: | Line 178: | ||
<p text-aligne:left style="margin-left:50px; margin-right:50px"> | <p text-aligne:left style="margin-left:50px; margin-right:50px"> | ||
- | Many | + | Many kill switches include promoters which are induced by the presence of a signal like IPTG or heat. Since these kill switches can malfunction due to human failure, we chose a different approach that fits perfectly to our device: A kill switch that is induced by blue light. |
- | <i>Ohlendorf et al.</i> constructed the pDawn vector which contains the blue light sensitive histidine kinase YF1. In the presence of blue light YF1 | + | <i>Ohlendorf et al.</i><sup><span style="color:blue"> <font color="#F0F8FF" face="Arial regular">[1]</font></span></sup> constructed the pDawn vector which contains the blue light sensitive histidine kinase YF1. In the presence of blue light YF1 does not phosphorylate its cognate response regulator FixJ which then does not drive gene expression from the FixK2 promoter. Downstream of the promoter the λ phage repressor cI is located which represses the strong λ phage promotor pR. |
<br> | <br> | ||
- | Downstream of this promotor lies our toxin of choice, PezT, which was characterized by <i>Mutschler et al.</i> to be a very strong inhibitor of cell growth. PezT is a kinase that phosphorylates uridine diphosphate-<i>N</i>-acetylglucosamine (UNAG) and part of | + | |
+ | <iframe width="320" height="240" src="//www.youtube.com/embed/9sIxNTcWG3o" frameborder="0" allowfullscreen></iframe> | ||
+ | |||
+ | |||
+ | <img alt="safety" src="/wiki/images/2/27/Liks_schema.png" width="60%" height="60%" align="right"> | ||
+ | |||
+ | <br> | ||
+ | Downstream of this promotor lies our toxin of choice, PezT, which was characterized by <i>Mutschler et al.</i><sup><span style="color:blue"> <font color="#F0F8FF" face="Arial regular">[2]</font></span></sup> to be a very strong inhibitor of cell growth. PezT is a kinase that phosphorylates uridine diphosphate-<i>N</i>-acetylglucosamine (UNAG) and is part of a pneumococcal toxin-antitoxin system which induces cell death under stress conditions. UNAG is an essential precursor in the peptidoglycan biosynthesis and phosphorylation of UNAG inhibits in <i>E. coli</i> cell wall synthesis in such an effective manner that studies failed in the past only because of its toxicity. | ||
</p></font> | </p></font> | ||
</body> | </body> | ||
Line 178: | Line 200: | ||
<p text-aligne:left style="margin-left:50px; margin-right:50px"> | <p text-aligne:left style="margin-left:50px; margin-right:50px"> | ||
- | In the absence of blue light (or day light respectively) the PezT toxin is not expressed and the bacteria are alive. After the FRET measurement or spilling the expression of PezT is induced by the | + | In the absence of blue light (or day light respectively) the PezT toxin is not expressed and the bacteria are alive. After the FRET measurement or a spilling the expression of PezT is induced by the blue light used in the FRET measurement or day light. Even if the spill remains unbeknownst to the operator, the expression of the toxin will be induced by day light and the leaking bacteria will contain themselves. Used capsules can be disposed without previous autoclaving. All these safety measurements raise our device’s applicability and operability in everyday life so that our device can be handled theoretically by untrained workers without any increase of risk. |
</p></font> | </p></font> | ||
</body> | </body> | ||
+ | |||
+ | |||
+ | <br><br><br> | ||
+ | <a href="https://2013.igem.org/Team:TU_Darmstadt/safety/Labjournal"> | ||
+ | <img alt="Labbook" border="5" width="57,5" height="50" src="/wiki/images/8/81/Book2.gif"> | ||
+ | <font size="6" color="#F0F8FF" face="Arial regular">Visit our lab book</font><br /> | ||
+ | </a> | ||
+ | |||
+ | |||
+ | </center> | ||
+ | <br><br><br> | ||
+ | |||
+ | <center> | ||
+ | <h2><font size="6" color="#F0F8FF" face="Arial regular">Safety form</font></h2> | ||
+ | |||
+ | </center> | ||
+ | |||
+ | |||
+ | <font size="3" color="#F0F8FF" face="Arial regular"> | ||
+ | <p text-aligne:left style="margin-left:50px; margin-right:50px"> | ||
+ | <br> | ||
+ | <a href="https://static.igem.org/mediawiki/2013/9/9e/TU_Darmstadt_IGEM_2013_Basic_Safety_Form.pdf"> | ||
+ | <font size="3" color="#F0F8FF" face="Arial regular"><b>Safety form were approved on October 3, 2013 by Evan Appleton.<b></font> | ||
+ | </a> | ||
+ | <br> | ||
+ | <font size="3" color="#F0F8FF" face="Arial regular"> | ||
+ | <p text-aligne:left style="margin-left:50px; margin-right:50px"> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
</body> | </body> | ||
+ | |||
+ | <center> | ||
<h2><font size="6" color="#F0F8FF" face="Arial regular">References</font></h2> | <h2><font size="6" color="#F0F8FF" face="Arial regular">References</font></h2> | ||
<body> | <body> | ||
<body> | <body> | ||
+ | |||
<font size="3" color="#F0F8FF" face="Arial regular"> | <font size="3" color="#F0F8FF" face="Arial regular"> | ||
Line 203: | Line 263: | ||
</body> | </body> | ||
+ | |||
</html> | </html> |
Latest revision as of 03:48, 5 October 2013
Why biosafety?
One key issue for the implementation of Synthetic Biology in everyday life is safety. Since genetically modified organisms (GMOs) can interact with natural organisms as well as evolve and adapt to their environment, completely new approaches are needed to address scientific and public safety concerns. Safety measurements have to work independently from the operator’s skills or background knowledge.
A light-induced kill switch
Many kill switches include promoters which are induced by the presence of a signal like IPTG or heat. Since these kill switches can malfunction due to human failure, we chose a different approach that fits perfectly to our device: A kill switch that is induced by blue light.
Ohlendorf et al. [1] constructed the pDawn vector which contains the blue light sensitive histidine kinase YF1. In the presence of blue light YF1 does not phosphorylate its cognate response regulator FixJ which then does not drive gene expression from the FixK2 promoter. Downstream of the promoter the λ phage repressor cI is located which represses the strong λ phage promotor pR.
Downstream of this promotor lies our toxin of choice, PezT, which was characterized by Mutschler et al. [2] to be a very strong inhibitor of cell growth. PezT is a kinase that phosphorylates uridine diphosphate-N-acetylglucosamine (UNAG) and is part of a pneumococcal toxin-antitoxin system which induces cell death under stress conditions. UNAG is an essential precursor in the peptidoglycan biosynthesis and phosphorylation of UNAG inhibits in E. coli cell wall synthesis in such an effective manner that studies failed in the past only because of its toxicity.
What happens after a spill?
In the absence of blue light (or day light respectively) the PezT toxin is not expressed and the bacteria are alive. After the FRET measurement or a spilling the expression of PezT is induced by the blue light used in the FRET measurement or day light. Even if the spill remains unbeknownst to the operator, the expression of the toxin will be induced by day light and the leaking bacteria will contain themselves. Used capsules can be disposed without previous autoclaving. All these safety measurements raise our device’s applicability and operability in everyday life so that our device can be handled theoretically by untrained workers without any increase of risk.
Visit our lab book
Safety form
Safety form were approved on October 3, 2013 by Evan Appleton.