Team:Hannover/Results/Plant Vector

From 2014.igem.org

(Difference between revisions)
 
Line 9: Line 9:
<h2>Results</h2><p class="text">The exchange of the original promoter of the pORE_E3 vector was successful. We gained a “new” vector with a 2x35s promoter (pORE_E3_2x35s). Furthermore we were able to remove the restriction sites XhoI and BglII from this vector. This was checked by a double digest and sequencing. Unfortunately our last attempt, changing the MCS to the MCS of RFC[21] via the insertion of two hybridized primers with overhangs, failed several times. Even a modified protocol couldn’t bring us the expected success. At the end, we ran out of time.<br><br>Of cause, we could have synthesized the insert, cut it with restriction enzymes and then clone it into the vector, but that’s what everyone could have done…</p>
<h2>Results</h2><p class="text">The exchange of the original promoter of the pORE_E3 vector was successful. We gained a “new” vector with a 2x35s promoter (pORE_E3_2x35s). Furthermore we were able to remove the restriction sites XhoI and BglII from this vector. This was checked by a double digest and sequencing. Unfortunately our last attempt, changing the MCS to the MCS of RFC[21] via the insertion of two hybridized primers with overhangs, failed several times. Even a modified protocol couldn’t bring us the expected success. At the end, we ran out of time.<br><br>Of cause, we could have synthesized the insert, cut it with restriction enzymes and then clone it into the vector, but that’s what everyone could have done…</p>
<center><table border="0"><tr><td><a href="https://static.igem.org/mediawiki/2014/5/5a/Hannover_20141016_PORE-E3_AY562536_Map.png" data-lightbox="galery1" data-title="Fig. 1A: The vector pORE_E3 (left) with the origin sequence"><img src="https://static.igem.org/mediawiki/2014/5/5a/Hannover_20141016_PORE-E3_AY562536_Map.png" width="300px"></a></td><td><a href="https://static.igem.org/mediawiki/2014/0/0f/Hannover_20141016_PORE_2x35S_RCF21_Map.png" data-lightbox="galery1" data-title="Fig. 1B: Our designed PORE_2x35S_RCF[21] with a 2x35s promoter and the MCS of RFC[21]"><img src="https://static.igem.org/mediawiki/2014/0/0f/Hannover_20141016_PORE_2x35S_RCF21_Map.png" width="300px"></a></td></tr>
<center><table border="0"><tr><td><a href="https://static.igem.org/mediawiki/2014/5/5a/Hannover_20141016_PORE-E3_AY562536_Map.png" data-lightbox="galery1" data-title="Fig. 1A: The vector pORE_E3 (left) with the origin sequence"><img src="https://static.igem.org/mediawiki/2014/5/5a/Hannover_20141016_PORE-E3_AY562536_Map.png" width="300px"></a></td><td><a href="https://static.igem.org/mediawiki/2014/0/0f/Hannover_20141016_PORE_2x35S_RCF21_Map.png" data-lightbox="galery1" data-title="Fig. 1B: Our designed PORE_2x35S_RCF[21] with a 2x35s promoter and the MCS of RFC[21]"><img src="https://static.igem.org/mediawiki/2014/0/0f/Hannover_20141016_PORE_2x35S_RCF21_Map.png" width="300px"></a></td></tr>
-
<tr><th colspan="3"><p class="text">Fig. 1: Pictures showing the vector pORE_E3 (left) with the origin sequence and (right) our designed PORE_2x35S_RCF[21] with a 2x35s promoter and the MCS of RFC[21] (plasmid maps originally taken from <a href="http://www.snapgene.com/resources">www.snapgene.com/resources</a>).</p></th></td></tr></table></center>
+
<tr><td colspan="3"><p class="text">Fig. 1: Pictures showing the vector pORE_E3 (left) with the origin sequence and (right) our designed PORE_2x35S_RCF[21] with a 2x35s promoter and the MCS of RFC[21] (plasmid maps originally taken from <a href="http://www.snapgene.com/resources">www.snapgene.com/resources</a>).</p></td></tr></table></center>
<p id="Fusszeile"><br><br><br><br><img src="https://static.igem.org/mediawiki/2014/6/6a/Hannover_20141010Fusszeile2.jpg" width="980px" style="float:right" /></p>
<p id="Fusszeile"><br><br><br><br><img src="https://static.igem.org/mediawiki/2014/6/6a/Hannover_20141010Fusszeile2.jpg" width="980px" style="float:right" /></p>
</body>
</body>
</html>
</html>

Latest revision as of 23:04, 17 October 2014

Results / Plant vector

We want to provide iGEM a new Plant vector with a BioBrick RFC[21]MCS and 2x35S promotor.

Results

The exchange of the original promoter of the pORE_E3 vector was successful. We gained a “new” vector with a 2x35s promoter (pORE_E3_2x35s). Furthermore we were able to remove the restriction sites XhoI and BglII from this vector. This was checked by a double digest and sequencing. Unfortunately our last attempt, changing the MCS to the MCS of RFC[21] via the insertion of two hybridized primers with overhangs, failed several times. Even a modified protocol couldn’t bring us the expected success. At the end, we ran out of time.

Of cause, we could have synthesized the insert, cut it with restriction enzymes and then clone it into the vector, but that’s what everyone could have done…

Fig. 1: Pictures showing the vector pORE_E3 (left) with the origin sequence and (right) our designed PORE_2x35S_RCF[21] with a 2x35s promoter and the MCS of RFC[21] (plasmid maps originally taken from www.snapgene.com/resources).





Retrieved from "http://2014.igem.org/Team:Hannover/Results/Plant_Vector"