Team:TU-Eindhoven/Parts

From 2012.igem.org

(Difference between revisions)
(Prototype team page)
 
(29 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
{{:Team:TU-Eindhoven/Templates/header}}
-
 
+
{{:Team:TU-Eindhoven/Templates/head|image=https://static.igem.org/mediawiki/2012/9/97/Ourbiobricks_ehv.jpg}}
 +
<groupparts>iGEM012 TU-Eindhoven</groupparts>
 +
[[File:GECO.jpg|400px|center]]
 +
<p>To start off with, the iGEM team decided to prepare BioBricks<sup>TM</sup> of the <span class="lightblue">GECO proteins</span> since the BioBricks<sup>TM</sup> of the calcium channels CCH1 and MID1 (<partinfo>BBa_K363008</partinfo> and <partinfo>BBa_K363009</partinfo> respectively) are already available and able to ligate directly into bacterial plasmids. Moreover, to ligate these calcium channels into yeast plasmids, it's more practical to order the sequences directly from Iida<html><a href="#ref_Iida"name="text_Iida"><sup>[1]</sup></a></html>, because then the sequence is immediately available for yeast plasmid ligation.</p>
 +
<br />
 +
<p>Our iGEM team prepared three different BioBricks<sup>TM</sup>: BBa_K881000 (R-GECO), BBa_K881001 (G-GECO), BBa_K881002 (B-GECO). These three GECO proteins, which are obtained from ''Zhao et al. 2011''<html><a href="#ref_zhao" name="text_zhao"><sup>[2]</sup></a></html>, are red, green and blue fluorescent respectively. The protocol for ligation and restriction obtained from the BioBrick<sup>TM</sup> library didn't work for our Biobricks<sup>TM</sup>. Therefore, we designed <span class="lightblue">our own protocol</span>, which can be found at the '[[Team:TU-Eindhoven/Protocols|Protocol]]' page, and is shortly described here. The coding DNA for these three proteins was ligated into a <partinfo>pSB1C3</partinfo> vector. After culturing, the vectors were restricted with restriction enzymes XbaI en PstI. These enzymes restricted the vector nicely, however, the DNA sequence coding for the fluorescent GECO proteins appears to contain a restriction site for PstI as well. Therefore, this procedure was repeated with restriction enzymes <span class="lightblue">XbaI</span> and <span class="lightblue">SpeI</span>. Using this restriction method, the BioBricks<sup>TM</sup> can be used in <span class="lightblue">yeast</span> cells and <span class="lightblue">E. coli</span> bacteria.</p>
 +
<br />
 +
<p>Although, these BioBricks<sup>TM</sup> are prepared in a more efficient way using our own protocol, the <span class="lightblue">permission</span> we needed to apply the GECO BioBricks<sup>TM</sup> to registry library was more difficult than expected. You can read more about this struggle at the '[[Team:TU-Eindhoven/Thoughts|Other Thoughts]]' page at the MTA section.</p>
 +
<br />
 +
[[File:Growth_rate.JPG|400px|right|link=]]
 +
<h3>Characterization</h3>
 +
<p>E. coli strain <span class="lightblue">BL21</span> transformed with Part BBa_K881000 and Part BBa_K881001 ligated into vector <span class="lightblue">pET<sub>28a</sub></span> were cultured in LB media containing 100 µg/ml kanamycin for ~4 hours at 37°C. The growth rate was followed by use of <span class="lightblue">OD600 measurements</span> (see figure on the right). Then the culture was induced at an OD600 of 0,82 absorption units with 100 µg/ml IPTG.</p>
 +
<br />
 +
<h3>Harvesting and Purification</h3>
 +
<p>After induction for 15 hours, the cells were harvested and lysed with 5ml BugBuster containing 1µl/ml Benzonase. The supernatant of this suspension was put on a Ni-NTA column for purification and afterwards put on a PD10 column and washed with a TRIS buffer containing NaCl to remove all the calcium molecules. Then, an SDS-gel was prepared to check the abundance and the purity of the GECO proteins (See figure below). As can be seen in the gels, the GECO proteins are present in abundance.</p>
 +
<br />
 +
[[File:Groene GECO.jpg|300px|left]]
 +
[[File:Rode GECO.jpg|325px|right]]
 +
<br />
 +
<h3>Calcium titration</h3>
 +
<p>Before measuring the fluorescence, the samples were prepared first. A 30mM MOPS buffer was prepared containing 100mM KCl and 10mM EGTA. Since <span class="lightblue">EGTA</span> has a high affinity for calcium, in this buffer the GECO proteins will be discomposed from calcium completely. Then 1μl 1mg/ml protein was added to this buffer as well as a <span class="lightblue">range of calcium concentrations</span> ranging from 0nM to 3,900nM free calcium. Then, the fluorescence of the two GECO proteins, G-GECO and R-GECO, was measured at 20°C. The proteins were excited at 485nm and 565nm respectively. In the figure below, it can be seen that the intensity of the fluorescence increases upon increasing free calcium concentration, suggesting our BioBricks<sup>TM</sup> are indeed <span class="lightblue">sensitive</span> to calcium concentrations. </p>
 +
<br />
 +
[[File:G-GECO_Ca_Titration.JPG|310px|left]]
 +
[[File:R-GECO_Ca_Titration.JPG|310px|right]]
 +
<br />
 +
<h3>References</h3>
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
<ul>
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
<li><a href="#text_Iida" name="ref_Iida">[1]</a> K. Iida, et al., Essential, completely conserved glycine residue in the domain III S2S3 linker of voltage-gated calcium channel α1 subunits in yeast and mammals, Journal of Biological Chemistry 282: 25659-25667, (2007)</a></li>
-
This is a template page. READ THESE INSTRUCTIONS.
+
<li><a href="#text_zhao" name="ref_zhao">[2]</a> Y. Zhao, et al., An expanded palette of genetically encoded Ca2+ indicators, Science 333: 1888-1891, (2011)</a></li>
-
</div>
+
</ul>
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You are provided with this team page template with which to start the iGEM season. You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
+
-
</div>
+
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You <strong>MUST</strong> have all of the pages listed in the menu below with the names specified.  PLEASE keep all of your pages within your teams namespace. 
+
-
</div>
+
-
</div>
+
</html>
</html>
-
 
+
{{:Team:TU-Eindhoven/Templates/footer}}
-
<!-- *** End of the alert box *** -->
+
-
 
+
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
-
!align="center"|[[Team:TU-Eindhoven|Home]]
+
-
!align="center"|[[Team:TU-Eindhoven/Team|Team]]
+
-
!align="center"|[https://igem.org/Team.cgi?year=2012&team_name=TU-Eindhoven Official Team Profile]
+
-
!align="center"|[[Team:TU-Eindhoven/Project|Project]]
+
-
!align="center"|[[Team:TU-Eindhoven/Parts|Parts Submitted to the Registry]]
+
-
!align="center"|[[Team:TU-Eindhoven/Modeling|Modeling]]
+
-
!align="center"|[[Team:TU-Eindhoven/Notebook|Notebook]]
+
-
!align="center"|[[Team:TU-Eindhoven/Safety|Safety]]
+
-
!align="center"|[[Team:TU-Eindhoven/Attributions|Attributions]]
+
-
|}
+
-
 
+
-
 
+
-
 
+
-
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
+
-
 
+
-
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for  users who wish to know more.
+
-
 
+
-
 
+
-
<groupparts>iGEM012 TU-Eindhoven</groupparts>
+

Latest revision as of 01:25, 27 September 2012