Team:Berkeley/Project
From 2012.igem.org
(114 intermediate revisions not shown) | |||
Line 5: | Line 5: | ||
<html> | <html> | ||
+ | <div class="row"> | ||
+ | <div class="col12" id="spacer4"> </div> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/5/53/Project_header0.jpg" usemap="#projecthome" width="980" hspace = "10"> | ||
+ | </div> | ||
+ | <map name="projecthome"> | ||
+ | <area shape="rect" coords="0,0,360,90" alt="Mercury" href="https://2012.igem.org/Team:Berkeley/Project" onfocus="this.blur()" /> | ||
+ | </map> | ||
+ | </div> | ||
+ | <div class="row-end" ></div> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
<div class="row"> | <div class="row"> | ||
- | <div class="col12" > | + | <div class="col12" id="spacer"></div> |
- | < | + | <div class="col3-2"> |
- | + | <a href="https://2012.igem.org/Team:Berkeley/Project/Localization"> | |
- | + | <img src="https://static.igem.org/mediawiki/2012/e/e6/Project_nav1.jpg" | |
- | + | onmouseover="this.src='https://static.igem.org/mediawiki/2012/2/22/Project_nav1_hover.jpg'" | |
- | + | onmouseout="this.src='https://static.igem.org/mediawiki/2012/e/e6/Project_nav1.jpg'" width="230"></a> | |
- | + | </div> | |
- | + | ||
- | + | <div class="col3-2"> | |
- | + | <a href="https://2012.igem.org/Team:Berkeley/Project/Construction"> | |
- | + | <img src="https://static.igem.org/mediawiki/2012/4/4d/Project_nav2.jpg" | |
- | + | onmouseover="this.src='https://static.igem.org/mediawiki/2012/b/b8/Project_nav2_hover.jpg'" | |
- | + | onmouseout="this.src='https://static.igem.org/mediawiki/2012/4/4d/Project_nav2.jpg'" width="230"> </a> | |
- | </ | + | </div> |
- | + | ||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Automation"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/0/0b/Project_nav3.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/4/48/Project_nav3_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/0/0b/Project_nav3.jpg'" width="230"></a> | ||
+ | </div> | ||
+ | |||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Zippers"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/e/eb/Project_nav4.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/7/70/Project_nav4_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/e/eb/Project_nav4.jpg'" width="230"></a> | ||
+ | </div> | ||
+ | <div class ="row-end"> | ||
</div> | </div> | ||
</div> | </div> | ||
<div class="row"> | <div class="row"> | ||
- | <div class=" | + | <div class="col4" id="spacer"></div> |
<div class="row-end"> </div> | <div class="row-end"> </div> | ||
</div> | </div> | ||
<div class="row"> | <div class="row"> | ||
- | <div class=" | + | <div class="col1" align = "justify"> |
- | + | <a name="Project Abstract"></a> | |
+ | <img src="https://static.igem.org/mediawiki/2012/f/f5/Project0_subheader1.jpg" width="980"> | ||
</div> | </div> | ||
+ | <div class="row"> | ||
+ | <div class="col1" align="justify"> | ||
+ | <p> | ||
+ | <b>MiCodes:</b> Enabling library screens with microscopy by connecting genotypes to observable phenotypes | ||
+ | |||
+ | <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> | ||
+ | |||
+ | <div class="row-end"></div> | ||
<div class="row"> | <div class="row"> | ||
- | <div class="col12 | + | <div class="col12" id="spacer3"></div> |
- | <div class="row-end"> </div> | + | <div class="row-end"></div> |
</div> | </div> | ||
+ | <br> | ||
+ | |||
<div class="row"> | <div class="row"> | ||
- | + | <div class="col1" align = "justify"> | |
- | <a name=" | + | <a name="Why Microscopy"></a> |
- | + | <img src="https://static.igem.org/mediawiki/2012/4/4b/Project0_subheader2.jpg" width="980"> | |
</div> | </div> | ||
- | + | <div class="row"> | |
- | + | <div class="col1" align="justify"> | |
+ | <p> | ||
- | <div | + | Microscopy is a versatile and widely used imaging technology that allows us to observe various phenotypes that are not easily obtainable using other techniques. For example, microscopy can show us how cells move around in their environment, how they are shaped and form networks with other cells, and how proteins and other metabolites can be spatially localized within cells. Such phenomena require direct visualization, which best achieved through microscopy. </div> |
+ | </div> | ||
- | < | + | <div class="row-end"></div> |
+ | <div class="row"> | ||
+ | <div class="col12" id="spacer3"></div> | ||
+ | <div class="row-end"></div> | ||
+ | </div> | ||
+ | <br> | ||
- | |||
+ | |||
+ | |||
+ | <div class="row"> | ||
+ | <div class="col1" align = "justify"> | ||
+ | <a name="Why Libraries"></a> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/b/b9/Project0_subheader3.jpg" width="980"> | ||
+ | </div> | ||
+ | |||
+ | <div class="row"> | ||
+ | <div class="col1" align="justify"> | ||
<p> | <p> | ||
- | + | ||
+ | When we engineer systems in synthetic biology using cellular features such as motility, morphology and subcellular localization, we usually like to do so using libraries. | ||
+ | This is due to our current limitation of guessing which parameters to choose to optimize a given system. By using libraries, we can examine a large parameter space and find trends present in our system and even optimal parameters to use for our design. It is difficult to screen libraries of certain cellular phenomena in high throughput using current technologies, so we need to look at other possible methods. | ||
+ | |||
</p> | </p> | ||
- | == | + | </div> |
+ | </div> | ||
+ | |||
+ | <div class="row-end"></div> | ||
+ | <div class="row"> | ||
+ | <div class="col12" id="spacer3"></div> | ||
+ | <div class="row-end"></div> | ||
+ | </div> | ||
+ | <br> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <div class="row"> | ||
+ | <div class="col1" align = "justify"> | ||
+ | <a name="What Are MiCodes"></a> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/5/5e/Project0_subheader4.jpg" width="980"> | ||
+ | </div> | ||
+ | |||
+ | <div class="row"> | ||
+ | <div class="col1" align="justify"> | ||
<p> | <p> | ||
- | + | By localizing fluorescent proteins to specific organelles, each cell can be given a "microscopic barcode", or <b>MiCode</b>. Below you can see a single sample MiCode. Each member of a library will get a unique MiCode, distinguishing it from the rest of the library and tying the MiCode phenotype to a specific genotype. | |
+ | </div></div> | ||
+ | |||
+ | <div style="text-align: center;"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/e/e2/Sample_micode.png" usemap="#projecthome" width="800" hspace = "10"> | ||
+ | </div> | ||
+ | <p align="center">This example MiCode has four targeted organelles: nucleus-red, vacuolar membrane-red, plasma membrane-blue, actin-green. | ||
</p> | </p> | ||
+ | <br><br> | ||
- | = | + | <div class="row"> |
- | + | <div class="col1" align="justify"> | |
- | + | ||
- | < | + | To do this, we needed to decide which organelles to target and how to target them. We also had to optimize our choice of promoters so that one fluorescent protein signal was not too strong or too weak in comparison to the rest. |
- | + | ||
- | + | ||
- | + | ||
</p> | </p> | ||
+ | </div></div> | ||
+ | |||
+ | |||
+ | <div class="row-end"></div> | ||
+ | <div class="row"> | ||
+ | <div class="col12" id="spacer3"></div> | ||
+ | <div class="row-end"></div> | ||
+ | </div> | ||
+ | <br> | ||
+ | <br> | ||
+ | <br> | ||
+ | <br> | ||
+ | |||
+ | |||
+ | <hr align="center"> | ||
+ | |||
+ | <div class="row"> | ||
+ | <div class="col12" id="spacer"></div> | ||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Localization"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/e/e6/Project_nav1.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/2/22/Project_nav1_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/e/e6/Project_nav1.jpg'" width="230"></a> | ||
+ | </div> | ||
+ | |||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Construction"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/4/4d/Project_nav2.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/b/b8/Project_nav2_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/4/4d/Project_nav2.jpg'" width="230"> </a> | ||
+ | </div> | ||
+ | |||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Automation"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/0/0b/Project_nav3.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/4/48/Project_nav3_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/0/0b/Project_nav3.jpg'" width="230"></a> | ||
+ | </div> | ||
+ | |||
+ | <div class="col3-2"> | ||
+ | <a href="https://2012.igem.org/Team:Berkeley/Project/Zippers"> | ||
+ | <img src="https://static.igem.org/mediawiki/2012/e/eb/Project_nav4.jpg" | ||
+ | onmouseover="this.src='https://static.igem.org/mediawiki/2012/7/70/Project_nav4_hover.jpg'" | ||
+ | onmouseout="this.src='https://static.igem.org/mediawiki/2012/e/eb/Project_nav4.jpg'" width="230"></a> | ||
+ | </div> | ||
+ | <div class ="row-end"> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | </body> | ||
</html> | </html> |
Latest revision as of 23:10, 21 October 2012
MiCodes: Enabling library screens with microscopy by connecting genotypes to observable phenotypes
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.
Microscopy is a versatile and widely used imaging technology that allows us to observe various phenotypes that are not easily obtainable using other techniques. For example, microscopy can show us how cells move around in their environment, how they are shaped and form networks with other cells, and how proteins and other metabolites can be spatially localized within cells. Such phenomena require direct visualization, which best achieved through microscopy.
When we engineer systems in synthetic biology using cellular features such as motility, morphology and subcellular localization, we usually like to do so using libraries. This is due to our current limitation of guessing which parameters to choose to optimize a given system. By using libraries, we can examine a large parameter space and find trends present in our system and even optimal parameters to use for our design. It is difficult to screen libraries of certain cellular phenomena in high throughput using current technologies, so we need to look at other possible methods.
By localizing fluorescent proteins to specific organelles, each cell can be given a "microscopic barcode", or MiCode. Below you can see a single sample MiCode. Each member of a library will get a unique MiCode, distinguishing it from the rest of the library and tying the MiCode phenotype to a specific genotype.
This example MiCode has four targeted organelles: nucleus-red, vacuolar membrane-red, plasma membrane-blue, actin-green.