Difference between revisions of "Team:Edinburgh/Description"

(Prototype team page)
 
Line 1: Line 1:
−
{{Edinburgh}}
+
{{Edigem15_Design}}
 
<html>
 
<html>
  
−
<h2> Project Description </h2>
 
  
−
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
    <head>
−
<br />
+
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
 +
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
 +
    </head>
  
−
<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>
 
  
 +
<body>
  
−
<br />
+
<!-- menu -->
−
<h4>Advice on writing your Project Description</h4>
+
      <div class="navbar-wrapper">
 +
        <div class="container">
 +
        <nav class="navbar transparent navbar-default navbar-fixed-top">
 +
          <div class="container">
 +
            <div class="navbar-header">
 +
              <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
 +
                <span class="sr-only">Toggle navigation</span>
 +
                <span class="icon-bar"></span>
 +
                <span class="icon-bar"></span>
 +
                <span class="icon-bar"></span>
 +
              </button>
 +
            </div>
 +
            <div id="navbar" class="navbar-collapse collapse">
 +
              <ul class="nav navbar-nav">
 +
                <li class="active">
 +
                  <a href="https://2015.igem.org/Team:Edinburgh">Home</a></li>
 +
                  <li class="dropdown">
 +
                    <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Project<span class="caret"></span></a>
 +
                    <ul class="dropdown-menu" role="menu">
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Description">Description</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Experiments">Experiments</a> </li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Project/Protocols">Protocols</a> </li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Results">Results</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Design">Design</a></li>
 +
                    </ul>
 +
                  </li>
 +
                  <li class="dropdown">
 +
                    <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Parts<span class="caret"></span></a>
 +
                    <ul class="dropdown-menu" role="menu">
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Parts">Team Parts</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Basic_Part">Basic Parts</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Composite_Part">Composite Parts</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Part_Collection">Part Collection</a> </li>
 +
                    </ul>
 +
                  </li>
 +
                  <li><a href="https://2015.igem.org/Team:Edinburgh/Attributions">Attributions</a></li>
 +
                  <li class="dropdown">
 +
                    <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Policy and Practices<span class="caret"></span></a>
 +
                    <ul class="dropdown-menu" role="menu">
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Practices">Our Story</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Safety">Safety</a> </li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Legality">Legality</a> </li>
 +
                    </ul>
 +
                  </li>
 +
                  <li><a href="https://2015.igem.org/Team:Edinburgh/Modeling">Modeling</a></li>
 +
                  <li class="dropdown">
 +
                    <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">InterLab<span class="caret"></span></a>
 +
                    <ul class="dropdown-menu" role="menu">
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/InterLab">InterLab</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/InterLabBook">LabBook</a> </li>
 +
                    </ul>
 +
                  </li>
 +
                  <li><a href="software.html">Software</a></li>
 +
                  <li><a href="entrepreneurship.html">Entrepreneurship</a></li>
 +
                  <li><a href="collaborations.html">Collaborations</a></li>
 +
                  <li class="dropdown">
 +
                    <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Notebook<span class="caret"></span></a>
 +
                    <ul class="dropdown-menu" role="menu">
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Notebook/HeroinPurity">Heroin Purity</a></li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Notebook/PMADetection">PMA Detection</a> </li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Notebook/DNPDetection">DNP Detection</a> </li>
 +
                      <li><a href="https://2015.igem.org/Team:Edinburgh/Notebook/FluidDynamics">Fluid Dynamics</a> </li>
 +
                    </ul>
 +
                  </li>
 +
                </ul>
 +
              </div>
 +
            </div>
 +
          </nav>
 +
        </div>
 +
      </div>
 +
    <!-- End of menu  -->
  
−
<p>
+
      <header class="intro">
−
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.
+
        <div class="intro-body">
−
</p>
+
          <div class="container">
 +
            <div class="row">
 +
              <div class="col-md-12">
 +
                <h1 class="brand-heading">Design</h1>
 +
                <p class="intro-text">
 +
<br>
 +
<br>
 +
<br>
 +
                </p>
 +
              </div>
 +
            </div>
 +
          </div>
 +
        </div>
 +
      </header>
  
−
<p>
+
      <section class="col-2 ss-style-roundedsplit">
−
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.
+
        <div class="column">
−
</p>
+
          <span class="icon icon-images">
 +
            <img src="whiteneedle.png">
 +
          </span>
 +
        </div>
 +
        <div class="column text">
 +
          <h2>Overview</h2>
 +
          <p>
 +
Over the course of the summer we talked to potential end users, NGO’s, representative and academics about their opinion on our device, What they wanted out of it and how they saw our device being implemented in our society. These conversation really helped us evolve our designs and come with the simple but elegant design we have right now.  
 +
          </p>
  
 +
         
 +
        </div>
 +
      </section>
 +
      <section class="color ss-style-bigtriangle">
 +
                  <p>
 +
Another big part of our design process was trying to computationally model how our biosensor will behave and helping us understand where are design might lack. Our early conversations made us realise for our biosensor to be better than the current methods , it will have to be easy to use, portable cheap to manufacture and having it paper based was the answer to that.
 +
        </p>
 +
      </section>
 +
      <section class="col-2 ss-style-doublediagonal">
 +
        <div class="column">
 +
          <span class="icon icon-images">
 +
            <img src="whiteneedle2.png">
 +
          </span>
 +
        </div>
 +
        <div class="column text">
 +
          <h2>Prototype 1</h2>
 +
          <p>
 +
Once we decided on to use paper-based biosensor we set out to talk to more people. //link A talk with Susan Deacon made us realise we will need to have multiple tests on one strip, That’s when we found inspiration in the design made by //reference *George Whiteside’s lab for a glucose biosensor*. In this design we would have channels of paper where water will diffuse separated by a hydrophobic material like wax or plastics.
 +
          </p>
 +
          <p>
 +
