Team:Chiba/System 1/Testing components
From 2010.igem.org
(→2. Pulse to GFP generator) |
|||
(40 intermediate revisions not shown) | |||
Line 18: | Line 18: | ||
border: 0; | border: 0; | ||
} | } | ||
+ | p{margin:20px 10px 10px;} | ||
</style> | </style> | ||
</html> | </html> | ||
Line 30: | Line 31: | ||
</form> | </form> | ||
</div> <!-- close search controls --> | </div> <!-- close search controls --> | ||
- | |||
- | |||
<body bgcolor="blue" text="black" link="yellow" vlink="purple" alink="red" background="https://static.igem.org/mediawiki/2010/a/a1/Chiba_ground_2.jpg"> | <body bgcolor="blue" text="black" link="yellow" vlink="purple" alink="red" background="https://static.igem.org/mediawiki/2010/a/a1/Chiba_ground_2.jpg"> | ||
<img src="https://static.igem.org/mediawiki/2010/f/f9/Chiba_menu_2.jpg"> | <img src="https://static.igem.org/mediawiki/2010/f/f9/Chiba_menu_2.jpg"> | ||
- | |||
<style type="text/css"> | <style type="text/css"> | ||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> | ||
Line 52: | Line 50: | ||
font: bold 14px Verdana, Arial, Helvetica, sans-serif; | font: bold 14px Verdana, Arial, Helvetica, sans-serif; | ||
color: #000; | color: #000; | ||
- | margin: | + | margin-top: 10px; |
- | padding: | + | padding-left: 10px; |
} | } | ||
+ | |||
+ | h3{ font:bold 13px Verdana; | ||
+ | padding-left: 15px;} | ||
+ | } | ||
+ | |||
+ | h4{padding-left:15px;} | ||
img { | img { | ||
Line 130: | Line 134: | ||
<li><a href="https://2010.igem.org/Team:Chiba/Support"><span>Support</span></a></li> | <li><a href="https://2010.igem.org/Team:Chiba/Support"><span>Support</span></a></li> | ||
<li id="current"><a href="https://2010.igem.org/Team:Chiba/Safety"><span>Safety</span></a></li> | <li id="current"><a href="https://2010.igem.org/Team:Chiba/Safety"><span>Safety</span></a></li> | ||
- | |||
</ul> | </ul> | ||
</div> | </div> | ||
Line 160: | Line 163: | ||
font: bold 14px Verdana, Arial, Helvetica, sans-serif; | font: bold 14px Verdana, Arial, Helvetica, sans-serif; | ||
color: #000; | color: #000; | ||
- | margin: | + | margin-top: 10px; |
- | padding: | + | padding-left: 15px; |
+ | } | ||
+ | |||
+ | h3{ font:bold 13px Verdana; | ||
+ | padding-left: 20px;} | ||
+ | |||
} | } | ||
Line 180: | Line 188: | ||
#tabs9 ul { | #tabs9 ul { | ||
margin:0; | margin:0; | ||
- | padding:2px 10px 0 | + | padding:2px 10px 0 105px; |
list-style:none; | list-style:none; | ||
} | } | ||
Line 231: | Line 239: | ||
<ul> | <ul> | ||
<!-- CSS Tabs --> | <!-- CSS Tabs --> | ||
- | <li><a href="https://2010.igem.org/Team:Chiba/Project"><span> | + | <li><a href="https://2010.igem.org/Team:Chiba/Project"><span>Double Click System</span></a></li> |
- | <li><a href="https://2010.igem.org/Team:Chiba/System_1"><span> | + | <li><a href="https://2010.igem.org/Team:Chiba/System_1"><span>Version 1</span></a></li> |
- | <li><a href="https://2010.igem.org/Team:Chiba/System_2"><span> | + | <li><a href="https://2010.igem.org/Team:Chiba/System_2"><span>Version 2</span></a></li> </ul> |
</div> | </div> | ||
</body> | </body> | ||
+ | </html> | ||
<!--- 2nd tab End---> | <!--- 2nd tab End---> | ||
- | <!--- | + | <!--- Background Contents End ---> |
- | < | + | <!-- ------------------------------------------------------------------------------- |
- | + | ------------------------------------------------------------------------------- | |
- | + | ここから下を編集 | |
- | + | ------------------------------------------------------------------------------- | |
- | + | ----------------------------------------------------------------------------------- --> | |
- | + | __NOTOC__ | |
- | + | <br><br> | |
- | + | [[Team:Chiba/System 1|<<Back]] | |
- | < | + | <br><br> |
- | < | + | <font size=5>Version 1 :Testing individual parts</font> |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | < | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | To realize the genetic double click system, we made two plasmids. First one is ''Pulse generator'', which generate the pulse of T7 RNAP in response to the 1st and 2nd input. The second one is ''pulse -> GFP generator'', which generates the output (GFP expression) on condition that T7 RNAP activates the GFP upstream promoter and also CI protein does not repress that promoter. | |
- | + | The subparts of those plasmids are shown below.<br> | |
- | + | <center> | |
- | + | [[Image:Chiba_icon_1.jpg]]<br> | |
- | + | [[Image:Chiba_icon_2.jpg]]<br> | |
- | + | </center> | |
+ | Regarding with those two plasmids, we tested the function of each parts in the plasmids.<br> | ||
- | + | ==1. Pulse generator== | |
- | + | For Pulse generator, the parts shown below were checked.Also, we checked if there were no crosstalk between CI/CI434 and CI promoter/CI434 promoter. | |
- | + | ||
- | /*- | + | ===T7/CI-OR1 hybrid promoter=== |
+ | *[http://partsregistry.org/wiki/index.php?title=Part:BBa_K396000 BBa_K396000] | ||
+ | T7/CI-OR1 hybrid promoter was designed to be activated by T7 RNA Polymerase and repressed by lambda CI protein. In sequence design, lambda CI operator site 1 (OR1, Part of BBa_R1051) was directly attached to the downstream of T7 promoter sequence (BBa_I719005). This characterization was implemented to validate the promoter function. In results, the activation and repression was actually observed. | ||
+ | ====Experiment&Results==== | ||
+ | [[Image:CI-1.jpg|frame|center|Fig. How to check the parts]] | ||
+ | [[Image:CI-2.jpg|frame|center|Fig. Data: Under the situation of CI non-expressed , T7 RNAP causes GFP expression by activating T7/CI hybrid promoter (Fig.1). On the other hand, under the situation of CI expressed, T7 RNAP does not cause GFP expression (Fig.2). The reason of this is considered as following. Under the situation of CI expressed, even though T7 RNAP tries to activate T7/CI promoter, the promoter Is repressed by CI because the ability of CI repression is superior to the one of T7 activation for this promoter. So it is concluded that T7/CI hybrid promoter is to be activated by T7 RNA Polymerase and repressed by lambda CI protein, following the rules of CI repression > T7 activation.]] | ||
+ | *Dubendorf, J.W. & Studier, F.W. Controlling basal expression in an inducible T7 expression system by blocking the target T7 promoter with lac repressor. Journal of Molecular Biology 219, 45-59 (1991). | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | + | ==2. Pulse to GFP generator== | |
- | + | For GFP generator, the parts shown below were checked. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ===Lux/CI434 hybrid promoter=== | |
- | + | We got the idea that cI and cI434 repressor don’t crosstalk[1], so we construct Pt7/cI and pLux/cI434 hybrid promoter. | |
- | + | ====Rationale==== | |
- | + | [[image:Hybrid.png]] | |
- | + | <br> | |
- | + | This hybrid promoter is designed to activated by LuxR when it is bound to AHL and repressed by the phage 434 cI repressor. The operator site sequence come from the biobrick part (BBa_R0052) and we set OR2(ttacaatgtatcttg) between -35 and -10, OR1(ttacaaactttcttg) at downstream of -10. There are only 16 bp between the -10 and -35 boxes we have confirmed that lux promoter works naturally while repression is under observation. | |
- | + | ||
- | + | ====Characterization of lux/CI434-OR1&OR2 hybrid promoter(BBa_K396001)==== | |
- | + | lux/CI434-OR1&OR2 hybrid promoter was designed to be activated by LuxR-AHL dimmer and repressed by 434 phage CI434 protein. This part was experimented whether GFP downstream of the hybrid was induced by AHL. Promoter. | |
- | + | [[Image:그림1.png|600px|thumb|center|alt text]] | |
- | + | <br> | |
- | + | [[Image:그림2.png|600px|thumb|center|alt text]] | |
- | + | <br> | |
- | + | [[Image:그림3.png|600px|thumb|center|alt text]] | |
- | + | ====Ref==== | |
- | + | #http://web.mit.edu/synbio/x/htdocs/BB_Parts/BBa_R0050/Part.htm | |
- | + | #http://partsregistry.org/Part:BBa_I12040 | |
- | + | #Basu S, Mehreja R, Thiberge S, Chen MT and Weiss R (2004). Spatiotemporal control of gene expression with pulse-generating networks. Proc Natl Acad Sci USA 101: 6355-6360. | |
- | + | ||
- | + |
Latest revision as of 03:57, 28 October 2010
<<Back
Version 1 :Testing individual parts
To realize the genetic double click system, we made two plasmids. First one is Pulse generator, which generate the pulse of T7 RNAP in response to the 1st and 2nd input. The second one is pulse -> GFP generator, which generates the output (GFP expression) on condition that T7 RNAP activates the GFP upstream promoter and also CI protein does not repress that promoter.
The subparts of those plasmids are shown below.
Regarding with those two plasmids, we tested the function of each parts in the plasmids.
1. Pulse generator
For Pulse generator, the parts shown below were checked.Also, we checked if there were no crosstalk between CI/CI434 and CI promoter/CI434 promoter.
T7/CI-OR1 hybrid promoter
- [http://partsregistry.org/wiki/index.php?title=Part:BBa_K396000 BBa_K396000]
T7/CI-OR1 hybrid promoter was designed to be activated by T7 RNA Polymerase and repressed by lambda CI protein. In sequence design, lambda CI operator site 1 (OR1, Part of BBa_R1051) was directly attached to the downstream of T7 promoter sequence (BBa_I719005). This characterization was implemented to validate the promoter function. In results, the activation and repression was actually observed.
Experiment&Results
- Dubendorf, J.W. & Studier, F.W. Controlling basal expression in an inducible T7 expression system by blocking the target T7 promoter with lac repressor. Journal of Molecular Biology 219, 45-59 (1991).
2. Pulse to GFP generator
For GFP generator, the parts shown below were checked.
Lux/CI434 hybrid promoter
We got the idea that cI and cI434 repressor don’t crosstalk[1], so we construct Pt7/cI and pLux/cI434 hybrid promoter.
Rationale
This hybrid promoter is designed to activated by LuxR when it is bound to AHL and repressed by the phage 434 cI repressor. The operator site sequence come from the biobrick part (BBa_R0052) and we set OR2(ttacaatgtatcttg) between -35 and -10, OR1(ttacaaactttcttg) at downstream of -10. There are only 16 bp between the -10 and -35 boxes we have confirmed that lux promoter works naturally while repression is under observation.
Characterization of lux/CI434-OR1&OR2 hybrid promoter(BBa_K396001)
lux/CI434-OR1&OR2 hybrid promoter was designed to be activated by LuxR-AHL dimmer and repressed by 434 phage CI434 protein. This part was experimented whether GFP downstream of the hybrid was induced by AHL. Promoter.
Ref
- http://web.mit.edu/synbio/x/htdocs/BB_Parts/BBa_R0050/Part.htm
- http://partsregistry.org/Part:BBa_I12040
- Basu S, Mehreja R, Thiberge S, Chen MT and Weiss R (2004). Spatiotemporal control of gene expression with pulse-generating networks. Proc Natl Acad Sci USA 101: 6355-6360.