Difference between revisions of "Part:BBa K2368011"

 
(5 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
__NOTOC__
 
__NOTOC__
 
<h1>Introduction</h1>
 
<h1>Introduction</h1>
<partinfo>BBa_K2368024 short</partinfo>
+
<p style="text-align: center"><partinfo>BBa_K2368011 short</partinfo></p>
<p> This part sweetness receptor T1R3 fusion with the FLAG tag, just like the picture showed below. </p>
+
<p> This part sweetness receptor T1R3 fusion with the Flag tag, just like the picture showed below. </p>
  
 
[[File:T-BIT-China-2017parts-45.png|center|500px|默认文字]]
 
[[File:T-BIT-China-2017parts-45.png|center|500px|默认文字]]
 
+
<p style="text-align: center">Fig. 1 The schematic diagram of T1R3-Flag</p>
  
  
 
<h1>Design</h1>
 
<h1>Design</h1>
<p> In order to show whether the sweet receptor T1R3 are translated and located correctly, we fusion the FLAG tag to N-terminal of T1R3. The reason fused tag to N-terminal is that the C-terminal of T1R3 interacts with the G protein α subunit, which is a crucial factor during signal deliver through G protein signal pathway. And the N-terminal is outside the cell, so it can be detected without killing it, using immunofluorescence can figure out whether T1R3 is located at the right position. </p>
+
<p> In order to show whether the sweet receptor T1R3 are translated and located correctly, we fusion the Flag tag to N-terminal of T1R3. The reason fused tag to N-terminal is that the C-terminal of T1R3 interacts with the G protein α subunit, which is a crucial factor during signal deliver through G protein signal pathway. And the N-terminal is outside the cell, so it can be detected without killing it, using immunofluorescence can figure out whether T1R3 is located at the right position. </p>
  
  
 
[[File:T-BIT-China-2017parts-46.png|center|500px|默认文字]]
 
[[File:T-BIT-China-2017parts-46.png|center|500px|默认文字]]
 
+
<p style="text-align: center"><span>Fig. 2 The schematic diagram of making T1R3-Flag</span></p>
 
<h1>Experiment</h1>
 
<h1>Experiment</h1>
<p> At the beginning, we construct the specific primer that consists of the gene sequence of FLAG tag. Then, fused T1R3 with the FLAG using PCR. The length of sequence is 50bp. </p>
+
<p> At the beginning, we construct the specific primer that consists of the gene sequence of Flag tag. Then, fused T1R3 with the Flag using PCR. The length of sequence is 50bp. </p>
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here
 
===Usage and Biology===
 
===Usage and Biology===
Line 22: Line 22:
 
<!-- -->
 
<!-- -->
 
<h2>Sequence and Features</h2>
 
<h2>Sequence and Features</h2>
<partinfo>BBa_K2368009 SequenceAndFeatures</partinfo>
+
<partinfo>BBa_K2368011 SequenceAndFeatures</partinfo>
  
  
 
<!-- Uncomment this to enable Functional Parameter display  
 
<!-- Uncomment this to enable Functional Parameter display  
 
===Functional Parameters===
 
===Functional Parameters===
<partinfo>BBa_K2368009 parameters</partinfo>
+
<partinfo>BBa_K2368011 parameters</partinfo>
 
<!-- -->
 
<!-- -->

Latest revision as of 16:00, 28 October 2017


Introduction

Flag+T1R3 overlap

This part sweetness receptor T1R3 fusion with the Flag tag, just like the picture showed below.

默认文字

Fig. 1 The schematic diagram of T1R3-Flag


Design

In order to show whether the sweet receptor T1R3 are translated and located correctly, we fusion the Flag tag to N-terminal of T1R3. The reason fused tag to N-terminal is that the C-terminal of T1R3 interacts with the G protein α subunit, which is a crucial factor during signal deliver through G protein signal pathway. And the N-terminal is outside the cell, so it can be detected without killing it, using immunofluorescence can figure out whether T1R3 is located at the right position.


默认文字

Fig. 2 The schematic diagram of making T1R3-Flag

Experiment

At the beginning, we construct the specific primer that consists of the gene sequence of Flag tag. Then, fused T1R3 with the Flag using PCR. The length of sequence is 50bp.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    COMPATIBLE WITH RFC[21]
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]