Team:Wisconsin-Madison/biobricks

From 2011.igem.org

(Difference between revisions)
(Created page with "<html> <style> hr { border: none; border-top: 1px #000000 solid; } #globalWrapper { //background: url('http://2011.igem...")
 
(5 intermediate revisions not shown)
Line 153: Line 153:
<center style="position:absolute; left:2px; top:210px">
<center style="position:absolute; left:2px; top:210px">
<ul id="sddm">
<ul id="sddm">
-
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/umad" onmouseover="mopen('m1')" onmouseout="mclosetime()">Home</a>
+
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison" onmouseover="mopen('m1')" onmouseout="mclosetime()">Home</a>
<div id="m1" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
<div id="m1" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/umad">Main</a>
+
<a href="https://2011.igem.org/Team:Wisconsin-Madison">Main</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/whatisigem">What is iGEM?</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/whatisigem">What is iGEM?</a>
 +
<a href="https://2011.igem.org/Team:Wisconsin-Madison/ca">Contributions & Attributions</a>
</div>
</div>
</li>
</li>
Line 166: Line 167:
                 <a href="https://2011.igem.org/Team:Wisconsin-Madison/directedevolution">Directed Evolution</a>
                 <a href="https://2011.igem.org/Team:Wisconsin-Madison/directedevolution">Directed Evolution</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/bmc">Microcompartment</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/bmc">Microcompartment</a>
 +
                <a href="https://2011.igem.org/Team:Wisconsin-Madison/parts">Parts</a>
</div>
</div>
</li>
</li>
Line 176: Line 178:
</div>
</div>
</li>
</li>
-
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/notebook" onmouseover="mopen('m4')" onmouseout="mclosetime()">Notebook</a>
+
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/calender" onmouseover="mopen('m4')" onmouseout="mclosetime()">Notebook</a>
<div id="m4" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
<div id="m4" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/notebookprotocols">Protocols</a>
+
<a href="https://2011.igem.org/Team:Wisconsin-Madison/protocols">Protocols</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/notebookcalender">Calender</a>
+
<a href="https://2011.igem.org/Team:Wisconsin-Madison/calender">Calendar</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/notebookexperiements">Experiment</a>
+
<a href="https://2011.igem.org/Team:Wisconsin-Madison/references">References</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/notebookreferences">References</a>
+
</div>
</div>
</li>
</li>
Line 189: Line 190:
<a href="https://2011.igem.org/Team:Wisconsin-Madison/reuposterSession">REU Poster Session</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/reuposterSession">REU Poster Session</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/socialmedia">Social Media</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/socialmedia">Social Media</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/presentations">Presentations</a>
 
</div>
</div>
</li>
</li>
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/safety" onmouseover="mopen('m6')" onmouseout="mclosetime()">Safety</a>
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/safety" onmouseover="mopen('m6')" onmouseout="mclosetime()">Safety</a>
 +
<div id="m6" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
 +
<a href="https://2011.igem.org/Team:Wisconsin-Madison/humanpractice">Human Practice</a>
 +
</div>
</li>
</li>
</ul>
</ul>
</center>
</center>
 +
<center>
<center>
Line 214: Line 218:
<table border="0" cellspacing="4" cellpadding="0"><tr><td>
<table border="0" cellspacing="4" cellpadding="0"><tr><td>
-
<img src="http://www.toreuse.com/wp-content/uploads/2010/12/tecan-2.jpg"/ align="right" width="350">
+
<img src="http://partsregistry.org/wiki/images/2/22/StdAsssmall.png"/ align="right">
<strong><font size="3">
<strong><font size="3">
-
Ethanol Sensor
+
Biobricks
</font></strong><p>
</font></strong><p>
-
The primary source of results thus far has been a plate reader. This is a device which can record the optical density (OD – a measure of cell concentration) as well as the fluorescence of up to 96 cultures at once. Ideally, we hope to produce such a robust fluorescent response as to not need the plate reader for qualitative assessments.
+
BioBricks are DNA sequences with a <a href="https://2011.igem.org/Team:Wisconsin-Madison/cutsites">standardized interface</a> that allows for simple cut and paste construction of biological systems. The interface consists of six specific restriction enzyme sites that flank the DNA coding region upstream and downstream; Along with restriction sites, BioBrick parts are also cloned into a specific plasmid backbone. There are two classifications of BioBricks:  parts and devices. Parts are the basic constituents of larger systems that code for basic biological functions, and devices consist of multiple parts that work synergistically to serve a specific application.  In order to functionalize these BioBricks, they are implemented into living cells, most commonly E. coli bacterial cells. Every year, each iGEM team submits their standardized BioBricks to the iGEM parts <a href="https://2011.igem.org/Team:Wisconsin-Madison/registry">registry</a>; this registry constitutes an open source library of synthetic biological parts that any future team can order and use for their project.  
<p><br>
<p><br>
-
This graph shows the fluorescent response of cell cultures containing two plasmids: pBAD33bb: exaDE and PexaA: TagRFP in pSB1A2 (pEtRv2.1). The fluorescence of the system at varying ethanol concentrations was normalized to the optical density of their respective cell culture. The cells’ fluorescence was measured over a range of ethanol concentrations from 0%-5% EtOH. This ethanol sensing system is “turned on” or induced in the presence of arabinose by the PBAD promoter.  The blue data points on the graph represent the fluorescence of cell cultures without any arabinose and therefore the ethanol sensor is uninduced; the red data points represent the fluorescent response of the induced system in the presence of .2% arabinose.
+
<font size="1"><i>Image source: http://partsregistry.org/wiki/images/2/22/StdAsssmall.png</i></font>
-
<p><br>
+
 
-
<img src="https://static.igem.org/mediawiki/2011/0/00/Pets_2.1_graph.jpg" align="left" width="500">
+
 
-
From the graph, it can be seen that there is an increase in fluorescence between the induced and uninduced system. This is the result that was expected, however, there isn’t a large difference in fluorescence between the two systems. To further increase this difference in fluorescence, we intend to decrease the “leakiness” of our promoter through directed evolution.  Additionally, the graph shows a positive correlation between fluorescence and ethanol concentration; therefore, our ethanol sensor exhibits a linear response in fluorescent intensity with varying ethanol concentrations. The magnitude of the slope of the data points represents the degree of our systems response. Currently, the slope of the data is smaller than desired. This will  also be the target of a directed evolution upon the ethanol sensor.
+
 
 +
 
 +
 

Latest revision as of 23:00, 28 September 2011









Project >> Overview, Ethanol Sensor, Alkane Sensor, Microcompartment

Biobricks

BioBricks are DNA sequences with a standardized interface that allows for simple cut and paste construction of biological systems. The interface consists of six specific restriction enzyme sites that flank the DNA coding region upstream and downstream; Along with restriction sites, BioBrick parts are also cloned into a specific plasmid backbone. There are two classifications of BioBricks: parts and devices. Parts are the basic constituents of larger systems that code for basic biological functions, and devices consist of multiple parts that work synergistically to serve a specific application. In order to functionalize these BioBricks, they are implemented into living cells, most commonly E. coli bacterial cells. Every year, each iGEM team submits their standardized BioBricks to the iGEM parts registry; this registry constitutes an open source library of synthetic biological parts that any future team can order and use for their project.


Image source: http://partsregistry.org/wiki/images/2/22/StdAsssmall.png