Difference between revisions of "Team:Michigan/Description"

(Prototype team page)
 
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Michigan}}
+
{{Team:Michigan/navbar-Irina}}
 +
{{Team:Michigan/Navigation}}
 +
 
 
<html>
 
<html>
 +
  <style>
 +
    #sideMenu, #top_title {display:none;}
 +
    #content { padding:0px; width:100%;}
 +
    body {background-color:white; width:100%}
 +
    #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 +
    #top_menu_inside, #top_menu_14 { height:20px;}
 +
  
 +
    div.blue {
 +
        background-color: white;
 +
        color: white;
 +
        margin: 20px 0 20px 0;
 +
        padding: 20px;
 +
        border-size: 10px;
 +
        border-color:#00274c;
 +
        border-style: solid;
 +
        display: flex;
 +
    }
  
 +
    div.maize {
 +
      background-color: white;
 +
      color: white;
 +
      margin: 20px 0 20px 0;
 +
      padding: 20px;
 +
      border-size: 10px;
 +
      border-color:#ffd700;
 +
      border-style:solid;
 +
      display: flex;
 +
    }
  
<div class="column full_size judges-will-not-evaluate">
+
    h2 {
<h3>★  ALERT! </h3>
+
      font-family: 'Poiret One', cursive;
<p>This page is used by the judges to evaluate your team for the<a href="https://2016.igem.org/Judging/Medals"> improve a previous part or project gold medal criterion</a>. </p>
+
      font-size: 30px;
<p> Delete this box in order to be evaluated for this medal. See more information at <a href="https://2016.igem.org/Judging/Pages_for_Awards/Instructions"> Instructions for Pages for awards</a>.</p>
+
      color: black;
</div>
+
    }
 
+
   
 
+
    p {
<div class="column full_size">
+
        font-family: 'Poiret One', cursive;
 
+
        font-size: 20px;
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
        color: black;
 
+
        display: flex;
 
+
      }
<h5>What should this page contain?</h5>
+
<ul>
+
      div.container {
<li> A clear and concise description of your project.</li>
+
      padding-top: 75px;
<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>
+
    h1 {
</ul>
+
        font-family: 'Poiret One', cursive;
 
+
        font-size: 40px;
 
+
        color: black;
</div>
+
    }
 
+
  </style>
<div class="column full_size" >
+
 
+
<h5>Advice on writing your Project Description</h5>
+
 
+
<p>
+
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>
+
 
+
</div>
+
 
+
 
+
<div class="column half_size" >
+
 
+
<h5>References</h5>
+
<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 thought about your project and what works inspired you.</p>
+
 
+
</div>
+
 
+
 
+
<div class="column half_size" >
+
<h5>Inspiration</h5>
+
<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>
+
 
+
  
 +
  <body>
 +
    <div class = "container"> <h1 style="text-align:center; font-size: 75px;"><font face= "Poiret One">Project Description</font></h1>
 +
      <div class="row">
 +
        <div class="blue">
 +
          <div class="col-md-12">
 +
            <p style="text-align:center; font-size:20px;"><font face="verdana">
 +
              Last year, we were inspired by “Toehold switches: de-novo-designed regulators of gene expression” (Green, Silver, et al.) to create a paper-based gene network featuring an aptamer-based genetic switch that was capable of producing a colorimetric output in the presence of a chosen target protein. We iterated through two toehold-based switch designs based but were not able to detect our target protein at in vitro levels.
 +
             
 +
              <br><br>This year, we have completely redesigned our genetic switch in an attempt to further improve its specificity and effectiveness. Our new design features two unique aptamers that bind to the target protein and are designed for proximity-dependent ligation similarly to those  outlined in “Protein detection using proximity-dependent DNA ligation assays” (Fredriksson, Gullberg, et al.). Once ligated, the tails of the two aptamers express the alpha fragment of lacZ, which enables free floating lacZ to metabolize Xgal and create a blue colorimetric output.
  
 +
              <br><br>While we are testing this with Thrombin as the target protein, we believe that by changing the aptamers,  this system could be used to detect any target you choose, opening the doors for a wide range of diagnostic uses. It is our goal to use the technology outlined in “Paper-based synthetic gene networks” (Pardee, Green, et al.) to mount our dehydrated synthetic gene network onto paper test strips that could be cheaply and effectively used as diagnostic devices similar to those discussed in “Rapid, Low-Cost Detection of Zika Virus Using Programmable Biomolecular Components” (Pardee, Green, et al). This technology would particularly benefit the fight against tuberculosis, as cheap and accurate diagnosis is the largest hurdle to treatment of the disease in much of the world.
 +
            </font></p>
 +
          </div>
 +
        </div>
 +
      </div>
 +
    </div>
 +
  </body>
 
</html>
 
</html>

Latest revision as of 21:18, 18 October 2016

Project Description

Last year, we were inspired by “Toehold switches: de-novo-designed regulators of gene expression” (Green, Silver, et al.) to create a paper-based gene network featuring an aptamer-based genetic switch that was capable of producing a colorimetric output in the presence of a chosen target protein. We iterated through two toehold-based switch designs based but were not able to detect our target protein at in vitro levels.

This year, we have completely redesigned our genetic switch in an attempt to further improve its specificity and effectiveness. Our new design features two unique aptamers that bind to the target protein and are designed for proximity-dependent ligation similarly to those outlined in “Protein detection using proximity-dependent DNA ligation assays” (Fredriksson, Gullberg, et al.). Once ligated, the tails of the two aptamers express the alpha fragment of lacZ, which enables free floating lacZ to metabolize Xgal and create a blue colorimetric output.

While we are testing this with Thrombin as the target protein, we believe that by changing the aptamers, this system could be used to detect any target you choose, opening the doors for a wide range of diagnostic uses. It is our goal to use the technology outlined in “Paper-based synthetic gene networks” (Pardee, Green, et al.) to mount our dehydrated synthetic gene network onto paper test strips that could be cheaply and effectively used as diagnostic devices similar to those discussed in “Rapid, Low-Cost Detection of Zika Virus Using Programmable Biomolecular Components” (Pardee, Green, et al). This technology would particularly benefit the fight against tuberculosis, as cheap and accurate diagnosis is the largest hurdle to treatment of the disease in much of the world.