Difference between revisions of "Team:Stony Brook"

 
(45 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Stony_Brook}}
 
{{Stony_Brook}}
 
<html>
 
<html>
−
<h2> Stony Brook iGEM 2015 </h2>
 
  
−
<h4>Before you start: </h4>
+
<style>
−
<p> Please read the following pages:</p>
+
  #sbu {
−
<ul>
+
    text-align: center;
−
<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>
+
  
−
<div class="highlightBox">
+
  p {
−
<h4> Styling your wiki </h4>
+
    text-indent: 50px;
−
<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>  
+
 
 +
  #splash {
 +
    background-image: url("https://static.igem.org/mediawiki/2015/c/c4/SB_Campus_arial_view.jpg");
 +
    height: calc(100vh - (75px));
 +
    background-size: cover;
 +
    //background-repeat: no-repeat;
 +
    background: transparent;
 +
    position: relative;
 +
    display: block;
 +
  }
 +
 
 +
  #title {
 +
    position: relative;
 +
    top: 65vh;
 +
    background: transparent;
 +
    box-sizing: border-box;
 +
    border: 0px solid black;
 +
    border-radius: 10px;
 +
    padding-left: 15px;
 +
    padding-right: 15px;
 +
    margin-left: auto;
 +
    margin-right: auto;
 +
  }
 +
 
 +
  #title h2 {
 +
    color: #E60000;
 +
    font-size: 72px;
 +
    opacity: 1;
 +
    line-height: 100%;
 +
    font-family: garamond, crimsonText, serif;
 +
    font-weight: bolder;
 +
    color: crimson;
 +
  }
 +
 
 +
*/  #testButton {
 +
    padding: 15px;
 +
    background: red;
 +
    position: absolute;
 +
    left: 45%;
 +
    bottom: 5%;
 +
    max-width: 5px;
 +
    max-height: 5px;
 +
    overflow: hidden;
 +
    border: 3px solid black;
 +
    border-radius: 10px;
 +
    -webkit-transition: max-height 0.75s, max-width 0.75s;
 +
    transition: max-height 0.75s, max-width 0.75s;
 +
  }
 +
 
 +
  #testButton:hover {
 +
    max-width: 100px;
 +
    max-height: 100px;
 +
  }
 +
 
 +
  #testButton a {
 +
    opacity: 0.01;
 +
  }
 +
 
 +
  #testButton:hover a {
 +
    opacity: 1;
 +
  } */
 +
 
 +
  #contentContainer {
 +
    //height: 1%;
 +
    //overflow: hidden;
 +
    width: 100vw;
 +
    //background-image: url("https://static.igem.org/mediawiki/2015/c/c4/SB_Campus_arial_view.jpg");
 +
    //background-size: cover;
 +
    //background-repeat: no-repeat;
 +
  }
 +
 
 +
  /*#iGEM img {
 +
    height: 100px;
 +
    position: absolute;
 +
    top: 75px;
 +
    left: 50px;
 +
  } */
 +
 
 +
  body {
 +
background-image: url(https://static.igem.org/mediawiki/2015/9/92/SB_Campus_arial_view_modification_attempt1.png);
 +
background-repeat:no-repeat;
 +
background-position: center center;
 +
background-attachment: fixed;
 +
-webkit-background-size: cover;
 +
-moz-background-size: cover;
 +
-o-background-size: cover;
 +
background-size: cover;
 +
        //overflow: hidden;  //DISABLE THIS IF YOU WANT TO USE PREVIEW                        THIS LINE BREAKS PREVIEW
 +
  }
 +
 
 +
  #social {
 +
        float: right;
 +
        margin-right: 50px;
 +
  }
 +
 
 +
  #social img {
 +
        padding-left: 15px;
 +
        padding-right: 15px;
 +
  }
 +
 
 +
  #social img:hover {
 +
        opacity: 0.5;
 +
  }
 +
 
 +
  /* #iGEM img:hover {
 +
        opacity: 0.5;
 +
  } */
 +
 
 +
  #space {
 +
      height: 100%; }
 +
 
 +
  #content {
 +
      height: 50px;}
 +
  #homeContent {
 +
      background-color: white;
 +
      padding-bottom: 25px;
 +
      font-size: 20px;}
 +
  #homeContent p, h4 {
 +
      margin-right: 10%;
 +
      margin-left: 10%}
 +
  #overview{
 +
      text-align:center;
 +
      margin:auto;}
 +
 
 +
