Difference between revisions of "Team:Washington/Demonstrate"

Line 1: Line 1:
{{Washington}}
+
{{Washington/Includes}}
  
<html>
+
<html> <body class="bg-light">
 +
<!-- REQUIRED INITIALIZERS -->
 +
<!-- pageIdentifier can be one of the headings on the navigation bar -->
 +
<!-- Home, Wet Lab, Dry Lab, Human Practices, Protocols, Team -->
 +
<!-- Capitalization important -->
 +
<div class="pageIdentifier" id="Dry Lab"></div>
  
<div class="clear"></div>
+
<!-- This is only for javascript. No need to mess with it if the page has content -->
 +
<!-- Only special pages will require the use of this -->
 +
<div class="subPageIdentifier" id="Demonstrations"></div>
  
 +
<!-- This div is necessary in order to load the navigation bar -->
 +
<div id="customNavbar"></div>
  
<div class="column full_size">
+
<!-- Don't mess with this top level div -->
<h1>Demonstrate</h1>
+
<div class="container-fluid bg-light" style="padding: 0px">
<h3>Gold Medal Criterion #4</h3>
+
<!-- Don't mess with the above -->
  
<p>
 
Teams that can show their system working under real world conditions are usually good at impressing the judges in iGEM. To achieve gold medal criterion #4, convince the judges that your project works. There are many ways in which your project working could be demonstrated, so there is more than one way to meet this requirement. This gold medal criterion was introduced in 2016, so check our what 2016 teams did to achieve a their gold medals!
 
</p>
 
  
<p>
 
Please see the <a href="https://2017.igem.org/Judging/Medals">2017 Medals Page</a> for more information.
 
</p>
 
  
 +
<!-- CONTENT EDITING STARTS INSIDE THIS DIV WITH ID "contentInsert"! -->
 +
<!-- IMPORTANT! -->
 +
<!-- <div id="nameBar">xyz</div> will make xyz appear large on top of content -->
 +
<!-- For images, please use the following format, and include alt text (Just a two word or so description of the image)
 +
<div class="contentImage rounded-circle" style="height: ##px; width: ##px"><img src="" alt="" /></div>
 +
-->
 +
<!-- For the new sections, use the format:
 +
<div id="xyz" class="jumpSection"></div>
 +
<h4 class="subSection">xyz</h4>
 +
h4 can be h1, h2, etc. 
 +
    IT IS VERY IMPORTANT THAT THE ID IS THE SAME AS THE HEADER, INCLUDING CAPITALIZATION!
 +
    IT IS ALSO VERY IMPORTANT TO INCLUDE THE "jumpSection" and "subSection" CLASS, OR IT WON'T BE DETECTED
 +
    BY THE JAVASCRIPT CODE-->
  
</div>
+
<!-- You have complete creative freedom. I would highly suggest learning the bootstrap
 +
grid system API -->
  
 +
<!-- DUPLICATE THIS ENTIRE HTML FILE TO A NEW FILE -->
  
<div class="column half_size">
+
<div id="contentInsert" style="margin: 3%">
 +
  <div id="nameBar">Demonstrations</div>
 +
  <br /><br />
 +
  <hr />
  
<h4> What should we do for our demonstration?</h4>
+
  <p>Because engineered organisms cannot be brought to the competition and our yeast are still in development, we are working on a demonstration of our closed-loop system using colored pH indicators as a proxy for the violacein system. </p>
  
<h5> Standard teams </h5>
+
<p>We have ran some preliminary tests to make sure that our color sensor is working. Using different concentrations of colored dyes in solution, we have shown that the color sensor is working as expected with the software we have written.</p>
  
<p>
+
<img class="contentImage largeImage" src="https://static.igem.org/mediawiki/2017/b/be/T--Washington--3DPlot.jpeg"/><div class="container" style="text-align: center">Figure: 3D plot of our Color test.</div><br /><br />
If you have built a proof of concept system, you can demonstrate it working under real world conditions. If you have built a biological device that is intended to be a sensor, can you show it detecting whatever it is intended to sense. If it is intended to work in the field, you can show how this might work using a simulated version in the lab, or a simulation of your device in the field.<strong> Please note biological materials must not be taken out of the lab</strong>.
+
<p>We are currently working on:</p>
</p>
+
<ul>
</div>
+
<li>Fine-turning our turbidity sensor</li>
 +
<li>Fine-tuning our syringe motors for functional use</li>
 +
<li>Testing our hardware system with pH indicators</li>
 +
</ul>
  
<div class="column half_size">
+
<p>We hope to post on our <a href="https://www.facebook.com/UWiGEMTeam/">Facebook page</a> once we get our system running. Also, please visit our exhibit space at the Jamboree to see it in action!</p>
 
+
 
<br>
+
</div>
<h5> Special track teams </h5>
+
</div>
 
+
<p>
+
Special track teams can achieve this medal criterion by bringing their work to the Jamboree and showcasing it in the track event. Art & Design, Measurement, Hardware and Software tracks will all have showcase events at the Giant Jamboree.<strong> Please note biological materials must not be taken out of the lab</strong>.
+
</p>
+
 
+
 
+
</div>
+
  
  
 +
</body>
 +
 +
<footer>
 +
<div id="foot"></div>
 +
</footer>
  
 
</html>
 
</html>

Revision as of 03:27, 2 November 2017

Washington iGEM

Demonstrations



Because engineered organisms cannot be brought to the competition and our yeast are still in development, we are working on a demonstration of our closed-loop system using colored pH indicators as a proxy for the violacein system.

We have ran some preliminary tests to make sure that our color sensor is working. Using different concentrations of colored dyes in solution, we have shown that the color sensor is working as expected with the software we have written.

Figure: 3D plot of our Color test.


We are currently working on:

  • Fine-turning our turbidity sensor
  • Fine-tuning our syringe motors for functional use
  • Testing our hardware system with pH indicators

We hope to post on our Facebook page once we get our system running. Also, please visit our exhibit space at the Jamboree to see it in action!