Team:USyd-Australia/pUS203

From 2014.igem.org

(Difference between revisions)
 
(34 intermediate revisions not shown)
Line 4: Line 4:
<html>
<html>
<a name="protstart"></a>
<a name="protstart"></a>
-
<tr><td > <h7> <a href="http://parts.igem.org/Part:BBa_K1388000">pUS203</a></h7></td>
+
<h2><a href="http://parts.igem.org/Part:BBa_K1388000">pUS203 Controllable Integrase production</a></h2>
</html>
</html>
Line 21: Line 21:
</script>
</script>
-
<a name="PlasmidMap"></a>
+
<p style="font-size:12px">
-
<li style="font-weight: bold;"> <h2 onclick="toggle_visibility('PlasmidMap');">Plasmid Map of pUS203</h2></li>
+
To see this part on the iGEM Parts catalogue please click <a href="http://parts.igem.org/Part:BBa_K1388000">here</a>. <br>Sequences for this part are also available in <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLRDJ3OVdUUlhEVjA/view?usp=sharing">SnapGene (.dna file)</a>, <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLT3hQZno4VXFVZ0U/view?usp=sharing">FASTA (.fa file)</a>, <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLbndkclF5UlFNVE0/view?usp=sharing">GenBank Standard (.gb file)</a> and <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLak5Qdi1CbFZ4bm8/view?usp=sharing">Plain Text (.txt file)</a> file format.
-
<div id="PlasmidMap">
+
</p>
-
<ul style="font-weight: normal;">
+
<h2>Aim</h2>
-
<img src="https://static.igem.org/mediawiki/2014/6/67/PUS203.png" >
+
<p>Our aim was to create a controllable Integrase producing plasmid as a submission part. From the submission plasmid the controllable Integrase Part could then be ligated into a convenient low-copy plasmid to help reduce the potential toxicity of Integrase to the cell.</p>
-
To see this part on the iGEM Parts catalogue please click <a href="http://parts.igem.org/Part:BBa_K1388000">here</a>. <br>Sequence for this part are available in <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLRDJ3OVdUUlhEVjA/view?usp=sharing">SnapGene (.dna file)</a>, <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLT3hQZno4VXFVZ0U/view?usp=sharing">FASTA (.fa file)</a>, <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLbndkclF5UlFNVE0/view?usp=sharing">GenBank Standard (.gb file)</a> and <a href="https://drive.google.com/file/d/0B4B2M7gt-JMLak5Qdi1CbFZ4bm8/view?usp=sharing">Plain Text (.txt file)</a> file format.
+
 
 +
<h2>Approach</h2>
 +
<p>
 +
<img src="https://static.igem.org/mediawiki/2014/6/67/PUS203.png" align="right" width="50%">
 +
The 2010 Paris Bettencourt team had developed a <a href=http://parts.igem.org/wiki/index.php?title=Part:BBa_K329013>controllable Integrase part</a> for use a population counter in their project. We contacted them to see if we could source the part from them but it was unfortunately not possible. We set about creating the BioBrick using the araC-pBAD from the well characterized part <a href=http://parts.igem.org/Part:BBa_K731201>K731201</a> and ordering the IntI1 as a gBlock. The araC-pBAD system in pSB1C3 had previously been prepared by Honours student Sam Ross (called the SamR construct). Our next steps were the design of the gBlock and integration of the IntI1 gBlock into the SamR construct.
 +
</p>
 +
 
 +
<h2>Materials</h2>
 +
<ul>DNA<ul>
 +
<li>SamR Construct: araC-pBAD in pSC1B3</li>
 +
<li><a href="#">IntI1 gBlock</a>: to be inserted into SamR</li>
 +
<li>pUS44: Verified plasmid containing an AttI site, used in Validation</li>
 +
<li>aeBlue: Cassette PCR'ed from <a href=http://parts.igem.org/Part:BBa_K1033929>K1033929</a> for us in validation</li>
 +
</ul>
</ul>
</ul>
-
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
 
-
<br><br>
 
-
</div>
 
-
<a name="gBlockDesign"></a>
+
<ul>Primers
-
<li style="font-weight: bold;"> <h2 onclick="toggle_visibility('gBlockDesign');">Design of IntI1 gBlock</h2></li>
+
<table>
-
<div id="gBlockDesign">
+
  <tr>