#toobig {
 +
    width: 60%;
 +
    margin-left: 20%;}
 +
 
 +
#end {
 +
    width: 50%;
 +
    margin-left: 25%;
 +
    border: 2px solid black;
 +
    border-radius: 15px;
 +
    text-align: center;}
 +
 
 +
</style>
 +
 
 +
 
 +
<div id=splash>
 +
 
 +
<div id=title>
 +
<h2 id=sbu> Stony Brook iGEM 2015 </h2>
 
</div>
 
</div>
  
−
<h4> Editing your wiki </h4>
+
<!-- <div id=iGEM>
−
<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>  
+
  <a href="https://2015.igem.org/Team:Stony_Brook"><img src="https://static.igem.org/mediawiki/2015/1/16/SBU_Igem_logo_1.png"></img></a>
−
<p> <a href="https://2015.igem.org/wiki/index.php?title=Team:Stony_Brook&action=edit"> Click here to edit this page! </a></p>
+
</div>    -->
−
<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>  
+
  
 +
<div id=social>
 +
  <a href="http://twitter.com/iGEMSBU"><img src="https://static.igem.org/mediawiki/2014/b/b5/Stony_brook_twitter_logo.png" alt= "twitter"></img></a>
 +
  <a href="http://www.facebook.com/iGEMatstonybrook"><img src="https://static.igem.org/mediawiki/2014/0/0f/Stony_brook_fb_logo.png" alt= "facebook"></img></a>
  
−
<h4>Templates </h4>
+
</div>
−
<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>Tips</h4>
+
<div id= space>
−
<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>
+
<p>.</p>
−
<ul>
+
</div>
−
<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>  
+
  
 +
<div id= "homeContent">
  
−
<h4>Inspiration</h4>
+
<h1 id=overview>Overview</h1>
−
<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> Uploading pictures and files </h4>
+
<h4>Background</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's namespace or at least include your team's name in the file name. <br />
+
<p> The human body has many feedback systems to maintain a suitable environment for its cells.  In its simplest form, a homeostatic system consists of a sensor and a response that the sensor can trigger. Our project investigates recreating such a system using E. Coli to determine the robustness and reliability of such an endeavor.  Our project has its roots in type II diabetes, when we thought about how people with this disease cannot get rid of excess glucose in their blood naturally. We imagined a system in which E. Coli detect high levels of glucose, and help the human body eliminate it. Most importantly, we decided to try and do this without the use of insulin in any way, due to the insulin insensitivity of the afflicted.</p>
−
When you upload, set the "Destination Filename" to <code>Team:YourOfficialTeamName/NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
+
  
−
<a href="https://2015.igem.org/Special:Upload">CLICK HERE TO UPLOAD FILES</a>
+
<h4>System</h4>
 +
<p> Our sensor is actually a protein that occurs naturally in E. Coli, EnvZ.  EnvZ is a protein receptor on the surface of the bacterium.  In response to high environmental osmolarity, it phosphorylates OmpR.  OmpR-P (phosphorylated) becomes a transcription factor that can bind to a specific promoter, OmpC, and allow transcription of downstream genes.Since a higher glucose level would raise osmolarity, this sensor could allow E. Coli to produce a protein in response to high glucose.</p>
 +
<p>The kidneys naturally reabsorb glucose from the urine to prevent a loss of unused glucose, and then it is stored.  For someone with type II diabetes, it gets reabsorbed into the blood, but it can’t be stored.  We found two tripeptides which have shown in clinical trials to actually block the proteins involved in reabsorbing glucose in the kidneys.  Our plan is to have these peptides controlled under an OmpC promoter so they would be produced when blood glucose is high, and would cause blood glucose to go down.</p>
 +
 
 +
<h4>Complications</h4>
 +
<p> One major complication was the fact that secreting tripeptides is a much harder task than it would seem.  We decided to make slightly larger peptides which are repeating chains of our tripeptides.  In a second cell, we can have a protease which cuts between our repeats.  This protease would be under a constituent T7 promoter so it is always available, and will be bound to the membrane to prevent it from interfering with the cells.  The whole system can be implemented in microcapsules with pores small enough so that the tripeptides and glucose can diffuse in and out, but the protease or any immune cells can’t.  Below is the full model for our system.</p>
 +
 
 +
