Difference between revisions of "Team:HKUST-Rice"

Line 5: Line 5:
  
 
                 <style type="text/css">
 
                 <style type="text/css">
−
#contentContainer {
+
 
−
padding-top:20px;
+
−
                                padding-bottom: 20px;
+
−
padding-right:20px;
+
−
                                padding-left: 20px;
+
−
margin-bottom: 10px;
+
−
                                margin-left: 20px;
+
−
                                margin-right: 20px;
+
−
width: 92%;
+
−
float: left;
+
−
background-color: #FFFFFF;
+
−
font-family: "Trebuchet MS", Helvetica, sans-serif;
+
−
}
+
  
 
p.link { text-align: right; font-size: 130%;}
 
p.link { text-align: right; font-size: 130%;}
 
a.learn:link{ text-decoration: none;}
 
a.learn:link{ text-decoration: none;}
 
p.link:hover {font-size: 150%;}
 
p.link:hover {font-size: 150%;}
−
p {text-align: justify;}
+
 
  
 
#quicklink {
 
#quicklink {
Line 74: Line 62:
 
                                 padding-top: 20px;
 
                                 padding-top: 20px;
 
                                 line-height: 20px;
 
                                 line-height: 20px;
−
                                 min.height: 100px;
+
                                 min.height: 50px;
 
                                 width:90%;
 
                                 width:90%;
 
                                 font-size: 120%;
 
                                 font-size: 120%;
−
margin-left: 5%;
+
                                margin-left: 5%;
 
                           }
 
                           }
 
                  
 
                  
Line 251: Line 239:
 
</head>
 
</head>
 
 
−
<body>
+
<body>
  
 
<div id="bannerContainer">
 
<div id="bannerContainer">
Line 276: Line 264:
 
<div class= "project_superrow">
 
<div class= "project_superrow">
 
<div id= "page_title"><h1>Project Description</h1>
 
<div id= "page_title"><h1>Project Description</h1>
−
</div>
+
        </div>
 +
 
 
<div class= "project_content">
 
<div class= "project_content">
 
<div class= "project_row">
 
<div class= "project_row">
Line 282: Line 271:
 
<p>In the previous iGEM competitions, multiple teams have worked on nitrate and phosphate responsive promoters, but none of them attempted to provide a potassium responsive promoter. In view of this,  our team is constructing a biological sensor in <i>E. coli</i>, which can detect NPK levels in the surrounding environment and give responses in the form of colors. In addition, we are characterizing the effects of a dual output system, in contrast to a single output system, in order to anticipate the expression of multiple outputs in a single system.</p>
 
<p>In the previous iGEM competitions, multiple teams have worked on nitrate and phosphate responsive promoters, but none of them attempted to provide a potassium responsive promoter. In view of this,  our team is constructing a biological sensor in <i>E. coli</i>, which can detect NPK levels in the surrounding environment and give responses in the form of colors. In addition, we are characterizing the effects of a dual output system, in contrast to a single output system, in order to anticipate the expression of multiple outputs in a single system.</p>
 
   <p class="link"><a class=" learn" href="https://2015.igem.org/Team:HKUST-Rice/Description"><font color=#6B6B47> Learn more ... </font></a></p>
 
   <p class="link"><a class=" learn" href="https://2015.igem.org/Team:HKUST-Rice/Description"><font color=#6B6B47> Learn more ... </font></a></p>
−
</div></div></div>
+
</div>
−
<div class= "project_content">
+
 
 
<div class= "project_row">
 
<div class= "project_row">
 
<h1>The Journey of HKUST-Rice iGEM team </h1>
 
<h1>The Journey of HKUST-Rice iGEM team </h1>
Line 292: Line 281:
 
<p>Besides staying in the lab, we also take every opportunity to engage the community to achieve 2 aims, to introduce synthetic biology to the younger community through <a href ="https://2015.igem.org/Team:HKUST-Rice/Practices_Debate" >debating</a> and to interact with the community and <a href ="https://2015.igem.org/Team:HKUST-Rice/Practices_ExploratoryResearch" >gather their perceptions</a> regarding biosensor and genetic engineering technology. Through engaging the community, we also gain valuable feedbacks and comments which we then use to improve our design. </p>
 
<p>Besides staying in the lab, we also take every opportunity to engage the community to achieve 2 aims, to introduce synthetic biology to the younger community through <a href ="https://2015.igem.org/Team:HKUST-Rice/Practices_Debate" >debating</a> and to interact with the community and <a href ="https://2015.igem.org/Team:HKUST-Rice/Practices_ExploratoryResearch" >gather their perceptions</a> regarding biosensor and genetic engineering technology. Through engaging the community, we also gain valuable feedbacks and comments which we then use to improve our design. </p>
 
</div></div>
 
</div></div>
−
 
−
 
−
<!--
 
−
<h3><ins>Background and Significance</ins></h3>
 
−
</div>
 
−
 
−
<h3> Welcome to iGEM 2015! </h3>
 
−
<p><h4>Your team has been approved and you are ready to start the iGEM season!</h4></p>
 
−
 
−
<h4>Before you start: </h4>
 
−
<p><h4>Please read the following pages:</h4></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>
 
−
 
