Difference between revisions of "Part:BBa K4144010"
RoyMustang (Talk | contribs) (→Usage and Biology) |
|||
Line 9: | Line 9: | ||
<html> | <html> | ||
<div class="col-lg" style="margin:auto;text-align:center;"> | <div class="col-lg" style="margin:auto;text-align:center;"> | ||
− | <img style="margin:20px auto 5px auto;" src="https://static.igem.wiki/teams/4144/wiki/same-part/bba-k414410/ | + | <img style="margin:20px auto 5px auto;" src="https://static.igem.wiki/teams/4144/wiki/same-part/bba-k414410/21cc148f07e497443664d7cb8066de8c.jpg |
" width="80%"> | " width="80%"> | ||
<p style="color:Gray; padding:0px 30px 10px;">Figure. 1 Linker addition design into opPet8p::sfGFP recombined protein</p> | <p style="color:Gray; padding:0px 30px 10px;">Figure. 1 Linker addition design into opPet8p::sfGFP recombined protein</p> |
Revision as of 20:24, 11 October 2022
Improved recombined SAMe transporter opPet8p fused with linker
Usage and Biology
Linkers can be classified into three groups: flexible, rigid and cleavable. Flexible linkers are generally composed of small, non-polar or polar residues such as Gly, Ser and Thr. The most common is the (Gly4Ser)n linker (Gly–Gly–Gly–Gly–Ser)n, where n indicates the number of repeats of the motif. Polyglycine linkers have also been evaluated, but the addition of a polar residue such as serine can reduce linker–protein interactions and preserve protein function. Due to their flexibility, these linkers are unstructured and thus provided limited domain separation in a previous study.
We WHU-China plan to use such linker to contact opPet8p and sfGFP in order to avoid the opPet8p membrane localization disruption by adding a sfGFP tag.
Figure. 1 Linker addition design into opPet8p::sfGFP recombined protein
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12INCOMPATIBLE WITH RFC[12]Illegal NheI site found at 520
- 21INCOMPATIBLE WITH RFC[21]Illegal BglII site found at 390
Illegal BamHI site found at 1018 - 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal AgeI site found at 1642
- 1000COMPATIBLE WITH RFC[1000]