<img id=toobig src="https://static.igem.org/mediawiki/2015/d/dc/7-7-15_model.png" width=100%></img>
 +
 
 +
<h4>Future Plans</h4>
 +
<p> Our hopes for our system are to create cells which successfully create our tripeptide in response to glucose, and cells that successfully express our protease.  Then we hope to put them together to study their interactions.  Besides creating our system, we hope to investigate a better sensor, as well as perhaps how to design specific sensors.  EnvZ is a histidine kinase, which has a cytoplasmic domain and a periplasmic domain.  The periplasmic domain seems to be the part that controls what triggers the protein, while the cytoplasmic domain controls what happens when it triggers.  We want to research possible ways to replace the periplasmic domain while retaining the cytoplasmic domain to possibly create a sensor that can detect other things, like glucose specifically.</p>
 +
 
 +
<div id=end>
 +
<h3>Congratulations team for winning a silver medal!</h3> </div>
 +
 
 +
</div>
  
  
  
−
</div></div> <!--These are the closing tags for div id="mainContainer" and div id="contentContainer". The corresponding opening tags appear in the template that is {{included}} at the top of this page.-->
+
<!--These were the closing tags for div id="mainContainer" and div id="contentContainer". The corresponding opening tags appear in the template that is {{included}} at the top of this page. REMOVED DUE TO PREVIEW GLITCH-->
  
 
</html>
 
</html>

Latest revision as of 12:44, 5 October 2015

Stony Brook iGEM 2015

twitter facebook

.

Overview

Background

The human body has many feedback systems to maintain a suitable environment for its cells. In its simplest form, a homeostatic system consists of a sensor and a response that the sensor can trigger. Our project investigates recreating such a system using E. Coli to determine the robustness and reliability of such an endeavor. Our project has its roots in type II diabetes, when we thought about how people with this disease cannot get rid of excess glucose in their blood naturally. We imagined a system in which E. Coli detect high levels of glucose, and help the human body eliminate it. Most importantly, we decided to try and do this without the use of insulin in any way, due to the insulin insensitivity of the afflicted.

System

Our sensor is actually a protein that occurs naturally in E. Coli, EnvZ. EnvZ is a protein receptor on the surface of the bacterium. In response to high environmental osmolarity, it phosphorylates OmpR. OmpR-P (phosphorylated) becomes a transcription factor that can bind to a specific promoter, OmpC, and allow transcription of downstream genes.Since a higher glucose level would raise osmolarity, this sensor could allow E. Coli to produce a protein in response to high glucose.

The kidneys naturally reabsorb glucose from the urine to prevent a loss of unused glucose, and then it is stored. For someone with type II diabetes, it gets reabsorbed into the blood, but it can’t be stored. We found two tripeptides which have shown in clinical trials to actually block the proteins involved in reabsorbing glucose in the kidneys. Our plan is to have these peptides controlled under an OmpC promoter so they would be produced when blood glucose is high, and would cause blood glucose to go down.

Complications

One major complication was the fact that secreting tripeptides is a much harder task than it would seem. We decided to make slightly larger peptides which are repeating chains of our tripeptides. In a second cell, we can have a protease which cuts between our repeats. This protease would be under a constituent T7 promoter so it is always available, and will be bound to the membrane to prevent it from interfering with the cells. The whole system can be implemented in microcapsules with pores small enough so that the tripeptides and glucose can diffuse in and out, but the protease or any immune cells can’t. Below is the full model for our system.

Future Plans

Our hopes for our system are to create cells which successfully create our tripeptide in response to glucose, and cells that successfully express our protease. Then we hope to put them together to study their interactions. Besides creating our system, we hope to investigate a better sensor, as well as perhaps how to design specific sensors. EnvZ is a histidine kinase, which has a cytoplasmic domain and a periplasmic domain. The periplasmic domain seems to be the part that controls what triggers the protein, while the cytoplasmic domain controls what happens when it triggers. We want to research possible ways to replace the periplasmic domain while retaining the cytoplasmic domain to possibly create a sensor that can detect other things, like glucose specifically.

Congratulations team for winning a silver medal!