Team:Berkeley

From 2012.igem.org

(Difference between revisions)
Line 1: Line 1:
-
{{:Team:Berkeley/Style}}
+
<html xmlns="http://www.w3.org/1999/xhtml"
 +
      xmlns:og="http://ogp.me/ns#"
 +
      xmlns:fb="https://www.facebook.com/2008/fbml">
 +
  <head>
 +
    <title>Berkeley iGEM 2011 </title>
 +
    <meta property="og:title" content="Berkeley iGEM 2011"/>
 +
    <meta property="og:type" content="university"/>
 +
    <meta property="og:description"
 +
          content="Berkeley's 2011 iGEM team wiki."/>
 +
<meta name="description" content="Berkeley iGEM 2011" />
 +
<meta name="keywords" content="igem, berkleley, 2011" />
 +
<link rel="stylesheet" href="https://2011.igem.org/Template:Team:Berkeley/nivocss?action=raw&ctype=text/css" type="text/css"/>
 +
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
-
<!--Navigation Bar-->
+
<script type="text/javascript" src="https://2011.igem.org/Template:Team:Berkeley/javascript/javanivoslider?action=raw&ctype=text/javascript"></script>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
  </head>
-
!align="center"|[[Team:Berkeley|Home]]
+
-
!align="center"|[[Team:Berkeley/Team|Team]]
+
-
!align="center"|[[Team:Berkeley/Project|Project]]
+
-
!align="center"|[[Team:Berkeley/Results|Results]]
+
-
!align="center"|[[Team:Berkeley/Notebook|Notebook]]
+
-
!align="center"|[[Team:Berkeley/Judging|Judging]]
+
-
!align="center"|[[Team:Berkeley/Safety|Safety]]
+
-
!align="center"|[[Team:Berkeley/Contributions|Contributions]]
+
-
|}
+
-
==MiCodes==
 
-
Current library screening methods typically discard all information regarding a majority of phenotypes that fail to meet a given threshold. Often, information from phenotypes beyond this threshold is of value—to demonstrate that the library has been fully explored, or to validate models correlating genotype and phenotype. To characterize the entire spectrum of phenotypes with a high-throughput method, we propose to apply microscopy to library screening. This requires a phenotype observable by microscopy connected to a construct genotype. MiCodes (microscopy barcodes) provide a unique phenotypic tag for each library member, which we generated by targeting combinations of fluorophores to several organelles within yeast. MiCodes can potentially scale to library sizes of 1,000,000 or more, using an automatable method to measure many cells in parallel. MiCodes act as a consistent, high throughput technology that connects genetic information to a visible phenotype for each member of the library.
+
 
 +
 
 +
 
 +
 
 +
<div id="top-section3"><center><img src="https://static.igem.org/mediawiki/2011/4/48/NavigationBar_Berkeley.jpg" alt="header" border="0"  usemap="#igemmap" width="1000"></center></div>
 +
 
 +
<map name="igemmap">
 +
  <area  shape="circle" coords="480,40,40" alt="Mercury" href="https://2011.igem.org" onfocus="this.blur()" />
 +
</map>
 +
 
 +
 
 +
<div class="layout-1000">
 +
<div class="row">
 +
<div class="col12" >
 +
<ul class="topnav">
 +
    <li><a href="https://2011.igem.org/Team:Berkeley">Home  </a></li>
 +
    <li>
 +
        <a href="https://2011.igem.org/Team:Berkeley/Project">Project</a>
 +
    </li>
 +
    <li>
 +
        <a href="https://2011.igem.org/Team:Berkeley/Parts">Parts</a>
 +
    </li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Safety">Safety</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Team">Team</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Judging">Judging</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Notebooks">Notebooks</a></li>
 +
</ul>
 +
<div> <div class ="row-end"> </div>
 +
</div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer2"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
 
 +
<div class="row">
 +
<div class="col6" align = "justify" >
 +
<img src="https://static.igem.org/mediawiki/2011/1/12/ProjectSummaryHeader.jpg" width="480">
 +
<p>Biosensors have widespread applications ranging from diagnostics to environmental monitoring. Vibrio cholerae's ToxR system can be used as a component in biological sensing devices. ToxS causes ToxR homodimerization, activating transcription of the ctx promoter. By replacing the periplasmic domain of ToxR with existing or engineered ligand-dependent homodimers, we hope to link ToxR dimerization (and gene expression) to the presence of specific ligands. Initially, ToxR constructs proved toxic to E. coli. We built a stress-regulated transcription system that drives relatively high expression of toxic proteins. This allowed us to further engineer ToxR chimeras. We fused an estrogen-dependent dimer with ToxR hoping to create an estrogen biosensor. We observed a range of constitutive phenotypes and plan more experiments to engineer a dose-dependent transcriptional response to estrogen. By fusing existing or engineered ligand dependent homodimers to ToxR, this modular system can be used to build new biosensors. </p>
 +
</div>
 +
