Difference between revisions of "Part:BBa K2996602"
Line 11: Line 11:
 
<span class='h3bb'>Sequence and Features</span>
 
<span class='h3bb'>Sequence and Features</span>
 
<partinfo>BBa_K2996602 SequenceAndFeatures</partinfo>
 
<partinfo>BBa_K2996602 SequenceAndFeatures</partinfo>
−
<img style="max-width: 50%" src="https://static.igem.org/mediawiki/2018/5/5d/T--TUDelft--2018_Figure1_colonyPCR_linkerTn5_Fusion.png" alt="">
+
<center>{{#tag:html|<img style="max-width: 50%" src="https://static.igem.org/mediawiki/2018/5/5d/T--TUDelft--2018_Figure1_colonyPCR_linkerTn5_Fusion.png" alt="" />}}</center><img style="max-width: 50%" src="https://static.igem.org/mediawiki/2018/5/5d/T--TUDelft--2018_Figure1_colonyPCR_linkerTn5_Fusion.png" alt="">
  
 
<!-- Uncomment this to enable Functional Parameter display  
 
<!-- Uncomment this to enable Functional Parameter display  

Revision as of 04:05, 7 October 2019


scar between RSRL and EGFP

After constructing pGEX4t-EGFP, we gave it to company to synthesize our desired RSRL sequence. Since the fragment can only be put between restrcition sites, there is a scar left between RSRL and EGFP. Actually, it is the restrcition site for BamHⅠ.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BamHI site found at 1
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]
<img style="max-width: 50%" src="T--TUDelft--2018_Figure1_colonyPCR_linkerTn5_Fusion.png" alt="">