-
<ul style="font-weight: normal;">
+
    <td width="50%">
-
The code for the Inti1 gene was sourced from pUS2056 (theUSyd  Coleman- Holmes lab had this LINK). We tried to get the part from the Paris Bettencourt team (from 2010 part <a href="http://parts.igem.org/cgi/partsdb/puttext.cgi">BBa_K329014</a>) but this was not possible so we had to make it. It was modified by Tom Geddes, Rokiah Alford and Nick Coleman to include: <ol>
+
<ul>
-
<li>- A different ribosome binding site, </li>
+
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers#iGEM1413">iGEM1413</a></li>
-
<li>- To remove an illegal Spe1 site near the end, </li>
+
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers#iGEM1414">iGEM1414</a></li>
-
<li>- To include a Sac1 restriction enzyme site at the beginning before the IntI1 gene so it could be excised independently of the promoter, </li>
+
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers#iGEM1415">iGEM1415</a></li>
-
<li>- To remove the pC promoter that was coded in the opposite direction to the promoter we wanted to use and would have clashed with the controllable promotion of this part, and </li>
+
-
<li>- To have Gibson ends that overlapped with the backbone we wanted to put it into which is described below.<li>
+
-
<br>
+
-
</ol>
+
-
This backbone, made by honours student Sam Ross, is PSB1C3 with araC-pBAD (which was sourced from <a "href=http://parts.igem.org/Part:BBa_K731201">BBa_K731201</a> a well characterized part) in between the suffix and prefix and will be called SamR’s plasmid throughout our documents. The code for the BioBrick section of this plasmid was used to predict the sequence for junction PCR sequences and our BioBrick’s sequence. </li>
+
-
<br>
+
-
Our first attempt to Gibson Assemble these two – the Inti1 Gblock and SamR’s plasmid – failed because the gibson end that overlapped the araC-pBAD section was incorrect. There was extra code after the code for pBAD which we had not anticipated. This triggered the redesign of the gblock.
+
</ul>
</ul>
 +
    </td>
 +
    <td>
 +
<ul>
 +
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers#iGEM1416">iGEM1416</a></li>
 +
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers">iGEM16</a></li>
 +
<li><a href="https://2014.igem.org/Team:USyd-Australia/Notebook/Primers">iGEM25</a></li>
 +
</ul>
 +
    </td>
 +
  </tr>
 +
  <tr>
 +
</table>
 +
 +
<h2>Inti1 gBlock Design</h2>
 +
<p>
 +
The code for the sequence for the IntI1 gene was sourced from pUS2056 but is highly conserved so this choice was out of convenience as the sequence was locally available. It was modified by Tom Geddes, Rokiah Alford and our supervisor Dr Nicholas Coleman to:<br><ul>
 +
<li>Include a Sac1 restriction enzyme site at the beginning before the Inti1 gene so it could be excised independently of the promoter if needed</li>
 +
<li>Include a different ribosome binding site </li>
 +
<li>Include Gibson ends that overlapped with the backbone for simple Gibson Assembly later with the SamR construct.</li>
 +
<li>Remove an illegal Spe1 site near the end to make it compliant with iGEM requirements</li>
 +
<li>Remove a promoter pC that was coded in the opposite direction to the promoter we wanted to use and would have clashed with the controllable promotion of this part</li></ul><br>
 +
Our first attempt to Gibson Assemble the SamR  construct and IntI1 gBlock failed because there was extra code after the code for pBAD which we had not anticipated. This meant that the Gibson Assembly could not properly integrate the gBlock. We discussed numerous options to try and either get rid of the problem sequence on the SamR construct or modify the ends of the gBlock to accommodate the problem sequence. In the end it was decided that a re-design of the gBlock would be the most efficient way to solve the problem.
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<br><br>
<br><br>
-
</div>
 
-
 
-
<a name="gBlockDesign2"></a>
 
-
<li style="font-weight: bold;"> <h2 onclick="toggle_visibility('gBlockDesign2');">Re-Design of first IntI1 gBlock</h2></li>
 
-
<div id="gBlockDesign2">
 
-
<ul style="font-weight: normal;">
 
