Team:Berkeley/Project/Construction

From 2012.igem.org

(Difference between revisions)
Line 61: Line 61:
<div class="col1" align="justify">
<div class="col1" align="justify">
<p>
<p>
-
We chose to use <a href="http://j5.jbei.org/j5manual/pages/23.html">Golden Gate Assembly</a> because it allowed for either scarless, single-pot library creation or the interchangeability of parts to rapidly create multipart devices.
+
We chose to use <a href="http://j5.jbei.org/j5manual/pages/23.html">Golden Gate Assembly</a> 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 (GG) 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.
 +
<img src="
</p>
</p>
</div>
</div>

Revision as of 12:34, 1 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 (GG) 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.


All about our MiCode design and cloning.