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

Line 1: Line 1:
−
{{BUHW2016}}
+
{{Template:BUHW2016_NavBar}}
 +
 
 +
 
 +
{{Template:BUHW2016_Bootstrap}}
 
<html>
 
<html>
 +
<head>
 +
<style>
 +
 +
 +
/********************************* DEFAULT WIKI SETTINGS  ********************************/
 +
 +
  #sideMenu, #top_title {display:none;}
 +
  #content { padding:0px; width:100%; margin-top:-12px; margin-left:0px;}
 +
  body {background-color:white; }
 +
  #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 +
 +
 +
 +
@font-face {
 +
    font-family: openSans;
 +
    src: url(https://static.igem.org/mediawiki/2016/1/1e/T--BostonU_HW--openSansLight_rcwolf.ttf);
 +
}
 +
 +
 +
html,body
 +
{
 +
    width: 100%;
 +
    min-width: 100%;
 +
    height: 100%;
 +
    margin: 0px;
 +
    padding: 0px;
 +
    overflow-x: hidden;
 +
}
 +
 +
 +
body{
 +
background-color: white;
 +
}
 +
 +
* {
 +
font-family: openSans !important;
 +
}
 +
 +
 +
.navbar {
 +
  background-color: black;
 +
  border-color: black;
 +
margin-top: 10px;
 +
 
 +
}
 +
 +
 +
 +
.navbar-default .navbar-header .navbar-brand,
 +
.navbar-default .navbar-header .navbar-brand:hover,
 +
.navbar-default .navbar-header .navbar-brand:focus {
 +
      color: white;
 +
  }
 +
  .navbar-default .nav > li > a,
 +
  .navbar-default .nav > li > a:focus {
 +
      color: white;
 +
      font-size: medium;
 +
  }
 +
  .navbar-default .nav > li > a:hover,
 +
  .navbar-default .nav > li > a:focus:hover {
 +
      color: white;
 +
      font-size: medium;
 +
  }
 +
  .navbar-default.affix {
 +
      background-color: white;
 +
      border-color: white;
 +
  }
 +
 +
 +
  /*  Animated Underlining For Menu Items  */
 +
.dropbtn {
 +
  display: inline-block;
 +
  position: relative;
 +
  padding-bottom: 3px;
 +
}
 +
.dropbtn:after {
 +
  content: '';
 +
  display: block;
 +
  margin: auto;
 +
  height: 2px;
 +
  width: 0px;
 +
  background: transparent;
 +
  transition: width .5s ease, background-color .5s ease;
 +
}
 +
.sliding-middle-out:hover > .dropbtn:after {
 +
  width: 100%;
 +
  background: white;
 +
}
 +
 +
 +
 +
 +
 +
/*  Dropdown Menu Functionality  */
 +
/* Style The Dropdown Button */
 +
.dropbtn {
 +
    color: white;
 +
    border: none;
 +
    cursor: pointer;
 +
}
 +
 +
/* The container <div> - needed to position the dropdown content */
 +
.dropdown {
 +
    position: relative;
 +
    display: inline-block;
 +
}
 +
 +
/* Dropdown Content (Hidden by Default) */
 +
.dropdown-content {
 +
    display: none;
 +
    position: absolute;
 +
    background-color: rgba(249,249,249,0.4);
 +
    min-width: 160px;
 +
}
 +
 +
/* Links inside the dropdown */
 +
.dropdown-content a {
 +
    color: black;
 +
    font-size: 15px;
 +
    padding: 10px 16px;
 +
    text-decoration: none;
 +
    display: block;
 +
}
 +
 +
/* Change color of dropdown links on hover */
 +
.dropdown-content a:hover {background-color: #f1f1f1}
 +
 +
/* Show the dropdown menu on hover */
 +
.dropdown:hover .dropdown-content {
 +
    display: block;
 +
}
 +
 +
.paddedNav{
 +
padding-left: 23px;
 +
padding-right: 23px;
 +
padding-bottom: 5px;
 +
}
 +
 +
 +
 +
 +
 +
 +
</style>
 +
 +
 +
</head>
 +
 +
 +
 +
 +
 +
  
  
  
 
<body>
 
<body>
−
<div class="services bg-primary">
+
 
−
<div class="row text-center">
+
<header id="top" class="header">
−
          <div class="col-lg-10 col-lg-offset-1">
+
 
−
         <div class="text-vertical-center" style="color: white;">
+
<nav class="navbar navbar-default navbar-fixed-top" style="max-height: 70px !important;">
−
            <h1>Project Build</h1>
+
  <div class="container-fluid paddedNav">
−
</div>
+
    <!-- Brand and toggle get grouped for better mobile display -->
 +
    <div class="navbar-header">
 +
      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1" aria-expanded="false">
 +
         <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" href="https://2016.igem.org/Team:BostonU_HW"><img src="https://static.igem.org/mediawiki/2016/9/97/T--BostonU_HW--NeptuneLogo_rcwolf.png" height="38" width="55" style="display: inline-block; padding-right: 17px; ">BU HW 2016</a>
 +
    </div>
 +
 
 +
    <!-- Collect the nav links, forms, and other content for toggling -->
 +
    <div class="collapse navbar-collapse " >
 +
      <ul class="nav navbar-nav navbar-right">
 +
        <li class="sliding-middle-out dropdown">
 +
            <a href="#" class="dropbtn">TEAM </a>
 +
            <div class="dropdown-content">
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Team">Meet the Team </a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Attributions">Attributions</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Collaborations">Collaborations</a>
 +
            </div>
 +
        </li>
 +
        <li class="sliding-middle-out dropdown">
 +
            <a href="#" class="dropbtn">PROJECT</a>
 +
            <img src="https://static.igem.org/mediawiki/2016/5/58/T--BostonU_HW--indexTriangle_rcwolf.png" width="36" height="18" style="margin-bottom: 0 !important; margin-top: 0; padding-bottom: 0 !important; border: none; display: block; margin: 0 auto;">
 +
            <div class="dropdown-content">
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Results">Results</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Demonstrate">Project Build</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Proof">Application</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Design">Documentation</a>
 +
            </div>
 +
        </li>
 +
        <li class="sliding-middle-out dropdown">
 +
            <a href="#" class="dropbtn">NOTEBOOK</a>
 +
            <div class="dropdown-content">
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Notebook">Timeline</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Experiments">Experiments</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Safety">Safety</a>
 +
            </div>
 +
        </li>
 +
        <li class="sliding-middle-out dropdown">
 +
            <a href="https://2016.igem.org/Team:BostonU_HW/Human_Practices" class="dropbtn">HUMAN PRACTICES</a>
 +
            <div class="dropdown-content">
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/HP/Silver">Silver</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/HP/Gold">Gold</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Integrated_Practices">Integrated Practices</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Engagement">Engagement</a>
 +
            </div>
 +
        </li>
 +
        <li class="sliding-middle-out dropdown">
 +
            <a href="#" class="dropbtn">AWARDS</a>
 +
            <div class="dropdown-content">
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Hardware">Hardware</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Software">Software</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Measurement">Measurement</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Model">Model</a>
 +
            </div>
 +
        </li>
 +
      </ul>
 +
    </div><!-- /.navbar-collapse -->
 +
  </div><!-- /.container-fluid -->
 +
</nav>
 +
 
 +
 
 
</div>
 
</div>
 +
 +
 +
 +
</body>
 +
 +
 +
 +
<html>
 +
 +
 +
 +
 +
 +
 +
<html>
 +
 +
<style>
 +
 +
  html {
 +
    background-color: #D2D2D2;
 +
  }
 +
  body {
 +
    background-color: #D2D2D2;
 +
  }
 +
 
 +
  #greyWrapper {
 +
    padding-top: 120px;
 +
    background-color: #D2D2D2;
 +
    margin: 0px 0px 40px 0px;
 +
    min-height: 1000px;
 +
  }
 +
  #pageTitle {
 +
    margin-left: 25px;
 +
    padding-bottom: 16px;
 +
  }
 +
  .pageBanner {
 +
    position: fixed;
 +
    color:black;
 +
    background-color:white;
 +
    width:100%;
 +
    top:70px;
 +
    z-index: 1;
 +
  }
 +
  .densmoreCard {
 +
    background-color: white;
 +
    padding:0;
 +
  }
 +
  .advisorCard {
 +
    background-color: white;
 +
  }
 +
  .miniBio {
 +
    padding-left: 20px;
 +
    padding-right:20px;
 +
    padding-bottom:30px;
 +
  }
 +
  .bioIcon {
 +
    border: none;
 +
    display: block;
 +
    margin-top: -24px;
 +
    margin-bottom: -20px;
 +
    margin-left: auto;
 +
    margin-right: auto;
 +
  }
 +
