Team:Berkeley/Parts

From 2011.igem.org

(Difference between revisions)
(Prototype team page)
 
(81 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
{{Team:Berkeley/header}}
-
 
+
{{Team:Berkeley/navigation}}
 +
{{Team:Berkeley/css}}
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
<div id="top-section3"><center><img src="https://static.igem.org/mediawiki/2011/4/48/NavigationBar_Berkeley.jpg" alt="header" border="0"  usemap="#igemmap"></center></div>
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
 
-
This is a template page. READ THESE INSTRUCTIONS.
+
 
 +
<map name="igemmap">
 +
  <area  shape="circle" coords="480,40,40" alt="Mercury" href="https://2011.igem.org" onfocus="this.blur()" />
 +
</map>
 +
 
 +
<div class= "layout-1000" >
 +
 
 +
 
 +
 
 +
<div class="row">
 +
<div class="col12" >
 +
<ul class="topnav">
 +
    <li><a href="https://2011.igem.org/Team:Berkeley">Home</a></li>
 +
    <li>
 +
        <a href="https://2011.igem.org/Team:Berkeley/Project">Project</a>
 +
    </li>
 +
    <li>
 +
        <a href="https://2011.igem.org/Team:Berkeley/Parts">Parts</a>
 +
    </li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Safety">Safety</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Team">Team</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Judging">Judging</a></li>
 +
    <li><a href="https://2011.igem.org/Team:Berkeley/Notebooks">Notebooks</a></li>
 +
</ul>
 +
<div> <div class ="row-end"> </div>
</div>
</div>
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
 
-
You are provided with this team page template with which to start the iGEM season.  You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
 
</div>
</div>
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
 
-
You <strong>MUST</strong> have a team description page, a project abstract, a complete project description, a lab notebook, and a safety page.  PLEASE keep all of your pages within your teams namespace. 
+
<div class="row">
 +
<div class="col12" id="spacer2"></div>
 +
<div class="row-end"> </div>
</div>
</div>
 +
 +
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/b/b2/Partsbanner-berkeley.jpg" width="980"> </div>
 +
<div class="row-end" ></div>
</div>
</div>
-
</html>
 
-
<!-- *** End of the alert box *** -->
+
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/0/09/SummaryPartsHeader.jpg" width="980"> </div> </div>
 +
<div class="row-end" ></div>
-
{|align="justify"
+
<div class="row">
-
|You can write a background of your team here. Give us a background of your team, the members, etc.  Or tell us more about something of your choosing.
+
  <div class="col12-3">
-
|[[Image:Berkeley_logo.png|200px|right|frame]]
+
-
|-
+
-
|
+
-
''Tell us more about your project.  Give us background.  Use this is the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:Berkeley_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:Berkeley | Team Example]]
+
-
|}
+
-
<!--- The Mission, Experiments --->
+
<b># of parts submitted:</b>
 +
<ul>
 +
<li>35 Regulatory promoters</li>
 +
<li>2 Ribosome Binding Sites</li>
 +
<li>2 Composite expression modules</li>
 +
<li>2 Coding proteins</li>
 +
</ul>
 +
<b>Total:</b> 42 Parts <br> <br>
 +
<b>Assembly Method:</b> BglBricks <br><br>
 +
<b>Accomplishments:</b> <br>
 +
<ul>
 +
<li>All 42 parts have been submitted to the registry and can be found <a href="http://partsregistry.org/cgi/partsdb/pgroup.cgi?pgroup=iGEM2011&group=Berkeley">HERE</a></li>
 +
<li>We submitted two new well-characterized BioBrick Parts in vector pSB1AC3 according to RFC10</li>
 +
<li>Compiled a set of 35 stress promoters that future iGEMers can utilize as regulatory elements</li>
 +
</ul>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
 
-
!align="center"|[[Team:Berkeley|Home]]
 
-
!align="center"|[[Team:Berkeley/Team|Team]]
 
