Difference between revisions of "Team:WashU StLouis/Description"

(Prototype team page)
 
 
Line 1: Line 1:
{{WashU_StLouis}}
+
{{:Team:WashU_StLouis/Header}}
 
<html>
 
<html>
  
<h2> Project Description </h2>
+
  <!-- Navigation -->
 +
  <nav class="navbar navbar-default navbar-fixed-top">
 +
    <div class="container">
 +
      <!-- Brand and toggle get grouped for better mobile display -->
 +
      <div class="navbar-header page-scroll">
 +
        <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
 +
          <span class="sr-only">Toggle navigation</span>
 +
          <span class="icon-bar"></span>
 +
          <span class="icon-bar"></span>
 +
          <span class="icon-bar"></span>
 +
        </button>
 +
        <a class="navbar-brand page-scroll" href="#page-top">Nitrogenius</a>
 +
      </div>
  
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
      <!-- Collect the nav links, forms, and other content for toggling -->
<br />
+
      <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
 +
        <ul class="nav navbar-nav navbar-right">
 +
          <li class="hidden">
 +
            <a href="#page-top"></a>
 +
          </li>
 +
          <li>
 +
            <a class="page-scroll" href="#description">Description</a>
 +
          </li>
 +
          <li>
 +
            <a href="mailto:ayekedavidr@wustl.edu?subject=Bug">Report Bugs</a>
 +
          </li>
 +
        </ul>
 +
      </div>
 +
      <!-- /.navbar-collapse -->
 +
    </div>
 +
    <!-- /.container-fluid -->
 +
  </nav>
  
<h5>What should this page contain?</h5>
 
<ul>
 
<li> A clear and concise description of your project.</li>
 
<li>A detailed explanation of why your team chose to work on this particular project.</li>
 
<li>References and sources to document your research.</li>
 
<li>Use illustrations and other visual resources to explain your project.</li>
 
</ul>
 
  
 +
  <!-- Project Overview -->
 +
  <!-- Main container -->
 +
  <div class="container">
 +
    <section id="description"  class="bg-light-gray row sectionNum1 sectionNum2 sectionNum3 sectionNum4 sectionNum5 sectionNum6 ">
 +
      <div class="container">
 +
        <div class="row">
 +
          <h4 class="text-muted section-heading">IGEM 2015 Project Description.</h4>
 +
          <p>
 +
            The 2014 WashU iGEM team successfully transferred the nif cluster from Cyanothece 51142 to E. coli. However, the nitrogenase activity they measured was minimal. Therefore, the WashU/Penn State 2015 team dedicated itself to increasing the nitrogenase activity of last year’s E. coli strain by knocking down and overexpressing certain genes on the nif-containing plasmid. Additionally, we are using genome-scale metabolic modeling to guide potential genetic interventions and facilitate nitrogen fixation in E. coli. We are performing a systematic analysis of metabolites and genes in our model to optimize nitrogenase activity.
 +
          </p>
 +
          <p>
 +
            A few weeks into our work, a member of our lab had trouble repeating the 2014 results and we began to consider the notion that E. coli may be incompatible with components of the plasmid—whose parts come directly from Cyanothece 51142—at the transcriptional, translational, or post-translational levels. After an evaluation of our remaining time and resources, we decided to construct a more minimal nif cluster for E. coli in order to reduce the effects of any native regulation present in the original plasmid we used. We plan to continue our analysis of the nif cluster using overexpression, knockdown, and metabolic engineering.
 +
          </p>
 +
          <p>
 +
            Our team is part of a larger project that is seeking to confer nitrogen fixation capabilities to a non-diazotrophic cyanobacterium, Synechocystis pp. 6803. Synechocystis is evolutionarily related by the endosymbiotic theory to plant chloroplasts, so a nitrogen-fixing Synechocystis could be used as a model to engineer plants that fix their own nitrogen. We hope that the results of this year’s iGEM team will be useful to the researchers working on The Nitrogen Project since E. coli is a well-characterized, fast-growing model organism.
 +
          </p>
 +
          <br>
  
<br />
+
        </div>
<h4>Advice on writing your Project Description</h4>
+
      </div>
 +
    </section>
  
<p>
+
  </div>
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.
+
</p>
+
  
<p>
 
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
 
</p>
 
  
 
<br />
 
<h4>References</h4>
 
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you though about your project and what works inspired you.</p>
 
 
 
 
<h4>Inspiration</h4>
 
<p>See how other teams have described and presented their projects: </p>
 
 
<ul>
 
<li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
 
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
 
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
 
</ul>
 
 
</div>
 
 
</html>
 
</html>
 +
{{:Team:WashU_StLouis/Footer}}

Latest revision as of 00:36, 18 September 2015

Washington University - Penn State iGEM

Welcome To Our Website!
WashU and Penn State   iGEM 2015
Project Description Let's Talk Apply for the 2016 iGEM Team!

IGEM 2015 Project Description.

The 2014 WashU iGEM team successfully transferred the nif cluster from Cyanothece 51142 to E. coli. However, the nitrogenase activity they measured was minimal. Therefore, the WashU/Penn State 2015 team dedicated itself to increasing the nitrogenase activity of last year’s E. coli strain by knocking down and overexpressing certain genes on the nif-containing plasmid. Additionally, we are using genome-scale metabolic modeling to guide potential genetic interventions and facilitate nitrogen fixation in E. coli. We are performing a systematic analysis of metabolites and genes in our model to optimize nitrogenase activity.

A few weeks into our work, a member of our lab had trouble repeating the 2014 results and we began to consider the notion that E. coli may be incompatible with components of the plasmid—whose parts come directly from Cyanothece 51142—at the transcriptional, translational, or post-translational levels. After an evaluation of our remaining time and resources, we decided to construct a more minimal nif cluster for E. coli in order to reduce the effects of any native regulation present in the original plasmid we used. We plan to continue our analysis of the nif cluster using overexpression, knockdown, and metabolic engineering.

Our team is part of a larger project that is seeking to confer nitrogen fixation capabilities to a non-diazotrophic cyanobacterium, Synechocystis pp. 6803. Synechocystis is evolutionarily related by the endosymbiotic theory to plant chloroplasts, so a nitrogen-fixing Synechocystis could be used as a model to engineer plants that fix their own nitrogen. We hope that the results of this year’s iGEM team will be useful to the researchers working on The Nitrogen Project since E. coli is a well-characterized, fast-growing model organism.