Difference between revisions of "Part:BBa K2333439"
| Line 13: | Line 13: | ||
<html><img src="https://static.igem.org/mediawiki/2017/d/da/T--William_and_Mary--Copper_Normalized_V1.png" width="600px"/></html> | <html><img src="https://static.igem.org/mediawiki/2017/d/da/T--William_and_Mary--Copper_Normalized_V1.png" width="600px"/></html> | ||
| + | <html><img src="https://static.igem.org/mediawiki/parts/b/b3/T--William_and_Mary--Copper_Timecourse.png" width="650px"/></html> | ||
| + | |||
Time course measurements were performed according to standard protocol, and copper sensor parts were transformed on 1C3 along with <partinfo>K2333434</partinfo> on 3K3, and induced with 500μM copper sulfate and .01mM IPTG. In addition to requiring less IPTG than W&M 2017's other parts, copper parts worked well at 500μM CuSO4 but experienced die offs at 1000μM. Fluorescence was normalized to steady state based upon when fluorescence no longer increased. As the no-Lon condition had not reached steady state when time course was ended, it was normalized to the final collected data point, which is likely close to the true steady state. | Time course measurements were performed according to standard protocol, and copper sensor parts were transformed on 1C3 along with <partinfo>K2333434</partinfo> on 3K3, and induced with 500μM copper sulfate and .01mM IPTG. In addition to requiring less IPTG than W&M 2017's other parts, copper parts worked well at 500μM CuSO4 but experienced die offs at 1000μM. Fluorescence was normalized to steady state based upon when fluorescence no longer increased. As the no-Lon condition had not reached steady state when time course was ended, it was normalized to the final collected data point, which is likely close to the true steady state. | ||
Revision as of 06:01, 1 November 2017
Copper sensor with Protein Degradation Tag C
This part constitutively expresses the CueR repressor. This repressor then inhibits the expression of protein degradation tagged (pdt-C) RFP from the downstream PcopA promoter. In the presence of copper, the repression of CueR is inhibited leading to greater RFP expression. Characterized by UMaryland 2017, fluorescence of this construct has been shown to increase with increasing copper concentration in both a qualitative and quantitative manner.
Usage and Biology
This part contains the CueR repressor under the constitutive promoter BBa_J23102 combined with pdt-C tagged RFP under the control of the PcopA promoter. Protein degradation tag C is the third strongest of the 6 protein degradation tags that William and Mary 2017 characterized, and is associated with the E. Coli orthogonal protease mf-Lon (BBa_K2333011). Therefore, this part is the third fastest of 6 pdt's to reach the steady-state fluorescence value. This part is contained in a suite of parts that allowed William and Mary 2017 to demonstrate persistence of speed-change effects for protein outputs beyond simple reporter proteins, and provides an example of a practical application of their speed-control system to improve biosensor output speed.
Characterization
W&M 2017 characterized this tag's degradation rate and speed change effects as part of their iGEM project. The graphs below show the speed data of this pdt tagged copper sensor part along with the data from the other tags in this series (BBa_K2333437-BBa_K2333442).
Time course measurements were performed according to standard protocol, and copper sensor parts were transformed on 1C3 along with BBa_K2333434 on 3K3, and induced with 500μM copper sulfate and .01mM IPTG. In addition to requiring less IPTG than W&M 2017's other parts, copper parts worked well at 500μM CuSO4 but experienced die offs at 1000μM. Fluorescence was normalized to steady state based upon when fluorescence no longer increased. As the no-Lon condition had not reached steady state when time course was ended, it was normalized to the final collected data point, which is likely close to the true steady state.
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12INCOMPATIBLE WITH RFC[12]Illegal NheI site found at 7
Illegal NheI site found at 30 - 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal AgeI site found at 1229
Illegal AgeI site found at 1341 - 1000COMPATIBLE WITH RFC[1000]