Difference between revisions of "Part:BBa K5301006"
Estrella0910 (Talk | contribs) (→Induction) |
Estrella0910 (Talk | contribs) (→Purification) |
||
Line 20: | Line 20: | ||
After confirming the successful expression of SnCSdT, we scaled up the culture and purified the protein. During plasmid construction, we incorporated a His-tag into the sequence, allowing for purification using nickel affinity chromatography, which specifically binds to His-tagged proteins. We eluted the protein using 300mM and 500mM imidazole, respectively, and obtained a large amount of target protein in both cases, as shown in figure 2. | After confirming the successful expression of SnCSdT, we scaled up the culture and purified the protein. During plasmid construction, we incorporated a His-tag into the sequence, allowing for purification using nickel affinity chromatography, which specifically binds to His-tagged proteins. We eluted the protein using 300mM and 500mM imidazole, respectively, and obtained a large amount of target protein in both cases, as shown in figure 2. | ||
<div class="center"><div class="thumb tnone"><div class="thumbinner" style="width:min-content;"><div style="zoom:0.4;overflow:hidden;"> | <div class="center"><div class="thumb tnone"><div class="thumbinner" style="width:min-content;"><div style="zoom:0.4;overflow:hidden;"> | ||
− | https://static.igem.wiki/teams/5301/parts/tri- | + | https://static.igem.wiki/teams/5301/parts/tri-2-purification.png |
</div><div class="thumbcaption"> | </div><div class="thumbcaption"> | ||
Figure 2.SDS-PAGE Analysis of SnCSdT Purified by Nickel Affinity Chromatography. Both 300mM and 500mM imidazole elution resulted in the acquisition of a significant amount of target protein. The molecular weight of SnCSdT is 42.1 kDa. | Figure 2.SDS-PAGE Analysis of SnCSdT Purified by Nickel Affinity Chromatography. Both 300mM and 500mM imidazole elution resulted in the acquisition of a significant amount of target protein. The molecular weight of SnCSdT is 42.1 kDa. |
Revision as of 03:34, 1 October 2024
SnCSdT is one of the components of multi-polymerized MSP.
Usage and Biology
In order to produce large nanodiscs more conveniently, we hope to flexibly extend the length of MSP according to demand, and thus propose the concept of multi-polymer MSP, which refers to large circular MSPs through end-to-end connections of multiple MSP fragments. We used NW15 as the basic MSP and selected three types of linkers (Spy/Sdy/Snoop) to achieve the connection of different MSP fragments through the formation of covalent bonds, and adopted rigorous design to prevent self-cyclization of each fragment of the multi-polymer MSP. Finally, the successful cyclization of large circular MSPs is characterized by the fluorescence of mCherry after the combination of mCherry [1-10] and mCherry [11]. SnCSdT, the second component of multi-polymerized MSP, is a fusion protein composed of SnoopCatcher, NW15, and SdyTag, with flexible GS linkers used to connect each part.
Cultivation, Purification and SDS-PAGE
Induction
We chose the T7 expression system as the pathway for protein expression and induced protein expression by adding IPTG at an appropriate time. Through experimental validation, we added the IPTG solution at a concentration of 0.8mM when the OD value of the bacterial suspension reached 0.6-0.8, resulting in substantial expression of soluble proteins.
Purification
After confirming the successful expression of SnCSdT, we scaled up the culture and purified the protein. During plasmid construction, we incorporated a His-tag into the sequence, allowing for purification using nickel affinity chromatography, which specifically binds to His-tagged proteins. We eluted the protein using 300mM and 500mM imidazole, respectively, and obtained a large amount of target protein in both cases, as shown in figure 2.
Structure and biological activity analysis
Sequence and Features
- 10INCOMPATIBLE WITH RFC[10]Illegal PstI site found at 1021
- 12INCOMPATIBLE WITH RFC[12]Illegal PstI site found at 1021
- 21INCOMPATIBLE WITH RFC[21]Illegal BglII site found at 203
Illegal BglII site found at 575 - 23INCOMPATIBLE WITH RFC[23]Illegal PstI site found at 1021
- 25INCOMPATIBLE WITH RFC[25]Illegal PstI site found at 1021
Illegal AgeI site found at 100
Illegal AgeI site found at 860 - 1000COMPATIBLE WITH RFC[1000]