Team:HIT-Harbin/Wetlab
From 2014.igem.org
Line 4: | Line 4: | ||
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/style.css?action=raw&ctype=text/css"> | <link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/style.css?action=raw&ctype=text/css"> | ||
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/contentstyle.css?action=raw&ctype=text/css"> | <link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/contentstyle.css?action=raw&ctype=text/css"> | ||
+ | <link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/projectstyle.css?action=raw&ctype=text/css"> | ||
<script type="text/javascript" src="https://2014.igem.org/Team:HIT-Harbin/js/main.js?action=raw&ctype=text/javascript"></script> | <script type="text/javascript" src="https://2014.igem.org/Team:HIT-Harbin/js/main.js?action=raw&ctype=text/javascript"></script> | ||
<!--main content --> | <!--main content --> | ||
Line 12: | Line 13: | ||
<!--project --> | <!--project --> | ||
<div id="project" class="nav1" > | <div id="project" class="nav1" > | ||
- | <a href="https://2014.igem.org/Team:HIT-Harbin/Project" name="top">Project</a> | + | <a href="https://2014.igem.org/Team:HIT-Harbin/Project" name="top"><span>Project</span></a> |
<ul> | <ul> | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li> | ||
Line 24: | Line 25: | ||
</div> | </div> | ||
<!--Wetlab--> | <!--Wetlab--> | ||
- | <div id="wetlab" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab" | + | <div id="wetlab" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab">Wetlab</a> |
<ul> | <ul> | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Protocols">Protocols</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Protocols">Protocols</a></li> | ||
Line 39: | Line 40: | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li> | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li> | ||
- | <li><a href="https://igem.org/Team.cgi | + | <li><a href="https://igem.org/Team.cgi">Profile</a></li> |
</ul> | </ul> | ||
</div> | </div> | ||
Line 57: | Line 58: | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li> | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Design">Design</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Design">Design</a></li> | ||
- | <li><a href="https://2014.igem.org/Team:HIT-Harbin/ | + | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Advantages">Advantages</a></li> |
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Modeling">Modeling</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Modeling">Modeling</a></li> | ||
</ul> | </ul> | ||
Line 80: | Line 81: | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li> | ||
<li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li> | <li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li> | ||
- | <li><a href="https://igem.org/Team.cgi">Profile</a></li> | + | <li><a href="https://igem.org/Team.cgi" target="_blank">Profile</a></li> |
</ul> | </ul> | ||
</div> | </div> | ||
Line 92: | Line 93: | ||
</div> | </div> | ||
</div> | </div> | ||
- | |||
<!--mainarea--> | <!--mainarea--> | ||
<div id="mainarea"> | <div id="mainarea"> | ||
<div class="multi-columns"> | <div class="multi-columns"> | ||
- | |||
<div id="subtitle"> | <div id="subtitle"> | ||
<h5>Control Group</h5> | <h5>Control Group</h5> |
Revision as of 21:36, 17 October 2014
Control Group
So as to test the working state of promoter when there is no dioxin, we designed this control circuit showed above. We replaced mdr83-805 by mdr521-805. Its sequence of dioxin receptor was eliminated. When it is stimulated by galactose in the environment, the circuit will express the DNA binding sequence which is independent of dioxin. It is especially for testing whether mdr521-805 can trigger transmembrane transportation. What’s more, Its localization effect as well as zero correction function can be tested.
Experimental Group
In order to make yeast be capable of detecting dioxins in the environment, we designed the circuit above. TEF is the constitutive promoter which can activate downstream sequences to express dual domain protein, namely, lexA-DBD/mDR83-80. Comparing with other amplifiers, lexA can rapidly and efficiently induce the expression of downstream gene. At the meantime, we designed and applied the operator-lexop which possesses eight LEXAdbd binding sites, thus the catalytic effect of lexA operator is further improved. mDR83-805 can express mdr83-805(mouse dioxin receptor). And after it combining intracellular dissociative dioxin, it will pass through karyotheca and combine with lexA operator to switch up downstream promoters and then activate the expression of green fluorescent protein downstream. Then we can know by observation whether there is dioxin in the environment or not.
Considering the amount of dioxin in the environment is in micro level or even trace level, when the concentration of dioxin decreases, those who can successfully combine with fusion protein lexadbd/mdr83-805 and then nucleic DNA will be less. Thus, we added a memory system to amplify the signal intensity by positive feedback regulation.
When there is a trace of dioxin, with the assistance of native intercellular hsp90 and arnt, the combination of fusion protein lexadbd/mdr83-805 and dioxin will activate the expression of florescent protein. Lex-A-DBD/mDR521-805 depicted in the picture is also dual domain protein but without binding site of dioxin hence cannot combine with dioxin. However, it can still pass through the nuclear membrane and combine with DNA to activate the expression of GFP. Such signal of the trace of dioxin can lead to the expression of a lot of GFP by amplification.