"
Team:UC Chile/Results/Int C
From 2012.igem.org
(Created page with "{{UC_Chile4}} <h2>pSB1A3_IntC (From 2010 Utah's iGEM team)</h2> We decided to use this plasmid to place the LuxCDEG part of the Lux operon in this plasmid, however after various...") |
|||
| Line 1: | Line 1: | ||
{{UC_Chile4}} | {{UC_Chile4}} | ||
| + | |||
| + | |||
| + | <h3>Int_C transformation</h3> | ||
| + | |||
| + | [[File:Int_C-Failagain.JPG| 600px| center]] | ||
| + | |||
| + | <br> | ||
<h2>pSB1A3_IntC (From 2010 Utah's iGEM team)</h2> | <h2>pSB1A3_IntC (From 2010 Utah's iGEM team)</h2> | ||
Revision as of 07:23, 26 September 2012
Int_C transformation
pSB1A3_IntC (From 2010 Utah's iGEM team)
We decided to use this plasmid to place the LuxCDEG part of the Lux operon in this plasmid, however after various attempts to transform Synechocystis without success we reconsidered (see below SOMEWHERE!!! [[]]) due to problems regarding the design of this plasmid backbone. After analyzing the sequence of the vector (CODE HERE) we blasted the sequences of the recombination sites and we found out that position of the sequences of each recombination site are swapped, leaving the backbone part of the plasmid to be integrated into the genome. Furthermore, the recombination sites are separated by aproximately 2.2 kilobases, knocking 1 gene.
You can see their original construct design here.
Here we illustrate the recombination mechanism in which the Int_C plasmid would integrate the backbone part of the vector to the genome.
