"
Team:Berkeley
From 2012.igem.org
| Line 4: | Line 4: | ||
<head> | <head> | ||
<title>Berkeley iGEM 2011 </title> | <title>Berkeley iGEM 2011 </title> | ||
| - | <meta property="og:title" content="Berkeley iGEM | + | <meta property="og:title" content="Berkeley iGEM 2012"/> |
<meta property="og:type" content="university"/> | <meta property="og:type" content="university"/> | ||
<meta property="og:description" | <meta property="og:description" | ||
content="Berkeley's 2011 iGEM team wiki."/> | content="Berkeley's 2011 iGEM team wiki."/> | ||
| - | <meta name="description" content="Berkeley iGEM | + | <meta name="description" content="Berkeley iGEM 2012" /> |
| - | <meta name="keywords" content="igem, berkleley, | + | <meta name="keywords" content="igem, berkleley, 2012" /> |
| - | <link rel="stylesheet" href="https:// | + | <link rel="stylesheet" href="https://2012.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> | <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script> | ||
| Line 33: | Line 33: | ||
<div class="col12" > | <div class="col12" > | ||
<ul class="topnav"> | <ul class="topnav"> | ||
| - | <li><a href="https:// | + | <li><a href="https://2012.igem.org/Team:Berkeley">Home </a></li> |
<li> | <li> | ||
| - | <a href="https:// | + | <a href="https://2012.igem.org/Team:Berkeley/Project">Project</a> |
</li> | </li> | ||
<li> | <li> | ||
| - | <a href="https:// | + | <a href="https://2012.igem.org/Team:Berkeley/Parts">Parts</a> |
</li> | </li> | ||
| - | <li><a href="https:// | + | <li><a href="https://2012.igem.org/Team:Berkeley/Safety">Safety</a></li> |
| - | <li><a href="https:// | + | <li><a href="https://2012.igem.org/Team:Berkeley/Team">Team</a></li> |
| - | <li><a href="https:// | + | <li><a href="https://2012.igem.org/Team:Berkeley/Judging">Judging</a></li> |
<li><a href="https://2011.igem.org/Team:Berkeley/Notebooks">Notebooks</a></li> | <li><a href="https://2011.igem.org/Team:Berkeley/Notebooks">Notebooks</a></li> | ||
</ul> | </ul> | ||
| Line 58: | Line 58: | ||
<div class="col6" align = "justify" > | <div class="col6" align = "justify" > | ||
<img src="https://static.igem.org/mediawiki/2011/1/12/ProjectSummaryHeader.jpg" width="480"> | <img src="https://static.igem.org/mediawiki/2011/1/12/ProjectSummaryHeader.jpg" width="480"> | ||
| - | <p> | + | <p> |
| - | + | Many applications in synthetic biology demand precise control over subcellular localization, cell morphology, motility, and other such phenotypes that are only observable via microscopy. At present, engineering these properties is challenging due in large part to the inherent throughput limitation imposed by microscopy. We have developed a strategy that enables high-throughput library screening with microscopy by coupling a unique fluorescence signature with each genotype present in a library. These MiCodes (microscopy barcodes) are generated by targeting combinations of fluorophores to several organelles within yeast, and they eliminate the need to isolate and observe clonal populations separately. MiCodes can potentially scale to library sizes of 10^6 or more, and their analysis can be largely automated using existing image processing software. As a proof of principle, we applied MiCodes to the problem of finding unique pairs of protein-protein interaction parts. | |
| - | + | </p> | |
| - | + | ||
| - | + | ||
</div> | </div> | ||
Revision as of 04:03, 26 September 2012
Many applications in synthetic biology demand precise control over subcellular localization, cell morphology, motility, and other such phenotypes that are only observable via microscopy. At present, engineering these properties is challenging due in large part to the inherent throughput limitation imposed by microscopy. We have developed a strategy that enables high-throughput library screening with microscopy by coupling a unique fluorescence signature with each genotype present in a library. These MiCodes (microscopy barcodes) are generated by targeting combinations of fluorophores to several organelles within yeast, and they eliminate the need to isolate and observe clonal populations separately. MiCodes can potentially scale to library sizes of 10^6 or more, and their analysis can be largely automated using existing image processing software. As a proof of principle, we applied MiCodes to the problem of finding unique pairs of protein-protein interaction parts.
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.