But there was one problem with this design, The distribution of the solution was not uniform #which really created some problems.
 +
          </p>
 +
        </div>
 +
      </section>
 +
      <section class="color ss-style-bigtriangle" >
 +
        <h2>Prototype 2 </h2>
 +
        <p>
 +
We brainstormed and tried to make our biosensor a bit more simple so that we could have uniform distribution throughout the strip and we came up with this design. This strip would have been of the size of a microscope slide. The Strips you see in centre of the biosensor would again be kept apart by a hydrophobic material and the biosensor would be places inside them.
 +
      </p>
 +
      <p>
 +
Although this design meant we could easily predict the diffusion of the liquid as it was all uniform, it did not do well in concentrating the colour produced at one place. It was just too spread out.
 +
//Modelling movie
 +
      </p>
 +
      </section>
 +
        <section class="col-2 ss-style-doublediagonal">
 +
        <div class="column">
 +
          <span class="icon icon-images">
 +
            <img src="whiteneedle.png">
 +
          </span>
 +
        </div>
 +
        <div class="column text">
 +
          <h2>Prototype 3 </h2>
 +
          <p>
 +
With the help of our modelling efforts it did not take us long come up with a new solution. Just make some cavities in the design we had that would contain the colour produced.
 +
          </p>
 +
          <p>
 +
At this time we really did think we had a winner, but //link talking to more experts made us realise  somewhere we could push ourself even more. Reducing the amount of liquid used as the end users might not want to waste a lot of their drug. Although this design only used about 150µl of solution we felt we could do better
 +
          </p>
 +
        </div>
 +
      </section>
 +
      <section class="color ss-style-bigtriangle">
 +
        <h2>Final Biosensor Design</h2>
 +
        <p>
 +
At this time we looked at some our older designs and that when we came up with our current design. This strip only required a tenth of the solution we were using before Uniform distribution, concentrated colours and minimalistic liquid requirements, it has it all.
 +
        </p>
 +
        <p>
 +
We were not done yet though, //link A talk with Adam Winstoke gave us the idea that we could increase the ease of use and reliability of results by making a smartphone application and we set out a goal to make that happen
 +
        </p>
 +
      </section>
  
−
<br />
+
      <section class="col-2 ss-style-doublediagonal">
−
<h4>References</h4>
+
        <div class="column">
−
<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>
+
          <span class="icon icon-images">
 +
            <img src="whiteneedle.png">
 +
          </span>
 +
        </div>
 +
        <div class="column text">
 +
          <h2>Completing the Device</h2>
 +
          <p>
 +
As soon as we started thinking on this idea we realised there were some hurdles that had to be overcome. For the results to be accurate the picture had to be in a fixed position. Also we needed to control the amount of light that the photo is taken in. The camera had to be positioned at a height more than the minimum focal length as well. At the same time we had to be true to our original intentions of ease of use, cost-effectiveness and portability.  
 +
          </p>
  
 +
        </div>
 +
      </section>
 +
        <section class="ss-style-bigtriangle">
 +
        <p>
 +
<br>
 +
        </p>
 +
      </section>
  
−
 
+
   
−
<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>
 
</div>
 +
</body>
 
</html>
 
</html>

Revision as of 09:52, 3 September 2015

gh

Design




Overview

Over the course of the summer we talked to potential end users, NGO’s, representative and academics about their opinion on our device, What they wanted out of it and how they saw our device being implemented in our society. These conversation really helped us evolve our designs and come with the simple but elegant design we have right now.

Another big part of our design process was trying to computationally model how our biosensor will behave and helping us understand where are design might lack. Our early conversations made us realise for our biosensor to be better than the current methods , it will have to be easy to use, portable cheap to manufacture and having it paper based was the answer to that.

Prototype 1

Once we decided on to use paper-based biosensor we set out to talk to more people. //link A talk with Susan Deacon made us realise we will need to have multiple tests on one strip, That’s when we found inspiration in the design made by //reference *George Whiteside’s lab for a glucose biosensor*. In this design we would have channels of paper where water will diffuse separated by a hydrophobic material like wax or plastics.

But there was one problem with this design, The distribution of the solution was not uniform #which really created some problems.

Prototype 2

We brainstormed and tried to make our biosensor a bit more simple so that we could have uniform distribution throughout the strip and we came up with this design. This strip would have been of the size of a microscope slide. The Strips you see in centre of the biosensor would again be kept apart by a hydrophobic material and the biosensor would be places inside them.

Although this design meant we could easily predict the diffusion of the liquid as it was all uniform, it did not do well in concentrating the colour produced at one place. It was just too spread out. //Modelling movie

Prototype 3

With the help of our modelling efforts it did not take us long come up with a new solution. Just make some cavities in the design we had that would contain the colour produced.

At this time we really did think we had a winner, but //link talking to more experts made us realise somewhere we could push ourself even more. Reducing the amount of liquid used as the end users might not want to waste a lot of their drug. Although this design only used about 150µl of solution we felt we could do better

Final Biosensor Design

At this time we looked at some our older designs and that when we came up with our current design. This strip only required a tenth of the solution we were using before Uniform distribution, concentrated colours and minimalistic liquid requirements, it has it all.

We were not done yet though, //link A talk with Adam Winstoke gave us the idea that we could increase the ease of use and reliability of results by making a smartphone application and we set out a goal to make that happen

Completing the Device

As soon as we started thinking on this idea we realised there were some hurdles that had to be overcome. For the results to be accurate the picture had to be in a fixed position. Also we needed to control the amount of light that the photo is taken in. The camera had to be positioned at a height more than the minimum focal length as well. At the same time we had to be true to our original intentions of ease of use, cost-effectiveness and portability.