-
!align="center"|[https://igem.org/Team.cgi?year=2010&team_name=Berkeley Official Team Profile]
 
-
!align="center"|[[Team:Berkeley/Project|Project]]
 
-
!align="center"|[[Team:Berkeley/Parts|Parts Submitted to the Registry]]
 
-
!align="center"|[[Team:Berkeley/Modeling|Modeling]]
 
-
!align="center"|[[Team:Berkeley/Notebook|Notebook]]
 
-
!align="center"|[[Team:Berkeley/Safety|Safety]]
 
-
!align="center"|[[Team:Berkeley/Attributions|Attributions]]
 
-
|}
 
 +
<br>
 +
</div>
 +
<div class="row-end" ></div>
 +
</div>
-
===Parts===
+
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
-
New for iGEM 2010 is the ''groupparts'' tag.  This tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
+
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/f/fb/PartssubHeader2.jpg" width="980"> </div> </div>
 +
<div class="row-end" ></div>
-
<groupparts>iGEM010 Berkeley</groupparts>
+
<div class="row">
 +
<div class="col12-3">
 +
 
 +
<h3>Function</h3>
 +
Stress promoters respond differently to various types of stress that is placed on the cell. We wanted a promoter that would be downregulated in the presence of membrane stress caused by the overexpression of ToxR fusion proteins. The design principle was to express ToxR fusion proteins under this promoter such that the stress it caused would downregulate its production.
 +
 
 +
<h3>Assembly</h3>
 +
The 34 stress promoters, identified from microarray data (Moen, 2009), were PCRed from E. coli MG1655 Genomic DNA. Basic parts were made in plasmids with pUC origins. A constitutive promoter (Pcon) was also cloned into a basic part as a control for characterization.
 +
 
 +
<h3>Characterization</h3>
 +
<p>The pool of 35 promoters was assembled in front of a rbs.sfGFP reporter gene, and the construct was transformed into E. coli MC1061. The transformed cells were subjected to generalized stresses (heat, cold, acid, base, salt) overnight, and their resulting fluorescence was measured.</p>
 +
 
 +
<center>
 +
<b><img src="https://static.igem.org/mediawiki/2011/0/03/Stress_Conditions.jpg" width= "400" height="250" align="center"></b></center>
 +
<b></b>
 +
 
 +
<h3>Data</h3>
 +
<p>Downregulation in response to stress, resulting in decreased fluorescence, was desired. Tecan plate measurements showed initial downregulation in some of the stress promoeters, with the cold condition yielding the best results. Further flow cytometry experiments confirmed the stress-responsive downregulation shown by the Tecan. In the figures below, we show fluorescence relative to that of the constitutive promoter in both conditions. Here we show our cold condition (25 degrees C) vs our control condition (37 degrees C). We find that that these chosen 4 promoters have downregulated activity from the environmental stress we put on the cells.</p>
 +
 
 +
<img src="https://static.igem.org/mediawiki/2011/f/fd/Cytometrydata.png" height="275" ><img src="https://static.igem.org/mediawiki/2011/3/3d/Tecandata.png" height="285" align="right">
 +
 
 +
 
 +
</div>
 +
<div class="row-end" ></div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
 
 +
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/b/b6/PartssubHeader3.jpg" width="980"> </div> </div>
 +
<div class="row-end" ></div>
 +
 
 +
<div class="row">
 +
<div class="col12-3">
 +
 
 +
<h3>Function</h3>
 +
The expression plasmid consists of a stress promoter regulating the production of ToxR. This construct allows us to express enough ToxR to allow for the functionality we desire and at the same time have minimal affect on bacterial growth rate.
 +
 
 +
<h3>Assembly</h3>
 +
The ToxR was PCR amplified out of V. cholerae genomic DNA, digested, and ligated in front of the leucine zipper IILK. A library of potential stress promoters and an RBS library were put in front of the ToxR fusion protein and the library was screened for healthy, transcriptionally active clones. We found a combination of the rffGH stress promoter and an rbs variant gave us the functionality we desired. This construct was then used as our template for our other ToxR fusion proteins. Note: for our ToxR chimeras, we switched from an IILK constitutive dimerizing periplasmic domain to Lambda-Rep and MukF constitutive dimerizing periplasmic domains after we identified the stress promoter because they provided higher levels fluorescence in our experiments. For this reason, we collected data using ToxR fusions of Lambda-Rep and MukF.
 +
 
 +