<div class="col6">
 +
<object width="480" height="300"><param name="movie" value="http://www.youtube.com/v/wuAlhXGKABA?"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/wuAlhXGKABA?" type="application/x-shockwave-flash" width="480" height="300" allowscriptaccess="always" allowfullscreen="true"></embed></object> </div>
 +
<div class ="row-end"> </div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
<div class="row">
 +
 
 +
<div class="col3-2"style="background-color:#101a4d;"><a href="https://2011.igem.org/Team:Berkeley/Project#ToxR"> <img src="https://static.igem.org/mediawiki/igem.org/1/10/Subtitlepic1.jpg"
 +
onmouseover="this.src='https://static.igem.org/mediawiki/igem.org/e/ef/Subtitlepic1hover.jpg'"
 +
onmouseout="this.src='https://static.igem.org/mediawiki/igem.org/1/10/Subtitlepic1.jpg'" width="230"></a>
 +
<p style="text-align:center; color:#CECECE;"> A protein with great potential as a general biosensor system.</p> </div>
 +
 
 +
<div class="col3-2"style="background-color:#185f73;"><a href="https://2011.igem.org/Team:Berkeley/Project#ToxRChimera"><img src="https://static.igem.org/mediawiki/2011/b/bb/Subtitlepic3header.jpg"
 +
onmouseover="this.src='https://static.igem.org/mediawiki/2011/2/26/Subtitlepic3headerhover.jpg'"
 +
onmouseout="this.src='https://static.igem.org/mediawiki/2011/b/bb/Subtitlepic3header.jpg'" width="230"> </a>
 +
<p style="text-align:center; color:#CECECE;"> Chimeric proteins that drive translation off of the Pctx promoter.</p></div>
 +
 
 +
<div class="col3-2" style="background-color:#303285"><a href="https://2011.igem.org/Team:Berkeley/Project#StressPromoters"><img src="https://static.igem.org/mediawiki/2011/2/2b/Subtitlepic2header.jpg"
 +
onmouseover="this.src='https://static.igem.org/mediawiki/2011/3/32/Subtitlepic2headerhover.jpg'"
 +
onmouseout="this.src='https://static.igem.org/mediawiki/2011/2/2b/Subtitlepic2header.jpg'" width="230"></a>
 +
<p style="text-align:center; color:#CECECE;"> Our method for expressing interesting (but toxic) proteins.</p> </div>
 +
 
 +
<div class="col3-2"style="background-color:#499394"><a href="https://2011.igem.org/Team:Berkeley/Project#EstrogenBiosensor"><img src="https://static.igem.org/mediawiki/2011/c/c8/Subtitlepic4.jpg"
 +
onmouseover="this.src='https://static.igem.org/mediawiki/2011/1/12/Subtitlepic4hover.jpg'"
 +
onmouseout="this.src='https://static.igem.org/mediawiki/2011/c/c8/Subtitlepic4.jpg'" width="230"></a>
 +
<p style="text-align:center; color:#CECECE;"> Bacteria engineered to detect the presence of estrogen. <br></p></div>
 +
<div class ="row-end"> </div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer"></div>
 +
<div class="row-end"> </div>
 +
</div>
<br>
<br>
 +
<div class="row">
-
Please visit our [[Team:Berkeley/Project|Project page]] for more details!
+
<div class="col4" align = "justify">
 +
<img src="https://static.igem.org/mediawiki/2011/b/bd/Aboutus.jpg">
 +
<p>We are Team Berkeley, a cohesive unit of 7 undergraduates and 3 advisers. Earlier this year we planned a complex and risky project, given the short amount of time iGEM made available. We quickly learned each others strengths and weaknesses and developed standard systems of organizational management in order to synchronize our efforts for the many parallel tasks at hand. We created protocols, shared them with one another, and worked together on troubleshooting. Using google docs to keep up with the status of cloning projects, the results of assays, material logistics, or the final steps required to complete a project ensured that through the months of hard work, we fine-tuned our ability to work together. As a team, we have learned firsthand how the synthetic biology community relies on the goal-oriented cooperation of skilled individuals from very different backgrounds and with very different skill sets. Some of us have strong engineering backgrounds while others of us have strong biology backgrounds, but we all share a desire to build synthetic biological systems that solve human problems. We are proud of the project that we have created which we will present at the Jamboree together in October.</p>
 +
</div>
-
<!--- The Mission, Experiments --->
+
<div class = "col14">
 +
<p>
 +
</p>
 +
</div>
 +
 
 +