</style>
 +
 +
 +
 +
<body>
 +
<!-- PAGE TITLE BANNER -->
 +
  <div id="greyWrapper">   
 +
    <div class="pageBanner">
 +
      <h3 id="pageTitle">PROJECT BUILD</h3>
 +
    </div>
 +
    <br><br><br><br>
 +
   
 +
   
 +
 +
 +
<div class="row" style="padding-top:50px; padding-bottom:50px;">
 +
  <div class="col-md-1"></div>
 +
  <div class="col-md-8" style="font-size: 4em; line-height: 130%; ">Considerations for Replication | Neptune is built to be modular, accessible, parametric, and expandable.</div>
 +
  <div class="col-md-3"></div>
 
</div>
 
</div>
−
</div>
 
−
<br></br>
 
  
 +
<div class="row" style="padding-top:100px; padding-bottom:100px;">
 +
  <div class="col-md-1"></div>
 +
  <div class="col-md-10" style="background-color: white; padding-top:50px; padding-bottom:50px;">
  
  
 +
    <div class="row">
 +
      <div class="col-md-3">
 +
      </div>
 +
      <div class="col-md-9">
 +
        <div style="font-size: 2em; line-height: 150%; color:#355E62;">OPEN SOURCE</div>
 +
      </div>
 +
    </div>
 +
    <div class="row" style="padding-top:20px; padding-bottom:20px;">
 +
      <div class="col-md-3">
 +
        <img src="https://static.igem.org/mediawiki/2016/8/8e/T--BostonU_HW--MakerFluidicsLogo_rcwolf.png" width="80%" style="padding-left:20px">
 +
      </div>
 +
      <div class="col-md-9">
 +
        MakerFluidics is an accessible, inexpensive microfluidic fabrication technique used to manufacture microfluidic chips. A user will use an SVG file to mill out both the control and flow layers of a microfluidic chip. Then he or she will use these 2 layers to sandwich a piece of PDMS and vacuum the chip to create a seal. Through Neptune, the user is encouraged to use this fabrication infrastructure to make their chip so that they may rapidly prototype many chips inexpensively for any iterations of their experiment and easily control their microfluidic system through the Neptune interface.
 +
      </div>
 +
    </div>
  