-
Three major changes happened to the gblock. We changed the code for the ribosome cut site which had one base wrong, we decided to put an Nhe1 restriction enzyme cut site between the inti1 gene and the promoters on the SamR construct because the low copy backbone we planned to move this biobrick to for validation had an Sac1 cut site in its backbone, and finally we totally overhauled the Gibson end for the junction between the pBAD promoter and the Inti1 gene because there was extra code on the SamR construct that we didn’t know about when designing this gblock the first time. These changed were performed by our supervisor Nick Coleman in consultation with Rokiah Alford. <br><br>
 
-
The gibson assembly of SamR’s plasmid and the Inti1 gblock was successful as was checked in the following ways: junction PCR and sequencing, restriction digestion, biobrick PCR ad sequencing.
 
 +
<h2>Inti1 gBlock ReDesign</h2>
 +
<p>
 +
Three major changes were decided: <br>
 +
<ul>
 +
<li>Changed the code for the ribosome cut site as a base pair was incorrect</li>
 +
<li>To put an Nhe1 restriction enzyme cut site between the IntI1 gene and the promoters on the SamR construct. This was done to help in the ligation of this BioBrick into the low-copy backbone pUS202. </li>
 +
<li>Changing of the end sequences to accommodate the extra code present on the SamR construct</li>
</ul>
</ul>
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<br><br>
<br><br>
-
</div>
 
-
<a name="Construction"></a>
 
-
<li style="font-weight: bold;"> <h2 onclick="toggle_visibility('Construction');">Construction</h2></li>
 
-
<div id="Construction">
 
-
<ul style="font-weight: normal;">
 
-
The IntI1 gBlock was inserted into the SamR construct using <a href="http://www.addgene.org/plasmid-protocols/gibson-assembly/">Gibson Asssembly</a>. The ends of the gBlock in the redesign of the gBlock were compatible with the ends of the SamR construct and after running the Gibson Assembly reaction we used a variety of methods to prove that our gBlock had inserted correctly (See Below <a href="Proof">Proof</a> section)
 
-
</ul>
 
-
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
+
<h2>Construction</h2>
-
<br><br>
+
<p>
-
</div>
+
The IntI1 gBlock was inserted into the SamR construct using <a href="http://www.addgene.org/plasmid-protocols/gibson-assembly/">Gibson Asssembly</a>. The ends of the gBlock in the redesign were compatible with the ends of the SamR construct and after running the Gibson Assembly reaction we used a variety of methods to prove that our gBlock had inserted correctly.
 +
