Difference between revisions of "Team:Aalto-Helsinki/Parts"

m
Line 97: Line 97:
 
<p><b>Validation:</b> Our GFP brick has been fully sequenced, and the sequencing results were as expected. We have also been able to express the GFP after fusing it with an amphiphilic brick. This construct functioned under <a href="http://parts.igem.org/Part:BBa_K608003">BBa_K608003</a>, a strong constitutive promoter and a medium RBS. HS Slovenia Team also helped us validate this brick. They gained positive results of their construct with the GFP through colony PCR and analytical restrictions, but were unable to detect the fluerescence under UV light or functionality of the fused protein.</p>
 
<p><b>Validation:</b> Our GFP brick has been fully sequenced, and the sequencing results were as expected. We have also been able to express the GFP after fusing it with an amphiphilic brick. This construct functioned under <a href="http://parts.igem.org/Part:BBa_K608003">BBa_K608003</a>, a strong constitutive promoter and a medium RBS. HS Slovenia Team also helped us validate this brick. They gained positive results of their construct with the GFP through colony PCR and analytical restrictions, but were unable to detect the fluerescence under UV light or functionality of the fused protein.</p>
 
<p style="color:red">The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name <b><a href="http://parts.igem.org/Part:BBa_K1655001">BBa_K1655001</a></b>.</p>
 
<p style="color:red">The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name <b><a href="http://parts.igem.org/Part:BBa_K1655001">BBa_K1655001</a></b>.</p>
−
<p>Click <a href="">here</a> to download the full sequence of our Fusable GFP in pSB1C3 backbone.</p>
+
<p>Click <a href="https://static.igem.org/mediawiki/2015/5/51/Aalto-Helsinki_gfp_sequence_ah009.gb">here</a> to download the full sequence of our Fusable GFP in pSB1C3 backbone.</p>
  
 
</section>
 
</section>
Line 113: Line 113:
 
<p><b>Validation:</b> Our amphiphilic brick's sequencing results were unclear, as the brick is mainly built of short repeats. <span style="color:red">Microscope pictures!</span></p>
 
<p><b>Validation:</b> Our amphiphilic brick's sequencing results were unclear, as the brick is mainly built of short repeats. <span style="color:red">Microscope pictures!</span></p>
 
<p style="color:red">The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name <b><a href="http://parts.igem.org/Part:BBa_K1655002">BBa_K1655002</a></b>.</p>
 
<p style="color:red">The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name <b><a href="http://parts.igem.org/Part:BBa_K1655002">BBa_K1655002</a></b>.</p>
−
<p>Click <a href="">here</a> to download the full sequence of the Amphiphilic Brick in pSB1C3 backbone.</p>
+
<p>Click <a href="https://static.igem.org/mediawiki/2015/4/41/Aalto-Helsinki_amph_sequence_ah009.gb">here</a> to download the full sequence of the Amphiphilic Brick in pSB1C3 backbone.</p>
  
  

Revision as of 08:17, 15 September 2015

Submitted Parts

Propane 1 / BBa_K1655000

Figure 1. Propane 1

Our Propane 1 includes 4 of the 10 required genes to produce propane in E. coli. The plasmid has been assembled from IDT's gBlocks with NEBuilder assembly, similar to Gibson Assembly.

Validation: We restricted our Propane 1 and ran the insert on an agarose gel. From the picture we can tell that the insert is the correct size. The result can be seen in Figure 2.
Additionally, we did a colony PCR with VR and our primer P001. The VR primer attaches to our plasmid's backbone while P001 anneals with the very beginning of our construct. With this colony PCR we were able to show that the insert is present and it is indeed in the pSB1C3 backbone. See figure 3 for results, where the product in wells 1, and 5-10 is of the right size.

The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name BBa_K1655000.

Click here to download the full sequence of Propane 1 in pSB1C3 backbone.

Fusable GFP / BBa_K1655001

Figure 4. GFP Brick

We built a GFP biobrick which can be fused to any protein's aminoterminal end with the standard BioBrick assembly enzymes. We have added an extra nucleotide prior to the brick's suffix to maintain the reading frame after fusion, which is typically lost when the restriction enzyme assembly is used.

Validation: Our GFP brick has been fully sequenced, and the sequencing results were as expected. We have also been able to express the GFP after fusing it with an amphiphilic brick. This construct functioned under BBa_K608003, a strong constitutive promoter and a medium RBS. HS Slovenia Team also helped us validate this brick. They gained positive results of their construct with the GFP through colony PCR and analytical restrictions, but were unable to detect the fluerescence under UV light or functionality of the fused protein.

The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name BBa_K1655001.

Click here to download the full sequence of our Fusable GFP in pSB1C3 backbone.

Amphiphilic / BBa_K1655002

Figure 5. Amphiphilic Brick

We submitted a sole amphiphilic brick, containing only the coding region of the ampihphilic protein. This brick can be used to produce intracellular micelles or vesicles under any chosen expression system.

Validation: Our amphiphilic brick's sequencing results were unclear, as the brick is mainly built of short repeats. Microscope pictures!

The colony which produced the product seen in figure 3, well 10 was sent to the registry under the name BBa_K1655002.

Click here to download the full sequence of the Amphiphilic Brick in pSB1C3 backbone.

Part Documentation

Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.

Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years 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.

Part Table

<groupparts>iGEM015 Example</groupparts>