<br><br><center><img src="https://static.igem.org/mediawiki/2011/1/14/ToxRLamRep.png" height="120" align="center"></center>
 +
 
 +
<h3>Characterization</h3>
 +
For characterization, we made fusion proteins of ToxR with Lamda Repressor and MukF proteins. Both of these proteins dimerize in wild-type and we expect them to help ToxR dimerize as well. We transformed ToxR-LambdaRep driven by Pstress into our reporter strain (see below for more details). In parallel, we also transformed our original constructs of ToxR-lambdaRep driven by Pbad into our reporter strains. Each construct was grown in 100 mg/ml, 50 mg/ml, 25 mg/ml, 12 mg/ml, 6 mg/ml 3 mg/ml, 1.5 mg/ml, and 0 mg/ml arabinose. For our control, a known nontoxic plasmid was transformed into the cells that should not activate our reporter strain.
 +
 
 +
<h3>Data</h3>
 +
As shown in the graph of Pbad-LambdaRep and Pbad-MukF, cells did not grow up well in the varying levels of arabinose. The relative fluorescence graphs also supported the conclusion that our constructs were toxic to the cells.
 +
 
 +
<br><br/>
 +
Our solution to the high toxicity of our ToxR chimeras was to have a promoter that would down regulate transcription when the cell was under stress. As shown in the Pstress graphs of LambdaRep and MukF, cells grew to a much higher OD and fluorescence especially in Pstress-LambdaRep compared to the control. All levels of arabinose showed similar results.
 +
 
 +
<center>
 +
<img src="https://static.igem.org/mediawiki/2011/7/73/Pbad_lamdarep.png" height="350"> <br>
 +
<img src="https://static.igem.org/mediawiki/2011/d/d9/Pbad_mukF.png" height="350"> <br>
 +
<img src="https://static.igem.org/mediawiki/2011/d/d4/Pstress_lamdarep.png" height="350"> <br>
 +
<img src="https://static.igem.org/mediawiki/2011/2/26/Pstress_mukF.png" height="350"> <br>
 +
<img src="https://static.igem.org/mediawiki/2011/e/e5/Control.png" height="350">
 +
</center>
 +
 
 +
</div>
 +
<div class="row-end" ></div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
 
 +
 
 +
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/d/dc/PartssubHeader4.jpg" width="980"> </div> </div>
 +
<div class="row-end" ></div>
 +
 
 +
 
 +
 
 +
<div class="row">
 +
<div class="col12-3">
 +
 
 +
<h3>Function</h3>
 +