</p>
-
<a name="Proof"></a>
+
<p>
-
<li style="font-weight: bold;"> <h2 onclick="toggle_visibility('Proof');">Proof</h2></li>
+
These changed were performed by our supervisor Nick Coleman in consultation with Rokiah Alford. The redesigned gBlock was able to be successfully Gibsoned into the SamR backbone. To verify the presence of the insert we used junction primers which would amplify over both ends of the insert and could only amplify if the gBlock had been integrated into the SamR construct. <br>
-
<div id="Proof">
+
<br><b>Junction primer PCR</b><br>
-
<ul style="font-weight: normal;">
+
-
Junction primer PCR:
+
-
The colonies from the Gibson Assembly reaction of the SamR plasmid and the Inti1 gblock that grew of the LB+ Cm25 plates were screened using two sets of junction primers. One set was for the junction between the promoter and the gblock, the second for the junction of the gblock and the PSB1C3 backbone. <br><br>
+
-
Junction primers for the junction of promoter and gblock were iGEM1413 and iGEM1414. These yielded a fragment size of 377bp which was found in 9 out 12 of colonies sampled and patch plated.  This result was far more than we anticipated because the selection method was only or the backbone’s resistence not the insert which was only the modified integrase gene. Samples from the patch plate of these positive colonies were subjected to a second junction primer screening. The junction primers for this were iGEM1416 and iGEM25 (last year’s USyd iGEM team designed this primer to amplify the whole biobrick from the suffix end and we re-purposed it here). These yielded a fragment size of 432bp in 8 of the expected 9 colonies that were positive for the 1st junction screen.  From the colonies positive for both junction screens 3 were plasmid prep’d (colonies 3, 9, and 33). <br><br>
+
Junction primers for the junction of promoter and gblock were iGEM1413 and iGEM1414 and were expected to give a fragment size of 377 base pairs. <br>
-
<h3>Junction primer sequencing:</h3><br>
+
<img src="https://static.igem.org/mediawiki/2014/4/4e/USyd-AustraliaWell_Images_restriction_Digest.png"> <br>
-
The products of both junction PCRs of these three colonies were sequenced and all sequences (the forward and reverse directions for each of the junctions i.e. 4 sequences per colony) corresponded to that predicted for the junctions using the code of the SamR plasmid and the gblock we designed. <br><br>
+
9 out of the 12 colonies screened gave a positive result and these were further screened with a second set of junction primers on the other side of the gBlock. The junction primers for this were iGEM1416 and iGEM25 and were expected to yielad a fragment size of 432bp. <br>
-
<h3>Plasmid Prep and check with restriction digestion:</h3><br>
+
<img src="https://static.igem.org/mediawiki/2014/7/70/USyd-Australia_RealSecondPCR_Junction_screen.png"> <br>
-
These three plasmid preps were checked by restriction digestion using combinations of an enzyme from the suffix (Spe1 and Pst1) and prefix (EcoR1), as well as Sac1 which has no cut sites and nhe1, an enzyme that cut only once at a site we introduced into the gblock for this purpose and to allow others to move the inti1 gene independently of the rest of the biobrick. The results were as predicted using snap gene for all except the Sac1 digest. We were satisfied with these results despite the Sac1 error because the other fragments were as expected and most importantly because Nhe1 cut, which could only have occurred if the gblock had been incorporated into the plasmid. These results supported the junction primer results.  The enzyme in the Sac1 digest of pUS203 was heat killed and this  digested  plasmid prep was used for the PCR of the biobrick. This showed that the unexpected action of the Sac1 seen in the gel for the digest of this plasmid luckily didn’t reflect an error in the biobrick code. <br><br>  
+
Again 9 of the 12 colonies were positive here. The PCR product was sequenced and corresponded with the expected sequence for the plasmid. 3 of the 8 colonies were selected to be grown up and Plasmid Prepped to remove the plasmid and allow restriction digest and sequencing of the plasmid for further verification.<br>
-
<h3>Biobrick PCR and sequencing:</h3><br>
+
 
-
The final check for this plasmid was to PCR the entire biobrick fragment using iGEM16 and iGEM25 (last year’s USyd team’s primers for the biobrick). This yelided a fragment size of 2676bp in 6 out of 8 PCR reactions of heat killed Sac1 restriction digested pUS203.  This PCR product was sequenced using the iGEM16 and iGEM25.
+
<br><b>Restriction Digest</b><br>
 +
 
 +
The pUS203 plasmid was further confirmed with restriction digestion. Spe1, Pst1 and EcoR1 are in the prefix and suffix and should cut.  An Nhe1 restriction site was added into the gBlock code and so a cut with this enzyme would indicate the gBlock had been inserted. Sac1 should not cut and should be identical to the uncut control lane. <br>
 +
 
 +
<img src="https://static.igem.org/mediawiki/2014/4/4e/USyd-AustraliaWell_Images_restriction_Digest.png"><br>
 +
 
 +
The digest results were as expected using SnapGene’s Virtual Digest tool. We were satisfied with these results despite the Sac1 error because the other fragments were as expected and most importantly because Nhe1 cut, which could only have occurred if the gblock had been incorporated into the plasmid. The Sac1 sample was heat-treated to inactive the Sac1 enzyme and used was used as a template to PCR the BioBrick. The results were still as expected which showed that the unexpected action of the Sac1 seen in the gel for the digest of this plasmid luckily didn’t reflect an error in the biobrick code. <br><br>
 +
 
 +
<b>Biobrick PCR and sequencing</b><br>
 +
The final check for this plasmid was to PCR the entire biobrick fragment using iGEM16 and iGEM25 and sequencing the product.  
 +
</p>
-
</ul>
 
-
</li>
 
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<a href="#protstart">Back to top</a><!------------------------------------------------------------------------------------------------------------>
<br><br>
<br><br>
-
</div>
+
<h2>Validation</h2>
-
 
+
-
 
