Difference between revisions of "Team:Hamilton McMaster"

 
(38 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
<html>
+
{{Hamilton_McMaster}}
−
<!-- ####################################################### -->
+
−
<!-- #  This html was produced by the igemwiki generator  # -->
+
−
<!-- #  https://github.com/igemuoftATG/generator-igemwiki  # -->
+
−
<!-- ####################################################### -->
+
  
−
<!-- repo for this wiki:  -->
+
<html>
  
−
</html>
+
<div class = "band">
−
{{Hamilton_McMaster/head}}
+
<h2> Abstract </h2>
−
<html>
+
<div class = "highlightBox">
−
<!-- <a href="" > direct image linking </a>
+
<p>Light-based bacterial protein expression systems have been well documented. Tabor <i>et al.</i> demonstrated a multichromatic protein expression system in E. coli through the combination of the CcaR-CcaS green-light sensitive construct derived from cyanobacteria and a previously characterized red-light sensitive system. This could be leveraged for the expression of multiple genes by exposing the bacteria to different wavelengths of light, i.e. red and green. We propose the application of this construct to recombinant protein expression. Using genetic cloning and recombinant protein techniques, <i>E. coli</i> is concurrently transformed with three plasmids: a chromophore, a red-light sensitive system, and a green-light sensitive system. Protein expression is induced through shining red light on the bacterial population. Following this, cell lysis is triggered by shining green light, which is mediated by a T4 Holin/Endolysin system. This releases the protein of interest into the cell media, allowing for straightforward collection and purification. This system would have important applications in both research and industry, allowing for the optimization and potential automation of heterologous bacterial protein production.</p>
−
 
+
−
<img src="" />
+
−
 
+
−
<p>Inline <strong>markdown</strong>!</p>
+
−
<p>HAMILTON_MCMASTER</p>
+
−
<p>More working md?</p>
+
−
<ul>
+
−
<li>yes</li>
+
−
<li>no</li>
+
−
</ul>
+
−
-->
+
−
 
+
−
<div id="navigation">
+
−
<ul>
+
−
<li class="active"><a href="https://2015.igem.org/Team:Hamilton_McMaster">home</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Team">team</a></li>
+
−
<li><a href="#">project</a>
+
−
<ul>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Description">description</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Experiments">experiments</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Results">results</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Design">design</a></li>
+
−
</ul>
+
−
</li><li><a href="#">parts</a>
+
−
<ul>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Parts">parts</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Basic_Part">basic parts</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Composite_Part">composite parts</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Part_Collection">part collection</a></li>
+
−
</ul>
+
−
</li><li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Notebook">notebook</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Attributions">attributions</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Collaborations">collaborations</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Practices">human practices</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Safety">safety</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Modeling">modeling</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Measurement">measurement</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Software">software</a></li>
+
−
<li><a href="https://2015.igem.org/Team:Hamilton_McMaster/Entrepreneurship">entrepreneurship</a></li>
+
−
</ul>
+
 
</div>
 
</div>
−
<div class="content">
 
−
<h2 id="welcome-to-igem-2015-">Welcome to iGEM 2015!</h2>
 
−
<p>Your team has been approved and you are ready to start the iGEM season!</p>
 
−
<h4 id="before-you-start-">Before you start:</h4>
 
−
<p>Please read the following pages:</p>
 
−
<ul>
 
−
<li><a href="https://2015.igem.org/Requirements">Requirements page</a></li>
 
−
<li><a href="https://2015.igem.org/Wiki_How-To">Wiki Requirements page</a></li>
 
−
</ul>
 
−
<h4 id="styling-your-wiki">Styling your wiki</h4>
 
−
<p>You may style this page as you like or you can simply leave the style as it is.
 
−
You can easily keep the styling and edit the content of these default wiki pages
 
−
with your project information and completely fulfill the requirement to document
 
−
your project.</p>
 
−
<p>While you may not win Best Wiki with this styling, your team is still eligible
 
−
for all other awards. This default wiki meets the requirements, it improves
 
−
navigability and ease of use for visitors, and you should not feel it is
 
−
necessary to style beyond what has been provided.</p>
 
−
<h4 id="editing-your-wiki">Editing your wiki</h4>
 
−
<p>On this page you can document your project, introduce your team members,
 
−
document your progress and share your iGEM experience with the rest of the
 
−
world!</p>
 
−
<p><a href="https://2015.igem.org/wiki/index.php?title=Team:Toronto&amp;action=edit">Click here to edit this page!</a></p>
 
−
<p>See tips on how to edit your wiki on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template
 
−
Documentation</a> page.</p>
 
−
<h4 id="templates">Templates</h4>
 
−
<p>This year we have created templates for teams to use freely. More information on
 
−
how to use and edit the templates can be found on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template
 
−
Documentation</a> page.</p>
 
−
<h4 id="tips">Tips</h4>
 
−
<p>This wiki will be your team’s first interaction with the rest of the world, so
 
−
here are a few tips to help you get started:</p>
 
−
<ul>
 
−
<li>State your accomplishments! Tell people what you have achieved from the start.</li>
 
−
<li>Be clear about what you are doing and how you plan to do this.</li>
 
−
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 
−
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 
−
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 
−
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2015.igem.org/Calendar_of_Events">iGEM 2015 calendar</a></li>
 
−
<li>Have lots of fun!</li>
 
−
</ul>
 
−
<h4 id="inspiration">Inspiration</h4>
 
−
<p>You can also view other team wikis for inspiration! Here are some examples:</p>
 
−
<ul>
 
−
<li><a href="https://2014.igem.org/Team:SDU-Denmark/">2014 SDU Denmark</a></li>
 
−
<li><a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a></li>
 
−
<li><a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a></li>
 
−
<li><a href="https://2014.igem.org/Team:Michigan">2014 Michigan</a></li>
 
−
<li><a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara</a></li>
 
−
<li><a href="https://2014.igem.org/Team:SCU-China">2014 SCU-China</a></li>
 
−
</ul>
 
−
<h4 id="uploading-pictures-and-files">Uploading pictures and files</h4>
 
−
<p>You can upload your pictures and files to the iGEM 2015 server. Remember to keep
 
−
all your pictures and files within your team&#39;s namespace or at least include
 
−
your team&#39;s name in the file name.</p>
 
−
<p>When you upload, set the &quot;Destination Filename&quot; to
 
−
<code>Team:YourOfficialTeamName/NameOfFile.jpg</code>. (If you don&#39;t do this, someone else
 
−
might upload a different file with the same &quot;Destination Filename&quot;, and your
 
−
file would be erased!)</p>
 
−
<p><a href="https://2015.igem.org/Special:Upload">CLICK HERE TO UPLOAD FILES</a></p>
 
−
 
 
</div>
 
</div>
 
</html>
 
</html>
−
{{Hamilton_McMaster/footer}}
+
{{:Template:Hamilton_McMaster_Footer}}

Latest revision as of 02:41, 18 September 2015

Abstract

Light-based bacterial protein expression systems have been well documented. Tabor et al. demonstrated a multichromatic protein expression system in E. coli through the combination of the CcaR-CcaS green-light sensitive construct derived from cyanobacteria and a previously characterized red-light sensitive system. This could be leveraged for the expression of multiple genes by exposing the bacteria to different wavelengths of light, i.e. red and green. We propose the application of this construct to recombinant protein expression. Using genetic cloning and recombinant protein techniques, E. coli is concurrently transformed with three plasmids: a chromophore, a red-light sensitive system, and a green-light sensitive system. Protein expression is induced through shining red light on the bacterial population. Following this, cell lysis is triggered by shining green light, which is mediated by a T4 Holin/Endolysin system. This releases the protein of interest into the cell media, allowing for straightforward collection and purification. This system would have important applications in both research and industry, allowing for the optimization and potential automation of heterologous bacterial protein production.