−
<div class="column half_size" >
+
    <br>
  
−
<h5>Inspiration</h5>
 
−
<p>See how other teams presented their results.</p>
 
−
<ul>
 
−
<li><a href="https://2014.igem.org/Team:TU_Darmstadt/Results/Pathway">2014 TU Darmstadt </a></li>
 
−
<li><a href="https://2014.igem.org/Team:Imperial/Results">2014 Imperial </a></li>
 
−
<li><a href="https://2014.igem.org/Team:Paris_Bettencourt/Results">2014 Paris Bettencourt </a></li>
 
−
</ul>
 
  
 +
 +
    <div class="row">
 +
      <div class="col-md-3">
 +
      </div>
 +
      <div class="col-md-9">
 +
        <div style="font-size: 2em; line-height: 150%; color:#355E62;">INSTRUCTIONAL RESOURCES</div>
 +
      </div>
 +
    </div>
 +
    <div class="row" style="padding-top:20px; padding-bottom:20px;">
 +
      <div class="col-md-3">
 +
        <img src="https://static.igem.org/mediawiki/2016/2/2f/T--BostonU_HW--FluigiLogo_rcwolf.png" width="90%" style="padding-left:20px">
 +
      </div>
 +
      <div class="col-md-9">
 +
        [Priya: Build & Assembly pages]
 +
      </div>
 +
    </div>
 +
 +
    <br>
 +
 +
        <div class="row">
 +
      <div class="col-md-3">
 +
      </div>
 +
      <div class="col-md-9">
 +
        <div style="font-size: 2em; line-height: 150%; color:#355E62;">PARAMETRIC</div>
 +
      </div>
 +
    </div>
 +
    <div class="row" style="padding-top:20px; padding-bottom:20px;">
 +
      <div class="col-md-3">
 +
        <img src="https://static.igem.org/mediawiki/2016/4/4f/T--BostonU_HW--MINTlogo_rcwolf.png" width="90%" style="padding-left:20px">
 +
      </div>
 +
      <div class="col-md-9">
 +
        All of our STL files used for 3-D printing hardware infrastructure are parametric. If the user decides to use a different servo than that which Neptune recommends, he or she may simply enter a few measurements into the  parameters listed at the top of the provided files and the designs will update automatically to reflect those changes.
 +
        <br><br>
 +
        Our software is designed to convert a mL amount to be dispensed into a PWM command to be sent to the arduino such that an even dispense rate is achieved for fluid movement through the microfluidic device. This conversion, however, is dependent on the specific servo/syringe combination the user has implemented. If the user decides to use a different servo/syringe setup than what is recommended by our system, he or she may still use our dispense conversion algorithm to control their system as it is also completely parametric.
 +
      </div>
 +
    </div>
 +
 +
    <br>
 +
 +
    <div class="row">
 +
      <div class="col-md-3">
 +
      </div>
 +
      <div class="col-md-9">
 +
        <div style="font-size: 2em; line-height: 150%; color:#355E62;">LARGE FUNCTIONAL RANGE OF HARDWARE</div>
 +
      </div>
 +
    </div>
 +
    <div class="row" style="padding-top:20px; padding-bottom:20px;">
 +
      <div class="col-md-3">
 +
        <img src="https://static.igem.org/mediawiki/2016/7/7c/T--BostonU_HW--3DuFlogo_rcwolf.png" width="90%" style="padding-left:20px">
 +
      </div>
 +
      <div class="col-md-9">
 +
        Our Hardware system is highly adaptable for both small and large system requirements. Neptune is capable of running up to 200 servo/syringe combinations at once, fulfilling the need for the most demanding microfluidic system. This number is calculated by finding the bottleneck in data transfer from the computer to Arduino, and the transfer rate from Arduino to motor controller shield. Processing time in both the computer and Arduino are comparatively negligible.
 +
        <br><br>
 +
        Transfer to Arduino: 115,200 bits/second, 14,400 bytes/second
 +
        Transfer to motor controller: standard mode of I2C: 100,000 bits/second, 12,500 bytes/second
 +
        Bytes required for one command: 12
 +
        <br><br>
 +
        Therefore the maximum theoretical number of commands that can be sent at once is 12,500/12 = 1040. Including a safety margin of over 5x to ensure that all servo/syringe combinations can move 5x per second to ensure smooth motion all at once, Neptune’s set maximum is 200 servo/syringe combinations.
 +
        <br><br>
 +
        Neptune transforms the build area of a desktop CNC mill into that of an entire machine shop, and beyond. By milling square, modular components with pre-drilled holes for easy mounting Neptune can span a build area of one 4.2”x 4.2” square to hundreds of feet in any direction. This modularity, in addition to enabling huge build areas, allows for custom baseboard configurations to fix each project’s individual needs. The pre-drilled holes ensure proper component alignment and spacing, further adding to Neptune’s ease-of-use.
 +
      </div>
 +
    </div>
 +
    <br>
 +
  </div>
 +
  <div class="col-md-1"></div>
 