+
-
<h2Validation</h2>
+
<ul style="font-weight: normal;">
<ul style="font-weight: normal;">
To validate our araC-pBAD/IntI1 BioBrick it would need to be present in a low copy plasmid in order to reduce the amount produced as it is potentially toxic to the cell at high concentrations. Our intial plan was to insert the BioBrick into pUS202 but it turned out not to be low-copy after validation. The back up option was to ligate the BioBrick into pSB6A1. The initial attempt was not successful and due to time constraints we decided to try and test the integron construct in the pSB1C3 it was currently in even with the potential toxicity.<br><br>
To validate our araC-pBAD/IntI1 BioBrick it would need to be present in a low copy plasmid in order to reduce the amount produced as it is potentially toxic to the cell at high concentrations. Our intial plan was to insert the BioBrick into pUS202 but it turned out not to be low-copy after validation. The back up option was to ligate the BioBrick into pSB6A1. The initial attempt was not successful and due to time constraints we decided to try and test the integron construct in the pSB1C3 it was currently in even with the potential toxicity.<br><br>
To test for the proper expression of our integron gene in the BioBrick we wanted to have an AttI site and integrase protein present in E. coli. This was so that upon transformation with a cassette (which has an AttC site) a co-integrate would quickly form with the AttI site and before the cassettes  could be lost out of the cell. Upon integration of the cassette the Gentomycin resistance (GmR) present on the cassette is expressed allowing us to select for the correct cells on Gentomycin plates. The negative control had no arabinose induction and so the cassette should not integrate and the cells should not be Gm resistant.<br><br>
To test for the proper expression of our integron gene in the BioBrick we wanted to have an AttI site and integrase protein present in E. coli. This was so that upon transformation with a cassette (which has an AttC site) a co-integrate would quickly form with the AttI site and before the cassettes  could be lost out of the cell. Upon integration of the cassette the Gentomycin resistance (GmR) present on the cassette is expressed allowing us to select for the correct cells on Gentomycin plates. The negative control had no arabinose induction and so the cassette should not integrate and the cells should not be Gm resistant.<br><br>
-
<img src=https://static.igem.org/mediawiki/2014/7/71/USyd-Australia_Integrase_diagrams_1.png”><br><br>
+
<img src="https://static.igem.org/mediawiki/2014/7/71/USyd-Australia_Integrase_diagrams_1.png" width="98%"><br><br>
The initial experiments did not yield positive results and due to time constraints we have not been able to troubleshoot the experiment.  
The initial experiments did not yield positive results and due to time constraints we have not been able to troubleshoot the experiment.  
</ul>
</ul>

Latest revision as of 02:55, 18 October 2014

iGEM_Link


pUS203 Controllable Integrase production

To see this part on the iGEM Parts catalogue please click here.
Sequences for this part are also available in SnapGene (.dna file), FASTA (.fa file), GenBank Standard (.gb file) and Plain Text (.txt file) file format.

Aim

Our aim was to create a controllable Integrase producing plasmid as a submission part. From the submission plasmid the controllable Integrase Part could then be ligated into a convenient low-copy plasmid to help reduce the potential toxicity of Integrase to the cell.

Approach

The 2010 Paris Bettencourt team had developed a controllable Integrase part for use a population counter in their project. We contacted them to see if we could source the part from them but it was unfortunately not possible. We set about creating the BioBrick using the araC-pBAD from the well characterized part K731201 and ordering the IntI1 as a gBlock. The araC-pBAD system in pSB1C3 had previously been prepared by Honours student Sam Ross (called the SamR construct). Our next steps were the design of the gBlock and integration of the IntI1 gBlock into the SamR construct.