<div class="col8-4">
 +
 
 +
        <div class="slider-wrapper theme-default">
 +
            <div class="ribbon"></div>
 +
            <div id="slider" class="nivoSlider">
 +
                <img src="https://static.igem.org/mediawiki/2011/c/ce/Slideshow1.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/e/ea/Slideshow2.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/d/db/Slideshow3.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/d/db/Slideshow4.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/d/d0/Slideshow5.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/2/2c/Slideshow6.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/f/f5/Slideshow7.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/b/b5/Slideshow14.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/7/71/Slideshow15.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/1/1a/Slideshow14.JPG" />
 +
                <img src="https://static.igem.org/mediawiki/2011/b/b2/Slideshow10.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/2/28/Slideshow12.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/9/9b/Slideshow13.jpg" />
 +
                <img src="https://static.igem.org/mediawiki/2011/9/94/Slideshow11.jpg" />
 +
            </div>
 +
    </div>
 +
 
 +
    <script type="text/javascript">
 +
  $(window).load(function() {
 +
        $('#slider').nivoSlider();
 +
    });
 +
    </script>
 +
<br>
 +
 
 +
<div id="fb-root"></div>
 +
<script>(function(d, s, id) {
 +
  var js, fjs = d.getElementsByTagName(s)[0];
 +
  if (d.getElementById(id)) {return;}
 +
  js = d.createElement(s); js.id = id;
 +
  js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";
 +
  fjs.parentNode.insertBefore(js, fjs);
 +
}(document, 'script', 'facebook-jssdk'));</script>
 +
 
 +
<div class="fb-like" data-href="https://2011.igem.org/Team:Berkeley" data-send="true" data-width="600" data-show-faces="false" data-font="lucida grande"></div>
-
<html>
 
</div>
</div>
 +
<div class="row-end"></div>
 +
</div>
 +
 +
<div class="row">
 +
<div class="col12" id="spacer"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 +
 +
<div class = "row">
 +
<div class="col12-3" style="background-color:#499394">
 +
<p style="text-align:left; color:#CECECE; font-size:13px; font-weight:bold; padding:3px"> The UC Berkeley iGEM team would like to thank Autodesk and Agilent for their financial support and Synberc, for their administrative support. </p>
 +
 +
</div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 +
 +
<div class="row">
 +
<div class="col12" id="spacer"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 +
<div class = "row">
 +
<div class="col12-3" >
 +
<img src="https://static.igem.org/mediawiki/2011/f/f1/Agilentlogo.png" width="300" >
 +
<img src="https://static.igem.org/mediawiki/2011/b/bc/SynBERC_logo_poster.png" width="300" >
 +
<img src="https://static.igem.org/mediawiki/2011/e/e8/Autodesk_logo_blk_l.jpg"width="300">
 +
<div class="row-end"></div>
 +
</div>
 +
</div>
</div>
</html>
</html>
 +
 +
 +
{{Team:Berkeley/header}}
 +
{{Team:Berkeley/css}}
 +
{{Team:Berkeley/navigation}}

Revision as of 03:56, 26 September 2012

Berkeley iGEM 2011

header
Mercury

Biosensors have widespread applications ranging from diagnostics to environmental monitoring. Vibrio cholerae's ToxR system can be used as a component in biological sensing devices. ToxS causes ToxR homodimerization, activating transcription of the ctx promoter. By replacing the periplasmic domain of ToxR with existing or engineered ligand-dependent homodimers, we hope to link ToxR dimerization (and gene expression) to the presence of specific ligands. Initially, ToxR constructs proved toxic to E. coli. We built a stress-regulated transcription system that drives relatively high expression of toxic proteins. This allowed us to further engineer ToxR chimeras. We fused an estrogen-dependent dimer with ToxR hoping to create an estrogen biosensor. We observed a range of constitutive phenotypes and plan more experiments to engineer a dose-dependent transcriptional response to estrogen. By fusing existing or engineered ligand dependent homodimers to ToxR, this modular system can be used to build new biosensors.

A protein with great potential as a general biosensor system.

Chimeric proteins that drive translation off of the Pctx promoter.

Our method for expressing interesting (but toxic) proteins.

Bacteria engineered to detect the presence of estrogen.


We are Team Berkeley, a cohesive unit of 7 undergraduates and 3 advisers. Earlier this year we planned a complex and risky project, given the short amount of time iGEM made available. We quickly learned each others strengths and weaknesses and developed standard systems of organizational management in order to synchronize our efforts for the many parallel tasks at hand. We created protocols, shared them with one another, and worked together on troubleshooting. Using google docs to keep up with the status of cloning projects, the results of assays, material logistics, or the final steps required to complete a project ensured that through the months of hard work, we fine-tuned our ability to work together. As a team, we have learned firsthand how the synthetic biology community relies on the goal-oriented cooperation of skilled individuals from very different backgrounds and with very different skill sets. Some of us have strong engineering backgrounds while others of us have strong biology backgrounds, but we all share a desire to build synthetic biological systems that solve human problems. We are proud of the project that we have created which we will present at the Jamboree together in October.


The UC Berkeley iGEM team would like to thank Autodesk and Agilent for their financial support and Synberc, for their administrative support.


header
iGEM Berkeley iGEMBerkeley iGEMBerkeley

Retrieved from "http://2012.igem.org/Team:Berkeley"