Team:Cambridge
From 2009.igem.org
Line 48: | Line 48: | ||
<div class="contentf"> | <div class="contentf"> | ||
<div style="height: 400; padding: 5px; background:#fff;"> | <div style="height: 400; padding: 5px; background:#fff;"> | ||
- | <h1>Project | + | <h1>The Project</h1> |
- | Under construction <br /><b> Under construction </b> <a href="https://2009.igem.org/Team:Cambridge/ | + | Under construction <br /><b> Under construction </b> <a href="https://2009.igem.org/Team:Cambridge/Project"> Read on...</a> |
</div> | </div> | ||
</div> | </div> | ||
Line 60: | Line 60: | ||
<div class="contentf"> | <div class="contentf"> | ||
<div style="height: 400; padding: 5px; background:#fff;"> | <div style="height: 400; padding: 5px; background:#fff;"> | ||
- | <h1> | + | <h1>The Team</h1> |
- | Under construction. <br /><b> Under construction. </b> <a href="https://2009.igem.org/Team:Cambridge/ | + | Under construction. <br /><b> Under construction. </b> <a href="https://2009.igem.org/Team:Cambridge/Team"> Read on...</a> |
</div> | </div> | ||
</div> | </div> | ||
Line 72: | Line 72: | ||
<div class="contentf"> | <div class="contentf"> | ||
<div style="height: 400; padding: 5px; background:#fff;"> | <div style="height: 400; padding: 5px; background:#fff;"> | ||
- | <h1> | + | <h1>Protocol</h1> |
Under construction<br /> <b> Under construction. </b> | Under construction<br /> <b> Under construction. </b> | ||
- | <a href="https://2009.igem.org/Team:Cambridge/ | + | <a href="https://2009.igem.org/Team:Cambridge/Protocol"> Read on...</a> |
</div> | </div> | ||
Line 86: | Line 86: | ||
<div class="contentf"> | <div class="contentf"> | ||
<div style="height: 400; padding: 5px; background:#fff;"> | <div style="height: 400; padding: 5px; background:#fff;"> | ||
- | <h1> | + | <h1>Notebook</h1> |
- | Under construction.</b> <a href="https://2009.igem.org/Team:Cambridge/ | + | Under construction.</b> <a href="https://2009.igem.org/Team:Cambridge/Notebook">Read on...</a> |
</div> | </div> | ||
</div> | </div> |
Revision as of 10:52, 21 July 2009
. | |
Previous iGEM teams have focused on genetically engineering bacteria to respond to novel inputs – for example light, or biologically significant compounds. There is an unmistakable need, therefore, to also develop clear, user-friendly outputs, especially for use with biosensors. The most popular output is the expression of a fluorescent protein, detectable using fluorescence microscopy. However, how much easier would it be if we could simply see the output with our own eyes? The Cambridge 2009 iGEM team is engineering E. coli to produce a range of pigments in order to equip future projects with better, more reliable, discrete outputs under logic control. Further, our bacteria utilize a shutter mechanism that guarantees pigment production after just a brief exposure to the desired input. | |
Team Example |
Home | The Team | The Project | Parts Submitted to the Registry | Modelling | Notebook | Protocols |
---|
(Or you can choose different headings. But you must have a team page, a project page, and a notebook page.)
OverviewPrevious iGEM teams have focused on genetically engineering bacteria to respond to novel inputs – for example light, or biologically significant compounds. There is an unmistakable need, therefore, to also develop clear, user-friendly outputs, especially for use with biosensors. The most popular output is the expression of a fluorescent protein, detectable using fluorescence microscopy. However, how much easier would it be if we could simply ''see'' the output with our own eyes? The Cambridge 2009 iGEM team is engineering E. coli to produce a range of pigments in order to equip future projects with better, more reliable, discrete outputs under logic control. Further, our bacteria utilize a shutter mechanism that guarantees pigment production after just a brief exposure to the desired input. |
||
|
||
|
||
|
||
NotebookUnder construction. Read on... |
||