Materials

    DNA
    • SamR Construct: araC-pBAD in pSC1B3
    • IntI1 gBlock: to be inserted into SamR
    • pUS44: Verified plasmid containing an AttI site, used in Validation
    • aeBlue: Cassette PCR'ed from K1033929 for us in validation
    Primers

    Inti1 gBlock Design

    The code for the sequence for the IntI1 gene was sourced from pUS2056 but is highly conserved so this choice was out of convenience as the sequence was locally available. It was modified by Tom Geddes, Rokiah Alford and our supervisor Dr Nicholas Coleman to:

    • Include a Sac1 restriction enzyme site at the beginning before the Inti1 gene so it could be excised independently of the promoter if needed
    • Include a different ribosome binding site
    • Include Gibson ends that overlapped with the backbone for simple Gibson Assembly later with the SamR construct.
    • Remove an illegal Spe1 site near the end to make it compliant with iGEM requirements
    • Remove a promoter pC that was coded in the opposite direction to the promoter we wanted to use and would have clashed with the controllable promotion of this part

    Our first attempt to Gibson Assemble the SamR construct and IntI1 gBlock failed because there was extra code after the code for pBAD which we had not anticipated. This meant that the Gibson Assembly could not properly integrate the gBlock. We discussed numerous options to try and either get rid of the problem sequence on the SamR construct or modify the ends of the gBlock to accommodate the problem sequence. In the end it was decided that a re-design of the gBlock would be the most efficient way to solve the problem. Back to top

    Inti1 gBlock ReDesign

    Three major changes were decided:

    • Changed the code for the ribosome cut site as a base pair was incorrect
    • To put an Nhe1 restriction enzyme cut site between the IntI1 gene and the promoters on the SamR construct. This was done to help in the ligation of this BioBrick into the low-copy backbone pUS202.
    • Changing of the end sequences to accommodate the extra code present on the SamR construct
    Back to top

    Construction

    The IntI1 gBlock was inserted into the SamR construct using Gibson Asssembly. The ends of the gBlock in the redesign were compatible with the ends of the SamR construct and after running the Gibson Assembly reaction we used a variety of methods to prove that our gBlock had inserted correctly.

    These changed were performed by our supervisor Nick Coleman in consultation with Rokiah Alford. The redesigned gBlock was able to be successfully Gibsoned into the SamR backbone. To verify the presence of the insert we used junction primers which would amplify over both ends of the insert and could only amplify if the gBlock had been integrated into the SamR construct.

    Junction primer PCR
    Junction primers for the junction of promoter and gblock were iGEM1413 and iGEM1414 and were expected to give a fragment size of 377 base pairs.

    9 out of the 12 colonies screened gave a positive result and these were further screened with a second set of junction primers on the other side of the gBlock. The junction primers for this were iGEM1416 and iGEM25 and were expected to yielad a fragment size of 432bp.

    Again 9 of the 12 colonies were positive here. The PCR product was sequenced and corresponded with the expected sequence for the plasmid. 3 of the 8 colonies were selected to be grown up and Plasmid Prepped to remove the plasmid and allow restriction digest and sequencing of the plasmid for further verification.

    Restriction Digest
    The pUS203 plasmid was further confirmed with restriction digestion. Spe1, Pst1 and EcoR1 are in the prefix and suffix and should cut. An Nhe1 restriction site was added into the gBlock code and so a cut with this enzyme would indicate the gBlock had been inserted. Sac1 should not cut and should be identical to the uncut control lane.

    The digest results were as expected using SnapGene’s Virtual Digest tool. We were satisfied with these results despite the Sac1 error because the other fragments were as expected and most importantly because Nhe1 cut, which could only have occurred if the gblock had been incorporated into the plasmid. The Sac1 sample was heat-treated to inactive the Sac1 enzyme and used was used as a template to PCR the BioBrick. The results were still as expected which showed that the unexpected action of the Sac1 seen in the gel for the digest of this plasmid luckily didn’t reflect an error in the biobrick code.

    Biobrick PCR and sequencing
    The final check for this plasmid was to PCR the entire biobrick fragment using iGEM16 and iGEM25 and sequencing the product.

    Back to top

    Validation

      To validate our araC-pBAD/IntI1 BioBrick it would need to be present in a low copy plasmid in order to reduce the amount produced as it is potentially toxic to the cell at high concentrations. Our intial plan was to insert the BioBrick into pUS202 but it turned out not to be low-copy after validation. The back up option was to ligate the BioBrick into pSB6A1. The initial attempt was not successful and due to time constraints we decided to try and test the integron construct in the pSB1C3 it was currently in even with the potential toxicity.

      To test for the proper expression of our integron gene in the BioBrick we wanted to have an AttI site and integrase protein present in E. coli. This was so that upon transformation with a cassette (which has an AttC site) a co-integrate would quickly form with the AttI site and before the cassettes could be lost out of the cell. Upon integration of the cassette the Gentomycin resistance (GmR) present on the cassette is expressed allowing us to select for the correct cells on Gentomycin plates. The negative control had no arabinose induction and so the cassette should not integrate and the cells should not be Gm resistant.



      The initial experiments did not yield positive results and due to time constraints we have not been able to troubleshoot the experiment.
    Back to top