Difference between revisions of "Part:BBa K2336035"

 
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
  
 
__NOTOC__
 
__NOTOC__
 
<partinfo>BBa_K2336035 short</partinfo>
 
<partinfo>BBa_K2336035 short</partinfo>
  
The report part of our circuit. It can be expressed to bind silicon
+
The capture part of our circuit. It can be expressed to bind silicon
 +
 
 +
<h1>'''Usage and Biology'''</h1>
 +
<p> OprF is motif cell wall anchor domain protein. GS stands for GS linker. FLAG is designed to test fluorescence. The genetic engineering bacteria can express the protein on its cell membrane. Then the bacteria can combine with silica surface. So we can get them back. Figure 1 shows the circuit of it.
 +
[[File: Sitag.png|center|thumb|400px|Figure 1: The circuit of oprF-GS-Sitag-FLAG.]]</p>
 +
<p>  As we’ve mentioned, this is the final step. After sensing and capturing task finished, the bacteria will combine with silica net, so we can achieve our goal -- get them back (with lanthanum). Figure 2 shows how it works.
 +
[[File: si.png|center|thumb|400px|Figure 2: The preview of Sitag displayed on cell membrane and work.]]</p>
 +
 
 +
<h1>'''Characterization'''</h1>
 +
<p>  We did some experiment to prove it works. </p>
 +
===SDS-PAGE===
 +
<p>  After oprF-GS-Sitag-FLAG is expressed successfully, we centrifuged the bacteria liquid and separated different proteins by SDS-PAGE.
 +
[[File: Sitagglue.png|center|thumb|400px|Figure 2: The preview of Sitag displayed on cell wall and work.]]</p>
 +
<p>Figure 3 shows an obvious ~57kDa protein bands of oprF-Sitag in test lane, which cannot be found in control lane. This result proves that the bacteria could express oprF-Sitag successfully.</p>
  
<!-- Add more about the biology of this part here
+
<h1>'''improvement'''</h1>
===Usage and Biology===
+
<p>  This part is an expansion of our team's work in 2015 (https://parts.igem.org/Part:BBa_K1592007). Two years ago, we did it in yeast. Now we put gene into <I>E.coli</I>. It was a hard experiment, but finally we made it. The gene order is also different from that in eukaryotes, such as yeast. We consider it as a great breakthrough.</p>
 +
<p>  Next we will do experiment to test its binding ability. We hope it will have the effect as we expected.</p>
  
 
<!-- -->
 
<!-- -->

Latest revision as of 20:17, 31 October 2017


oprF-GS-Sitag-FLAG

The capture part of our circuit. It can be expressed to bind silicon

Usage and Biology

OprF is motif cell wall anchor domain protein. GS stands for GS linker. FLAG is designed to test fluorescence. The genetic engineering bacteria can express the protein on its cell membrane. Then the bacteria can combine with silica surface. So we can get them back. Figure 1 shows the circuit of it.

Figure 1: The circuit of oprF-GS-Sitag-FLAG.

As we’ve mentioned, this is the final step. After sensing and capturing task finished, the bacteria will combine with silica net, so we can achieve our goal -- get them back (with lanthanum). Figure 2 shows how it works.

Figure 2: The preview of Sitag displayed on cell membrane and work.

Characterization

We did some experiment to prove it works.

SDS-PAGE

After oprF-GS-Sitag-FLAG is expressed successfully, we centrifuged the bacteria liquid and separated different proteins by SDS-PAGE.

Figure 2: The preview of Sitag displayed on cell wall and work.

Figure 3 shows an obvious ~57kDa protein bands of oprF-Sitag in test lane, which cannot be found in control lane. This result proves that the bacteria could express oprF-Sitag successfully.

improvement

This part is an expansion of our team's work in 2015 (https://parts.igem.org/Part:BBa_K1592007). Two years ago, we did it in yeast. Now we put gene into E.coli. It was a hard experiment, but finally we made it. The gene order is also different from that in eukaryotes, such as yeast. We consider it as a great breakthrough.

Next we will do experiment to test its binding ability. We hope it will have the effect as we expected.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    INCOMPATIBLE WITH RFC[12]
    Illegal NheI site found at 72
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BamHI site found at 639
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal NgoMIV site found at 3
    Illegal AgeI site found at 1527
  • 1000
    COMPATIBLE WITH RFC[1000]