The reporter construct give a fluorescent output that correlates to the amount of transcriptional activity ToxR promotes on Pctx (it's wild type promoter). Since transcriptional activity by ToxR dimers depends on the strength of dimerization, the level of fluorescence can be correlated to how tightly the ToxR dimerizes.
 +
 
 +
<h3>Assembly</h3>
 +
ToxR’s native target, the ctx promoter (Pctx), was PCRed out of Vibrio cholerae genomic DNA and made into a basic part. The promoter was then placed upstream of an rbs.sfGFP part using 2AB assembly.
 +
 
 +
<br><br><center><img src="https://static.igem.org/mediawiki/2011/2/27/PctxGFP.png" height="100" align="center"></center>
 +
 
 +
 
 +
<h3>Characterization</h3>
 +
By cotransforming this reporter plasmid and the expression plasmid (see above) we were able to measure the strength of ctx promoter (Pctx) induction by ToxR.
 +
 
 +
<h3>Data</h3>
 +
See Expression Plasmid Data above.
 +
 
 +
</div>
 +
<div class="row-end" ></div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
 
 +
<div class="row">
 +
<div class="col12"> <img src="https://static.igem.org/mediawiki/2011/0/04/PartssubHeader5.jpg" width="980"> </div> </div>
 +
<div class="row-end" ></div>
 +
 
 +
<div class="row">
 +
<div class="col12-3">
 +
 
 +
<h3>Function</h3>
 +
The human estrogen receptor is known to dimerize around estradiol. By fusing the human estrogen receptor to ToxR, we can create an estradiol biosensor and potentially an estradiol-inducible system in E. coli.
 +
 
 +
<h3>Assembly</h3>
 +
The estrogen receptor was refactored to optimally express in E. coli and assembled using designed oligos and PCA (polymerase cycling assembly). The final protein was made into a basic part. Various sub-sections of the estrogen receptor were PCR amplified as basic parts in order to create truncations that might display different responses to estradiol (see figure). The estrogen receptor was fused to ToxR’s C-terminus with Gly-Ser linkers and thus exposed to the periplasm when expressed in the cell.
 +
 
 +
<br><br> <center><img src="https://static.igem.org/mediawiki/2011/2/29/EstrogenToxR.png" height="100"></center>
 +
 
 +
<h3>Characterization</h3>
 +
In order to characterize the system, the different truncations of estrogen receptor fused to ToxR were tested with a plate reader. In our control condition, no estrogen was added. For the experimental condition, 1uM of estradiol was added to the solution.
 +
 
 +
<br><br>
 +
<center><img src="https://static.igem.org/mediawiki/2011/f/ff/EstrogenFigureFinal.png" height="370"></center>
 +
 
 +
<h3>Data</h3>
 +
Below are the results of the plate reader data for our control and experimental conditions described above. We find that there is no truncation of estrogen receptor that gives an estradiol-inducible system; however, we are optimistic about trying other truncations and ToxR fusions that might lead us to an estrogen biosensor.
 +
 
 +
<br><br> <center><img src="https://static.igem.org/mediawiki/2011/9/97/Estrogendata.png" width="800"></center>
 +
 
 +
 
 +
</div>
 +
<div class="row-end" ></div>
 +
</div>
 +
 
 +
<div class="row">
 +
<div class="col12" id="spacer3"></div>
 +
<div class="row-end"> </div>
 +
</div>
 +
 
 +
 
 +
</div>
 +
</html>

Latest revision as of 00:14, 29 September 2011

header
Mercury
# of parts submitted:
  • 35 Regulatory promoters
  • 2 Ribosome Binding Sites
  • 2 Composite expression modules
  • 2 Coding proteins
Total: 42 Parts

Assembly Method: BglBricks

Accomplishments:
  • All 42 parts have been submitted to the registry and can be found HERE
  • We submitted two new well-characterized BioBrick Parts in vector pSB1AC3 according to RFC10
  • Compiled a set of 35 stress promoters that future iGEMers can utilize as regulatory elements

Function

Stress promoters respond differently to various types of stress that is placed on the cell. We wanted a promoter that would be downregulated in the presence of membrane stress caused by the overexpression of ToxR fusion proteins. The design principle was to express ToxR fusion proteins under this promoter such that the stress it caused would downregulate its production.

Assembly

The 34 stress promoters, identified from microarray data (Moen, 2009), were PCRed from E. coli MG1655 Genomic DNA. Basic parts were made in plasmids with pUC origins. A constitutive promoter (Pcon) was also cloned into a basic part as a control for characterization.

Characterization

The pool of 35 promoters was assembled in front of a rbs.sfGFP reporter gene, and the construct was transformed into E. coli MC1061. The transformed cells were subjected to generalized stresses (heat, cold, acid, base, salt) overnight, and their resulting fluorescence was measured.

Data

Downregulation in response to stress, resulting in decreased fluorescence, was desired. Tecan plate measurements showed initial downregulation in some of the stress promoeters, with the cold condition yielding the best results. Further flow cytometry experiments confirmed the stress-responsive downregulation shown by the Tecan. In the figures below, we show fluorescence relative to that of the constitutive promoter in both conditions. Here we show our cold condition (25 degrees C) vs our control condition (37 degrees C). We find that that these chosen 4 promoters have downregulated activity from the environmental stress we put on the cells.

Function

The expression plasmid consists of a stress promoter regulating the production of ToxR. This construct allows us to express enough ToxR to allow for the functionality we desire and at the same time have minimal affect on bacterial growth rate.

Assembly

The ToxR was PCR amplified out of V. cholerae genomic DNA, digested, and ligated in front of the leucine zipper IILK. A library of potential stress promoters and an RBS library were put in front of the ToxR fusion protein and the library was screened for healthy, transcriptionally active clones. We found a combination of the rffGH stress promoter and an rbs variant gave us the functionality we desired. This construct was then used as our template for our other ToxR fusion proteins. Note: for our ToxR chimeras, we switched from an IILK constitutive dimerizing periplasmic domain to Lambda-Rep and MukF constitutive dimerizing periplasmic domains after we identified the stress promoter because they provided higher levels fluorescence in our experiments. For this reason, we collected data using ToxR fusions of Lambda-Rep and MukF.

Characterization

For characterization, we made fusion proteins of ToxR with Lamda Repressor and MukF proteins. Both of these proteins dimerize in wild-type and we expect them to help ToxR dimerize as well. We transformed ToxR-LambdaRep driven by Pstress into our reporter strain (see below for more details). In parallel, we also transformed our original constructs of ToxR-lambdaRep driven by Pbad into our reporter strains. Each construct was grown in 100 mg/ml, 50 mg/ml, 25 mg/ml, 12 mg/ml, 6 mg/ml 3 mg/ml, 1.5 mg/ml, and 0 mg/ml arabinose. For our control, a known nontoxic plasmid was transformed into the cells that should not activate our reporter strain.

Data

As shown in the graph of Pbad-LambdaRep and Pbad-MukF, cells did not grow up well in the varying levels of arabinose. The relative fluorescence graphs also supported the conclusion that our constructs were toxic to the cells.

Our solution to the high toxicity of our ToxR chimeras was to have a promoter that would down regulate transcription when the cell was under stress. As shown in the Pstress graphs of LambdaRep and MukF, cells grew to a much higher OD and fluorescence especially in Pstress-LambdaRep compared to the control. All levels of arabinose showed similar results.




Function

The reporter construct give a fluorescent output that correlates to the amount of transcriptional activity ToxR promotes on Pctx (it's wild type promoter). Since transcriptional activity by ToxR dimers depends on the strength of dimerization, the level of fluorescence can be correlated to how tightly the ToxR dimerizes.

Assembly

ToxR’s native target, the ctx promoter (Pctx), was PCRed out of Vibrio cholerae genomic DNA and made into a basic part. The promoter was then placed upstream of an rbs.sfGFP part using 2AB assembly.

Characterization

By cotransforming this reporter plasmid and the expression plasmid (see above) we were able to measure the strength of ctx promoter (Pctx) induction by ToxR.

Data

See Expression Plasmid Data above.

Function

The human estrogen receptor is known to dimerize around estradiol. By fusing the human estrogen receptor to ToxR, we can create an estradiol biosensor and potentially an estradiol-inducible system in E. coli.

Assembly

The estrogen receptor was refactored to optimally express in E. coli and assembled using designed oligos and PCA (polymerase cycling assembly). The final protein was made into a basic part. Various sub-sections of the estrogen receptor were PCR amplified as basic parts in order to create truncations that might display different responses to estradiol (see figure). The estrogen receptor was fused to ToxR’s C-terminus with Gly-Ser linkers and thus exposed to the periplasm when expressed in the cell.

Characterization

In order to characterize the system, the different truncations of estrogen receptor fused to ToxR were tested with a plate reader. In our control condition, no estrogen was added. For the experimental condition, 1uM of estradiol was added to the solution.

Data

Below are the results of the plate reader data for our control and experimental conditions described above. We find that there is no truncation of estrogen receptor that gives an estradiol-inducible system; however, we are optimistic about trying other truncations and ToxR fusions that might lead us to an estrogen biosensor.