Team:RHIT/Parts

From 2012.igem.org

(Difference between revisions)
 
(14 intermediate revisions not shown)
Line 20: Line 20:
<div class="rhit-content">
<div class="rhit-content">
<div class="rhit-header">
<div class="rhit-header">
-
<img src="/wiki/images/f/f2/Rhit-banner.png" width="100%"/>
+
<a href="https://2012.igem.org/Team:RHIT"><img src="https://static.igem.org/mediawiki/igem.org/8/87/Banner_only2.png" width="100%"/></a>
<div id="logged_out">
<div id="logged_out">
 +
<a href="https://2012.igem.org/Main_Page">iGEM Home</a>
<a href="https://2012.igem.org/wiki/index.php?title=Special:UserLogin&returnto=2012.igem.org/Team:RHIT">Login</a>
<a href="https://2012.igem.org/wiki/index.php?title=Special:UserLogin&returnto=2012.igem.org/Team:RHIT">Login</a>
</div>
</div>
-
                                <div id="logged_in">
+
<div id="logged_in">
-
                                        <a id='user-link' class='RHIT-external' href='#'></a>&nbsp;
+
<a href="https://2012.igem.org/Main_Page">iGEM Home</a>
-
                                        <a id='account-link' class='RHIT-external' href='https://igem.org/User_Information'>My Account</a>&nbsp;
+
<a id='user-link' class='RHIT-external' href='#'></a>&nbsp;
-
                                        <a id='logout-link' class='RHIT-external' href='https://2012.igem.org/wiki/index.php?title=Special:UserLogout&returnto=2012.igem.org/Team:RHIT'>Log Out</a>
+
<a id='account-link' class='RHIT-external' href='https://igem.org/User_Information'>My Account</a>&nbsp;
-
                                </div>
+
<a id='logout-link' class='RHIT-external' href='https://2012.igem.org/wiki/index.php?title=Special:UserLogout&returnto=2012.igem.org/Team:RHIT'>Log Out</a>
 +
</div>
</div>
</div>
-
<div class="rhit-nav">
+
<div class="rhit-navLeft">
<a href="/Team:RHIT">Home</a>
<a href="/Team:RHIT">Home</a>
 +
</div>
 +
<div class="rhit-nav">
<a href="/Team:RHIT/Current_Team">Team</a>
<a href="/Team:RHIT/Current_Team">Team</a>
 +
</div>
 +
<div class="rhit-nav">
<a href="/Team:RHIT/Project">Project</a>
<a href="/Team:RHIT/Project">Project</a>
 +
</div>
 +
<div class="rhit-navRed">
<a href="/Team:RHIT/Parts">BioBricks</a>
<a href="/Team:RHIT/Parts">BioBricks</a>
 +
</div>
 +
<div class="rhit-nav">
<a href="/Team:RHIT/Modeling">Modeling</a>
<a href="/Team:RHIT/Modeling">Modeling</a>
 +
</div>
 +
<div class="rhit-nav">
<a href="/Team:RHIT/Notebook">Notebook</a>
<a href="/Team:RHIT/Notebook">Notebook</a>
-
<a href="/Team:RHIT/Sponsors">Sponsors</a>
 
</div>
</div>
-
<div class="rhit-partsBox">
+
<div class="rhit-navRight">
-
+
<a href="/Team:RHIT/Outreach">Outreach</a>
 +
</div>
 +
<div class="rhit-genericBox">
 +
<p>The RHIT iGEM team’s BioBrick uses several pre-existing parts; a <a href="http://partsregistry.org/wiki/index.php/Part:BBa_K592100">fluorescent domain</a>, the <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_J176013">VP64 activator domain</a>, and the combination part of the <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K165018">nuclear localization sequence and terminator</a>. The remaining sequences used were the <a href="http://www.yeastgenome.org/cgi-bin/getSeq?map=amap&chr=3&beg=71603&end=71803&rev=">Fus1 promoter with Ste12 binding sites</a>, <a href="http://mic.sgmjournals.org/content/150/11/3783.full">LexA binding sites</a>, and the <a href="http://heptamer.tamu.edu/cgi-bin/gb2/gbrowse_details/BW2952?ref=NC_012759;start=4193983;end=4194591;name=lexA;class=Sequence;feature_id=7826;db_id=main%3Adatabase">LexA binding domain</a>.</p><br /><br />
 +
<p>The Ste12 binding sequences appear at 188, 176, and 160 base pairs before the start codon; they are 8, 6, and 7 base pairs long, respectively. Several LexA binding sites were added to the Fus1 promoter sequence at 140, 103, and 90 base pairs before the start codon; they are each nine base pairs long. This was done to allow the promoter to respond to two different signals, the Fus1 transcription factor and the LexA/VP64 transcription factor. LexA is a commonly used DNA-binding domain. The VP64 domain is a viral activator protein; it does not bind to DNA, but if it is fused to something that does, it will recruit the transcriptional apparatus. When LexA is fused to the VP64 protein, they form a potent transcriptional activator.</p><br /><br />
 +