−
<div class="highlightBox">
 
−
<h4> Styling your wiki </h4>
 
−
<p><h4>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.</h4></p>
 
−
<p><h4>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.</h4></p>
 
−
</div>
 
−
 
−
<h4> Editing your wiki </h4>
 
−
<p><h4>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!</h4></p>
 
−
<p><h4> <a href="https://2015.igem.org/wiki/index.php?title=Team:HKUST-Rice&action=edit"> Click here to edit this page! </a></h4></p>
 
−
<p><h4>See tips on how to edit your wiki on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation</a> page.</h4></p>
 
−
 
−
 
−
<h4>Templates </h4>
 
−
<p><h4>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.</h4></p>
 
−
 
−
 
−
<h4>Tips</h4>
 
−
<p><h4>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:</h4></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>Inspiration</h4>
 
−
<p><h4> You can also view other team wikis for inspiration! Here are some examples:</h4></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>
 
−
<p> <h4>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 />
 
−
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!)</h4></p>
 
−
 
−
<a href="https://2015.igem.org/Special:Upload">CLICK HERE TO UPLOAD FILES</a>
 
−
-->
 
−
 
−
 
−
 
  
  
Line 476: Line 399:
 
               </table>  
 
               </table>  
  
 +
</body>
  
−
       
+
<!--
 +
<h3><ins>Background and Significance</ins></h3>
 +
</div>
 +
 
 +
<h3> Welcome to iGEM 2015! </h3>
 +
<p><h4>Your team has been approved and you are ready to start the iGEM season!</h4></p>
 +
 
 +
<h4>Before you start: </h4>
 +
<p><h4>Please read the following pages:</h4></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>
 +
 
 +
<div class="highlightBox">
 +
<h4> Styling your wiki </h4>
 +
<p><h4>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.</h4></p>
 +
<p><h4>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.</h4></p>
 +
</div>
 +
 
 +
<h4> Editing your wiki </h4>
 +
<p><h4>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!</h4></p>
 +
<p><h4> <a href="https://2015.igem.org/wiki/index.php?title=Team:HKUST-Rice&action=edit"> Click here to edit this page! </a></h4></p>
 +
<p><h4>See tips on how to edit your wiki on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation</a> page.</h4></p>
 +
 
 +
 
 +
<h4>Templates </h4>
 +
<p><h4>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.</h4></p>
 +
 
 +
 
 +
<h4>Tips</h4>
 +
<p><h4>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:</h4></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>Inspiration</h4>
 +
<p><h4> You can also view other team wikis for inspiration! Here are some examples:</h4></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>
 +
<p> <h4>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 />
 +
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!)</h4></p>
 +
 
 +
<a href="https://2015.igem.org/Special:Upload">CLICK HERE TO UPLOAD FILES</a>
 +
-->
  
−
</body>
 
 
</html>
 
</html>

Revision as of 06:57, 30 August 2015

Scroll down to learn more

Project Description

Potassium (K), Phosphorus (P) and Nitrogen (N) are three macronutrients for plants, and deficiencies in any of these can lead to plant diseases. By creating a biological sensor that can quickly provide soil status to plant owners, we can prevent plant diseases due to the lack of nutrients.

In the previous iGEM competitions, multiple teams have worked on nitrate and phosphate responsive promoters, but none of them attempted to provide a potassium responsive promoter. In view of this, our team is constructing a biological sensor in E. coli, which can detect NPK levels in the surrounding environment and give responses in the form of colors. In addition, we are characterizing the effects of a dual output system, in contrast to a single output system, in order to anticipate the expression of multiple outputs in a single system.

Learn more ...

The Journey of HKUST-Rice iGEM team

We are HKUST-Rice iGEM team. Our team is the first cross continental team in iGEM. Our team comprise of 32 student members, 18 of them are from the Hong Kong University of Science and technology and 14 of them are from Rice University. Benefit from forming a large joint team, we have members coming from different disciplinary which allow us to think from different perspectives. With the combined force form our members, we show the result of our work over the summer.

Taking the native metabolic pathway found in E. coli, we have designed a potassium ions (K+) regulated construct and a nitrate (NO3-) regulated construct that could potentially report the K+ and NO3- level in soil. Knowing that previous iGEM team also worked on nitrate regulated promoter and phosphate regulated promoter, our team utilize those promoter and further characterize in order to give more information about those promoters.

In addition, we are characterizing the effects of a dual output system, in contrast to a single output system, in order to predict the expression of multiple outputs in a single system.

When it comes to the real application method of our biosensors, our team considered 2 factors, Biological safety and feasibility. Biological safety are our priority, especially when our focus are related to the agricultural business. In our plan of applying the biosensor, we choose to deliver the biosensor in a cell-free system, which have no capability to sustain itself in the wild. However when we factor in the feasibility, we think that delivering our biosensor in common soil bacteria will be more practical. Hence we perform proof of concept experiments to demonstrate our concepts.

Besides staying in the lab, we also take every opportunity to engage the community to achieve 2 aims, to introduce synthetic biology to the younger community through debating and to interact with the community and gather their perceptions regarding biosensor and genetic engineering technology. Through engaging the community, we also gain valuable feedbacks and comments which we then use to improve our design.