</div>
 
</div>
  
−
</body>
 
  
−
</html>
 
  
−
{{BUHW2016Footer}}
+
<br><br>
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
</body>
 +
</html>

Revision as of 17:53, 14 October 2016


PROJECT BUILD





Considerations for Replication | Neptune is built to be modular, accessible, parametric, and expandable.
OPEN SOURCE
MakerFluidics is an accessible, inexpensive microfluidic fabrication technique used to manufacture microfluidic chips. A user will use an SVG file to mill out both the control and flow layers of a microfluidic chip. Then he or she will use these 2 layers to sandwich a piece of PDMS and vacuum the chip to create a seal. Through Neptune, the user is encouraged to use this fabrication infrastructure to make their chip so that they may rapidly prototype many chips inexpensively for any iterations of their experiment and easily control their microfluidic system through the Neptune interface.

INSTRUCTIONAL RESOURCES
[Priya: Build & Assembly pages]

PARAMETRIC
All of our STL files used for 3-D printing hardware infrastructure are parametric. If the user decides to use a different servo than that which Neptune recommends, he or she may simply enter a few measurements into the parameters listed at the top of the provided files and the designs will update automatically to reflect those changes.

Our software is designed to convert a mL amount to be dispensed into a PWM command to be sent to the arduino such that an even dispense rate is achieved for fluid movement through the microfluidic device. This conversion, however, is dependent on the specific servo/syringe combination the user has implemented. If the user decides to use a different servo/syringe setup than what is recommended by our system, he or she may still use our dispense conversion algorithm to control their system as it is also completely parametric.

LARGE FUNCTIONAL RANGE OF HARDWARE
Our Hardware system is highly adaptable for both small and large system requirements. Neptune is capable of running up to 200 servo/syringe combinations at once, fulfilling the need for the most demanding microfluidic system. This number is calculated by finding the bottleneck in data transfer from the computer to Arduino, and the transfer rate from Arduino to motor controller shield. Processing time in both the computer and Arduino are comparatively negligible.

Transfer to Arduino: 115,200 bits/second, 14,400 bytes/second Transfer to motor controller: standard mode of I2C: 100,000 bits/second, 12,500 bytes/second Bytes required for one command: 12

Therefore the maximum theoretical number of commands that can be sent at once is 12,500/12 = 1040. Including a safety margin of over 5x to ensure that all servo/syringe combinations can move 5x per second to ensure smooth motion all at once, Neptune’s set maximum is 200 servo/syringe combinations.

Neptune transforms the build area of a desktop CNC mill into that of an entire machine shop, and beyond. By milling square, modular components with pre-drilled holes for easy mounting Neptune can span a build area of one 4.2”x 4.2” square to hundreds of feet in any direction. This modularity, in addition to enabling huge build areas, allows for custom baseboard configurations to fix each project’s individual needs. The pre-drilled holes ensure proper component alignment and spacing, further adding to Neptune’s ease-of-use.