<p>Since the promoter sequence came from a pre-existing gene, there was no need to add a ribosome binding site or transcriptional start site. Therefore, following the Fus1 promoter was the blue fluorescent domain, followed by a short Gly-Ser linker (GGTTCTGGTTCTGGTTCTGGTTCTGGTTCTGGTTCT), another fluorescent domain, and then the linker again. This simply makes the heteroprotein easier to detect, as it will have more fluorescence. Following this was the LexA binding domain. Connecting the LexA binding domain to the VP64 activator domain was the following linker: GCTTCTCCAAAAAAAAAAAGAAAAGTTGGTAGAGCTCT. At the end of our sequence, after the VP64 activator domain, the combination nuclear localization sequence/terminator was added.</p><br /><br />
 +
<p>Overall, the part was designed to be a DNA sequence that would respond to an initial signal with the production of a heteroprotein. This heteroprotein would serve two functions; it is a reporter protein via fluorescence, and it is capable of upregulating its own production. The LexA binding sites in the promoter allow the LexA and VP64 domains in the heteroprotein to initiate more transcription of the heteroprotein via a positive feedback loop, thus creating the possibility for a non-transient signal.</p><br /><br />
 +
<h4>Proposed Parts</h4>
 +
<p>Due to time constraints in receiving our DNA order, we were not able to submit a part on time. However, if we had been able to, we would have submitted the <a href="https://static.igem.org/mediawiki/igem.org/2/2d/Dual-function_promoter.txt">dual-function promoter</a> (binding sequences as detailed above) and the heteroprotein coding sequence. The entire marked-up sequence for our construct can be found <a href="https://static.igem.org/mediawiki/igem.org/6/62/Putative_Blue_Fusion_2b_%282761bps%29.pdf">here</a>.</p>
</div>
</div>
</div>
</div>
</body>
</body>
</html>
</html>

Latest revision as of 03:54, 4 October 2012

Home
Team
Project
BioBricks
Modeling
Notebook
Outreach

The RHIT iGEM team’s BioBrick uses several pre-existing parts; a fluorescent domain, the VP64 activator domain, and the combination part of the nuclear localization sequence and terminator. The remaining sequences used were the Fus1 promoter with Ste12 binding sites, LexA binding sites, and the LexA binding domain.



The Ste12 binding sequences appear at 188, 176, and 160 base pairs before the start codon; they are 8, 6, and 7 base pairs long, respectively. Several LexA binding sites were added to the Fus1 promoter sequence at 140, 103, and 90 base pairs before the start codon; they are each nine base pairs long. This was done to allow the promoter to respond to two different signals, the Fus1 transcription factor and the LexA/VP64 transcription factor. LexA is a commonly used DNA-binding domain. The VP64 domain is a viral activator protein; it does not bind to DNA, but if it is fused to something that does, it will recruit the transcriptional apparatus. When LexA is fused to the VP64 protein, they form a potent transcriptional activator.



Since the promoter sequence came from a pre-existing gene, there was no need to add a ribosome binding site or transcriptional start site. Therefore, following the Fus1 promoter was the blue fluorescent domain, followed by a short Gly-Ser linker (GGTTCTGGTTCTGGTTCTGGTTCTGGTTCTGGTTCT), another fluorescent domain, and then the linker again. This simply makes the heteroprotein easier to detect, as it will have more fluorescence. Following this was the LexA binding domain. Connecting the LexA binding domain to the VP64 activator domain was the following linker: GCTTCTCCAAAAAAAAAAAGAAAAGTTGGTAGAGCTCT. At the end of our sequence, after the VP64 activator domain, the combination nuclear localization sequence/terminator was added.



Overall, the part was designed to be a DNA sequence that would respond to an initial signal with the production of a heteroprotein. This heteroprotein would serve two functions; it is a reporter protein via fluorescence, and it is capable of upregulating its own production. The LexA binding sites in the promoter allow the LexA and VP64 domains in the heteroprotein to initiate more transcription of the heteroprotein via a positive feedback loop, thus creating the possibility for a non-transient signal.



Proposed Parts

Due to time constraints in receiving our DNA order, we were not able to submit a part on time. However, if we had been able to, we would have submitted the dual-function promoter (binding sequences as detailed above) and the heteroprotein coding sequence. The entire marked-up sequence for our construct can be found here.

Retrieved from "http://2012.igem.org/Team:RHIT/Parts"