Difference between revisions of "Team:BostonU HW/Description"

 
(4 intermediate revisions by one other user not shown)
Line 9: Line 9:
 
           <div class="col-lg-10 col-lg-offset-1">
 
           <div class="col-lg-10 col-lg-offset-1">
 
         <div class="text-vertical-center" style="color: white;">
 
         <div class="text-vertical-center" style="color: white;">
             <h1>Fluigi Overview</h1>
+
             <h1>Neptune Overview</h1>
 
</div>
 
</div>
 
</div>
 
</div>
Line 15: Line 15:
 
</div>
 
</div>
  
 +
<div id="uses" class="col-lg-10 col-lg-offset-1">
 +
<h2 align="center"> What is Neptune? </h2>
 +
            <br>
 +
<h4> Neptune is a specify, design, and build end-to-end microfluidic development tool. The motivation for Neptune... </h4>
 +
<br>
  
 
+
        </div>
<div class="column full_size judges-will-not-evaluate">
+
<h3>★  ALERT! </h3>
+
<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>
+
<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>
+
 
</div>
 
</div>
 
 
<div class="column full_size">
 
 
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
 
 
 
<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>
 
 
 
 
</div>
 
</div>
  
<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 id="uses" class="col-lg-10 col-lg-offset-1">
 +
<h2 align="center"> Where can we use Microfluidics? </h2>
 +
            <br>
 +
<li>Synthetic Biology:
 +
<a href="http://pubs.rsc.org/en/content/articlepdf/2014/lc/c4lc00509k"> 'Lab on a Chip', 2014</a>
 +
</li>
 +
</br>
 +
<li>Experiments to monitor precise control of the number and concentration of input:
 +
<a href="http://stke.sciencemag.org/content/5/213/ra17.full"> 'Diverse Sensitivity Thresholds in Dynamic Signaling Response by Social Amoebae', 2012</a>
 +
</li>
 +
</br>
 +
<li>Single-cell tracking:
 +
<a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4836382"> 'Microfluidics for Synthetic Biology: From Design to Execution'</a>
 +
</li>
 +
</br>
 +
<li>Microchemostat for environmental control:
 +
<a href="http://science.sciencemag.org/content/309/5731/137.full">'Long-Term Monitoring of Bacteria Undergoing Programmed Population Control in a Microchemostat', 2005</a>
 +
</li>
 +
<br>
 +
        </div>
 +
</div>
 
</div>
 
</div>
  
  
<div class="column half_size" >
 
  
<h5>References</h5>
+
</body>
<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>
+
</html>
<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>
+
  
 
+
{{BUHW2016Footer}}
 
+
</html>
+

Latest revision as of 16:20, 22 July 2016

Neptune Overview

What is Neptune?


Neptune is a specify, design, and build end-to-end microfluidic development tool. The motivation for Neptune...


Where can we use Microfluidics?


  • Synthetic Biology: 'Lab on a Chip', 2014

  • Experiments to monitor precise control of the number and concentration of input: 'Diverse Sensitivity Thresholds in Dynamic Signaling Response by Social Amoebae', 2012

  • Single-cell tracking: 'Microfluidics for Synthetic Biology: From Design to Execution'

  • Microchemostat for environmental control: 'Long-Term Monitoring of Bacteria Undergoing Programmed Population Control in a Microchemostat', 2005