Difference between revisions of "Part:BBa K2996602"
Line 12: | Line 12: | ||
<partinfo>BBa_K2996602 SequenceAndFeatures</partinfo> | <partinfo>BBa_K2996602 SequenceAndFeatures</partinfo> | ||
<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> | <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> | ||
− | <center><b>Figure 1.</b> <i>33333.</i> 4567876543</center> | + | <center> |
+ | <b>Figure 1.</b> <i>33333.</i> 4567876543</center> | ||
<!-- Uncomment this to enable Functional Parameter display | <!-- Uncomment this to enable Functional Parameter display |
Revision as of 10:43, 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:
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21INCOMPATIBLE WITH RFC[21]Illegal BamHI site found at 1
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000COMPATIBLE WITH RFC[1000]