Team:Berkeley/Project/Construction

From 2012.igem.org

(Difference between revisions)
Line 65: Line 65:
<p align="center">
<p align="center">
<img src="https://static.igem.org/mediawiki/2012/d/d2/BsmBI.png" width="600">  
<img src="https://static.igem.org/mediawiki/2012/d/d2/BsmBI.png" width="600">  
-
<p>An example type IIs restriction enzyme, BsmBI.
+
<p align="center">An example type IIs restriction enzyme, BsmBI.
</p>
</p>
<br>
<br>
Line 87: Line 87:
<div class="col1" align = "justify">
<div class="col1" align = "justify">
<a name="MiCode Cloning"></a>
<a name="MiCode Cloning"></a>
-
     <img src="https://static.igem.org/mediawiki/2012/6/65/Project2_subheader2.jpg" width="980">
+
     <img src="https://static.igem.org/mediawiki/2012/6/65/Project2_subheader2.jpg" width="980" class="addborder">
</div>
</div>

Revision as of 05:47, 2 October 2012

header
iGEM Berkeley iGEMBerkeley iGEMBerkeley

Mercury

We chose to use Golden Gate Assembly because it allowed us to either create single-pot libraries or the interchange of combinatorially expand the number of multi-gene devices with smaller constituent parts. Golden Gate Assembly (GGA) is powered by Type IIs restriction enzymes, which cut distal to their recognition sites. Because of this, we have full control over the resulting 4bp overhangs, giving us a theoretical choice between 4^4, or 256 different overhangs. In practice, we reduced this set, eliminating cases where three out of the four matched to minimize chances of mis-annealing.

An example type IIs restriction enzyme, BsmBI.


The basic, fundamental unit of our GGA is the part plasmid, shown below. We


All about our MiCode design and cloning.