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

 
(3 intermediate revisions by 2 users not shown)
Line 167: Line 167:
 
   <div class="container-fluid paddedNav">
 
   <div class="container-fluid paddedNav">
 
     <!-- Brand and toggle get grouped for better mobile display -->
 
     <!-- Brand and toggle get grouped for better mobile display -->
     <div class="navbar-header">k
+
     <div class="navbar-header">
 
       <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1" aria-expanded="false">
 
       <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="sr-only">Toggle navigation</span>
Line 191: Line 191:
 
         <li class="sliding-middle-out dropdown">
 
         <li class="sliding-middle-out dropdown">
 
             <a href="#" class="dropbtn">PROJECT</a>
 
             <a href="#" class="dropbtn">PROJECT</a>
 +
           
 
             <div class="dropdown-content">
 
             <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/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/Demonstrate">Demonstration</a>
                   <a href="https://2016.igem.org/Team:BostonU_HW/Proof">Application</a>
+
                   <a href="https://2016.igem.org/Team:BostonU_HW/Proof">Proof</a>
                   <a href="https://2016.igem.org/Team:BostonU_HW/Design">Documentation</a>
+
                   <a href="https://2016.igem.org/Team:BostonU_HW/Design">Design</a>
 +
                  <a href="https://2016.igem.org/Team:BostonU_HW/Parts">Parts</a>
 
             </div>
 
             </div>
 
         </li>
 
         </li>
Line 208: Line 210:
 
         <li class="sliding-middle-out dropdown">
 
         <li class="sliding-middle-out dropdown">
 
             <a href="https://2016.igem.org/Team:BostonU_HW/Human_Practices" class="dropbtn">HUMAN PRACTICES</a>
 
             <a href="https://2016.igem.org/Team:BostonU_HW/Human_Practices" class="dropbtn">HUMAN PRACTICES</a>
       
+
           
 
             <div class="dropdown-content">
 
             <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/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/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>
 
             </div>
 
         </li>
 
         </li>
 
         <li class="sliding-middle-out dropdown">
 
         <li class="sliding-middle-out dropdown">
 
             <a href="#" class="dropbtn">AWARDS</a>
 
             <a href="#" class="dropbtn">AWARDS</a>
 +
           
 
             <div class="dropdown-content">
 
             <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/Integrated_Practices">Integrated Practices</a>
 
                   <a href="https://2016.igem.org/Team:BostonU_HW/Software">Software</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>
 
             </div>
 
         </li>
 
         </li>
 
         <li class="sliding-middle-out dropdown">
 
         <li class="sliding-middle-out dropdown">
             <a href="#" class="dropbtn">MEDAL JUSTIFICATION </a>
+
             <a href="#" class="dropbtn">MEDAL CRITERIA </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;">
 
             <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">
 
             <div class="dropdown-content">
Line 232: Line 233:
 
                   <a href="https://2016.igem.org/Team:BostonU_HW/Silver">Silver</a>
 
                   <a href="https://2016.igem.org/Team:BostonU_HW/Silver">Silver</a>
 
                   <a href="https://2016.igem.org/Team:BostonU_HW/Gold">Gold</a>
 
                   <a href="https://2016.igem.org/Team:BostonU_HW/Gold">Gold</a>
                   <a href="https://2016.igem.org/Team:BostonU_HW/AboveAndBeyond">Above And Beyond</a>
+
                    
 
             </div>
 
             </div>
 
         </li>
 
         </li>
 +
       
  
 
       </ul>
 
       </ul>
Line 240: Line 242:
 
   </div><!-- /.container-fluid -->
 
   </div><!-- /.container-fluid -->
 
</nav>
 
</nav>
 
  
 
</div>
 
</div>
Line 319: Line 320:
 
      
 
      
 
      
 
      
<!--
+
 
 +
 
 +
 
 
<div class="row" style="padding-top:50px; padding-bottom:50px;">
 
<div class="row" style="padding-top:50px; padding-bottom:50px;">
 
   <div class="col-md-1"></div>
 
   <div class="col-md-1"></div>
   <div class="col-md-8" style="font-size: 4em; line-height: 130%">Here's what we did: </div>
+
   <div class="col-md-10" style="font-size: 3em; line-height: 130%;">
   <div class="col-md-3"></div>
+
    <div class="row">
 +
      <div class="col-md-4"><img src="https://static.igem.org/mediawiki/2016/7/7d/T--BostonU_HW--bronze_med.png" width="100%"></div>
 +
      <div class="col-md-8">Bronze Medal Requirements</div>
 +
    </div>
 +
  </div>
 +
   <div class="col-md-1"></div>
 
</div>
 
</div>
-->
 
  
<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%">
 
<img src="https://static.igem.org/mediawiki/2016/7/7d/T--BostonU_HW--bronze_med.png" style="max-width:40%; max-height:40%;">
 
</div>
 
<div class="col-md-3"></div>
 
</div>
 
  
<div class="row" style="padding-top:50px; padding-bottom:50px;">
+
<div class="row" style="padding-top:100px; padding-bottom:100px;">
 
   <div class="col-md-1"></div>
 
   <div class="col-md-1"></div>
   <div class="col-md-10" style="font-size: 1em;">  
+
   <div class="col-md-10" style="background-color: white; padding-top:50px; padding-bottom:50px;">
 +
    <div class="row">
 +
      <div class="col-md-1"></div>
 +
      <div class="col-md-10">
 +
        <div class="row">
 +
          <div style="font-size: 2em; line-height: 150%; color:#355E62;">Register for iGEM, have a great summer, and attend the Giant Jamboree</div>
 +
        <br><br>
 +
        <div>
 +
          We're very excited to be part of the Jamboree, to see all the other amazing projects, to show everyone what we've accomplished through our hard work this summer. And we're excited to see you there too :)
 +
          <br><br>
 +
        </div>
 +
        </div><br><br><br>
  
<p style="font-size: 2em; font-weight: bold" > Register for iGEM, have a great summer, and attend the Giant Jamboree. </p>
+
          <div class="row">
 +
          <div style="font-size: 2em; line-height: 150%; color:#355E62;">Meet all deliverables on the Requirements page (section 3), except those that specifically mention parts</div>
 +
        <br><br>
 +
        <div>
 +
          <ul>
 +
            <li>Team Wiki: You're looking at her.</li>
 +
            <li>Poster: Come by our table and take a look.</li>
 +
            <li>Presentation: You'll love what you see.</li>
 +
            <li>Project Attributions: Please see out attributions page.</li>
 +
            <li>Registry Part Pages: Hardware track.</li>
 +
            <li>Safety Forms: Complete.</li>
 +
            <li>Judging Forms: Complete.</li>
 +
          </ul>
 +
          <br><br>
 +
        </div>
 +
        </div><br><br><br>
 +
      <div class="row">
 +
          <div style="font-size: 2em; line-height: 150%; color:#355E62;">Meet all deliverables on the Requirements page (section 3), except those that specifically mention parts</div>
 +
        <br><br>
 +
        <div>
  
<p> We're very excited to be part of the Jamboree, to see all the other amazing projects, to show everyone what we've accomplished through our hard work this summer. And we're excited to see you there too :) </p>
+
            Neptune is a design tool that implements the research done by many mentors and graduate student. Before us, other students developed single, abstract software tools toward microfluidic design. These tools saw limited to no use because they failed to integrate into a bigger system. We created the software for the Neptune user interface that wraps these different projects, and we created the hardware control infrastructure for the microfluidics that are generated from this workflow. We have also contributed to the algorithmic libraries of Neptune by developing a tool called Mushroom Mapper, which allows for a higher level of abstraction when specifying microfluidic chip designs. Here we attribute the different components behind Neptune, the ones created by other students and mentors. <br><br>
 +
            <b style="font-size: 1.5em">3DuF:</b>
 +
            <br><br>
 +
            3DuF is a user friendly, open source application for creating microfluidic designs and design components that can then be fabricated with CAD tools. This application is embedded in Neptune as a visualization tool for the microfluidic chip design. This tool is currently in development by our mentor Josh Lippai.
 +
            <br><br>
 +
            <b style="font-size: 1.5em">MakerFluidics:</b>
 +
            <br><br>
 +
            MakerFluidics is a microfluidic fabrication protocol that leverages open, low cost, and easily accessible tools to fabricate microfluidics. In this toolchain, microfluidics are created using a CNC mill to create channels in a thermoplastic, biocompatible stock. MakerFluidics uses open source software, including 3DuF, and now Neptune. Neptune is developed to be compatible with MakerFluidics; in Neptune SVG design schematics are generated, ready to fabricate with a CNC mill. This protocol was developed by our mentor Ryan Silva.
 +
            <br><br>
 +
            <b style="font-size: 1.5em">Fluigi Core:</b>
 +
            <br><br>
 +
            Fluigi Core is a place and route tool that takes MINT files that the user inputs into Neptune, and it performs an optimization placing of channels, valves, and other components onto the microfluidic chip. In essence, Fluigi Core generates design schematics from the MINT standard microfluidic specification format you provide it. Neptune wraps Fluigi Core, it is the algorithmic library to our software. This program is currently in development by our mentor Radhakrishna Sanka.
 +
            <br><br>
 +
            <b style="font-size: 1.5em">NetSynth:</b>
 +
            <br><br>
 +
            NetSynth is a logic minimization library for Verilog. The original purpose of NetSynth was to take a Verilog description of a circuit, and convert this into a netlist of wires and gates that realize the design description. Our iGEM team has joined the prior work of Prashant Vaidyanathan to refactor NetSynth into a tool that can also perform logic minimization on microfluidic designs. Prashant is responsible for originally repurposing NetSynth for microfluidic design, and our team has further contributed to this by integrating NetSynth outputs with the Mushroom Mapper tool we created.
 +
            <br><br>
 +
        </div>
 +
        </div><br><br><br>
  
<p style="font-size: 2em; font-weight: bold"> Meet all deliverables on the Requirements page (section 3), except those that specifically mention parts. </p>
+
<div class="row">
 +
          <div style="font-size: 2em; line-height: 150%; color:#355E62;">Document at least one new substantial contribution to the iGEM community that showcases a project made with BioBricks. This contribution should be equivalent in difficulty to making and submitting a BioBrick part</div>
 +
        <br><br>
 +
        <div>
 +
          Our contribution to the iGEM community is not a single hardware device, nor a one-off software tool. Our contribution to the iGEM community, and the synthetic biology community as a whole, is much greater than that. This summer we built a completely integrated, seamless, end-to-end microfluidic design, fabrication, and control workflow. This workflow enables the rapid, modular, and parametric design of microfluidic chips, and our workflow integrates with low cost, open fabrication methods. This is something that has never been possible in microfluidics before.
 +
          <br><br>
  
 +
          <div>
 +
          Physically, our contribution to the community is twofold:
 +
          <br><br>
  
<p>  
+
          <div>
<p>Team Wiki: You're looking at her. </p>
+
          This summer we created Neptune, an integrated microfluidic design suite. This is a single software tool that spans the entire microfluidic design process. In Neptune, users can create microfluidic chips design schematics with the aid of algorithms that optimize the design. Neptune allows microfluidics to be designed through LFR, a specification we worked to create. With LFR, designs are parametric and the design process is simple. Neptune also allows researchers to run experiments directly through the interface by providing a control page. Users can upload a chip design to Neptune, and then use Neptune to manipulate valve states and actuate pumps to generate fluid flows in the chip.
<p>Poster: Come by our table and take a look. </p>
+
          <br><br>
<p>Presentation: You'll love what you see. </p>
+
<p>Project Attributions: Please see out attributions page.</p>
+
<p>Registry Part Pages: Hardware track. </p>
+
<p>Sample Submission: hardware track.</p>
+
<p>Safety Forms: Complete. </p>
+
<p>Judging Forms: Complete.  </p>
+
</p>
+
  
<p style="font-size: 2em; font-weight: bold"> Create a page on your team wiki with clear attribution of each aspect of your project. This page must clearly attribute work done by the students and distinguish it from work done by others, including host labs, advisors, instructors, sponsors, professional website designers, artists, and commercial services. </p>
+
          <div>
 +
          We did not stop there. This summer we also created a full hardware control infrastructure for microfluidic chips. We developed original designs for controlling valve actuation and fluid dispension using low cost servo motors and 3D printed components. These designs are both parametric, and the they have high precision in their fluid dispension. Further, we designed 3D print schematics for a pump array to control a microfluidic chip; these 3D print schematics are all served through Neptune.
 +
          <br><br>
  
<p> Neptune is a design tool that implements the research done by many mentors and graduate student. Before us, other students developed single, abstract software tools toward microfluidic design. These tools saw limited to no use because they failed to integrate into a bigger system. We created the software for the Neptune user interface that wraps these different projects, and we created the hardware control infrastructure for the microfluidics that are generated from this workflow. We have also contributed to the algorithmic libraries of Neptune by developing a tool called Mushroom Mapper, which allows for a higher level of abstraction when specifying microfluidic chip designs. Here we attribute the different components behind Neptune, the ones created by other students and mentors. </p>
+
          <div>
<p>3DuF:</p>
+
          Thus, we have developed everything a researcher would need to design, fabricate, and run experiments on their microfluidic device. Accessibility, though, has always been our biggest goal. We developed this entire workflow with the synthetic biology community in mind. Microfluidics have always been very difficult to fabricate, and costly, with tools for fabrication and design costing nearly $100,000. Further, control infrastructure is also costly, and most software tools to control microfluidics are specialized to single hardware pieces. We developed our workflow to interface with and use only open source, low cost tools. We designed 3D printed hardware for the purpose of providing a more accessible alternative, and we use the MakerFluidics fabrication protocol to keep fabrication costs as low as possible.
<p> 3DuF is a user friendly, open source application for creating microfluidic designs and design components that can then be fabricated with CAD tools. This application is embedded in Neptune as a visualization tool for the microfluidic chip design. This tool is currently in development by our mentor Josh Lippai. </p>
+
          <br><br>
        <p>MakerFluidics: </p>
+
<p>MakerFluidics is a microfluidic fabrication protocol that leverages open, low cost, and easily accessible tools to fabricate microfluidics. In this toolchain, microfluidics are created using a CNC mill to create channels in a thermoplastic, biocompatible stock. MakerFluidics uses open source software, including 3DuF, and now Neptune. Neptune is developed to be compatible with MakerFluidics; in Neptune SVG design schematics are generated, ready to fabricate with a CNC mill. This protocol was developed by our mentor Ryan Silva. </p>
+
<p>FluigiCore: </p>
+
<p> Fluigi Core is a place and route tool that takes MINT files that the user inputs into Neptune, and it performs an optimization placing of channels, valves, and other components onto the microfluidic chip. In essence, Fluigi Core generates design schematics from the MINT standard microfluidic specification format you provide it. Neptune wraps Fluigi Core, it is the algorithmic library to our software. This program is currently in development by our mentor Radhakrishna Sanka. </p>
+
<p>NetSynth:  </p>
+
<p> NetSynth is a logic minimization library for Verilog. The original purpose of NetSynth was to take a Verilog description of a circuit, and convert this into a netlist of wires and gates that realize the design description. Our iGem team has joined the prior work of Prashant Vaidyanathan to refactor NetSynth into a tool that can also perform logic minimization on microfluidic designs. Prashant is responsible for originally repurposing NetSynth for microfluidic design, and our team has further contributed to this by integrating NetSynth outputs with the Mushroom Mapper tool we created. </p>
+
  
 +
          <div>
 +
          Please, follow this link to see the documentation for Neptune, and our hardware pieces.
 +
          <br><br>
 +
        </div>
 +
        </div><br><br><br>
  
<p style="font-size: 2em; font-weight: bold"> Document at least one new substantial contribution to the iGEM community that showcases a project made with BioBricks. This contribution should be equivalent in difficulty to making and submitting a BioBrick part. </p>
 
 
 
<p>Our contribution to the iGem community is not a single hardware device, nor a one-off software tool. Our contribution to the iGem community, and the synthetic biology community as a whole, is much greater than that. This summer we built a completely integrated, seamless, end-to-end microfluidic design, fabrication, and control workflow. This workflow enables the rapid, modular, and parametric design of microfluidic chips, and our workflow integrates with low cost, open fabrication methods. This is something that has never been possible in microfluidics before. </p> 
 
 
<p>Physically, our contribution to the community is twofold: </p>
 
 
<p>This summer we created Neptune, an integrated microfluidic design suite. This is a single software tool that spans the entire microfluidic design process. In Neptune, users can create microfluidic chips design schematics with the aid of algorithms that optimize the design. Neptune allows microfluidics to be designed through LFR, a specification we worked to create. With LFR, designs are parametric and the design process is simple. Neptune also allows researchers to run experiments directly through the interface by providing a control page. Users can upload a chip design to Neptune, and then use Neptune to manipulate valve states and actuate pumps to generate fluid flows in the chip.</p>
 
 
<p>We did not stop there. This summer we also created a full hardware control infrastructure for microfluidic chips. We developed original designs for controlling valve actuation and fluid dispension using low cost servo motors and 3D printed components. These designs are both parametric, and the they have high precision in their fluid dispension. Further, we designed 3D print schematics for a pump array to control a microfluidic chip; these 3D print schematics are all served through Neptune. </p>
 
 
<p>Thus, we have developed everything a researcher would need to design, fabricate, and run experiments on their microfluidic device. Accessibility, though, has always been our biggest goal. We developed this entire workflow with the synthetic biology community in mind. Microfluidics have always been very difficult to fabricate, and costly, with tools for fabrication and design costing nearly $100,000. Further, control infrastructure is also costly, and most software tools to control microfluidics are specialized to single hardware pieces. We developed our workflow to interface with and use only open source, low cost tools. We designed 3D printed hardware for the purpose of providing a more accessible alternative, and we use the MakerFluidics fabrication protocol to keep fabrication costs as low as possible.</p>
 
 
 
<p>Please, follow this link to see the documentation for Neptune, and our hardware pieces.</p>
 
  
 +
      </div>
 +
      <div class="col-md-1"></div>
 +
    </div>
 
   </div>
 
   </div>
 
   <div class="col-md-1"></div>
 
   <div class="col-md-1"></div>
 
</div>
 
</div>
 
<br><br>
 
 
 
 
 
 
 
  
  

Latest revision as of 03:20, 20 October 2016


MEDAL CRITERIA: BRONZE





Bronze Medal Requirements
Register for iGEM, have a great summer, and attend the Giant Jamboree


We're very excited to be part of the Jamboree, to see all the other amazing projects, to show everyone what we've accomplished through our hard work this summer. And we're excited to see you there too :)




Meet all deliverables on the Requirements page (section 3), except those that specifically mention parts


  • Team Wiki: You're looking at her.
  • Poster: Come by our table and take a look.
  • Presentation: You'll love what you see.
  • Project Attributions: Please see out attributions page.
  • Registry Part Pages: Hardware track.
  • Safety Forms: Complete.
  • Judging Forms: Complete.





Meet all deliverables on the Requirements page (section 3), except those that specifically mention parts


Neptune is a design tool that implements the research done by many mentors and graduate student. Before us, other students developed single, abstract software tools toward microfluidic design. These tools saw limited to no use because they failed to integrate into a bigger system. We created the software for the Neptune user interface that wraps these different projects, and we created the hardware control infrastructure for the microfluidics that are generated from this workflow. We have also contributed to the algorithmic libraries of Neptune by developing a tool called Mushroom Mapper, which allows for a higher level of abstraction when specifying microfluidic chip designs. Here we attribute the different components behind Neptune, the ones created by other students and mentors.

3DuF:

3DuF is a user friendly, open source application for creating microfluidic designs and design components that can then be fabricated with CAD tools. This application is embedded in Neptune as a visualization tool for the microfluidic chip design. This tool is currently in development by our mentor Josh Lippai.

MakerFluidics:

MakerFluidics is a microfluidic fabrication protocol that leverages open, low cost, and easily accessible tools to fabricate microfluidics. In this toolchain, microfluidics are created using a CNC mill to create channels in a thermoplastic, biocompatible stock. MakerFluidics uses open source software, including 3DuF, and now Neptune. Neptune is developed to be compatible with MakerFluidics; in Neptune SVG design schematics are generated, ready to fabricate with a CNC mill. This protocol was developed by our mentor Ryan Silva.

Fluigi Core:

Fluigi Core is a place and route tool that takes MINT files that the user inputs into Neptune, and it performs an optimization placing of channels, valves, and other components onto the microfluidic chip. In essence, Fluigi Core generates design schematics from the MINT standard microfluidic specification format you provide it. Neptune wraps Fluigi Core, it is the algorithmic library to our software. This program is currently in development by our mentor Radhakrishna Sanka.

NetSynth:

NetSynth is a logic minimization library for Verilog. The original purpose of NetSynth was to take a Verilog description of a circuit, and convert this into a netlist of wires and gates that realize the design description. Our iGEM team has joined the prior work of Prashant Vaidyanathan to refactor NetSynth into a tool that can also perform logic minimization on microfluidic designs. Prashant is responsible for originally repurposing NetSynth for microfluidic design, and our team has further contributed to this by integrating NetSynth outputs with the Mushroom Mapper tool we created.




Document at least one new substantial contribution to the iGEM community that showcases a project made with BioBricks. This contribution should be equivalent in difficulty to making and submitting a BioBrick part


Our contribution to the iGEM community is not a single hardware device, nor a one-off software tool. Our contribution to the iGEM community, and the synthetic biology community as a whole, is much greater than that. This summer we built a completely integrated, seamless, end-to-end microfluidic design, fabrication, and control workflow. This workflow enables the rapid, modular, and parametric design of microfluidic chips, and our workflow integrates with low cost, open fabrication methods. This is something that has never been possible in microfluidics before.

Physically, our contribution to the community is twofold:

This summer we created Neptune, an integrated microfluidic design suite. This is a single software tool that spans the entire microfluidic design process. In Neptune, users can create microfluidic chips design schematics with the aid of algorithms that optimize the design. Neptune allows microfluidics to be designed through LFR, a specification we worked to create. With LFR, designs are parametric and the design process is simple. Neptune also allows researchers to run experiments directly through the interface by providing a control page. Users can upload a chip design to Neptune, and then use Neptune to manipulate valve states and actuate pumps to generate fluid flows in the chip.

We did not stop there. This summer we also created a full hardware control infrastructure for microfluidic chips. We developed original designs for controlling valve actuation and fluid dispension using low cost servo motors and 3D printed components. These designs are both parametric, and the they have high precision in their fluid dispension. Further, we designed 3D print schematics for a pump array to control a microfluidic chip; these 3D print schematics are all served through Neptune.

Thus, we have developed everything a researcher would need to design, fabricate, and run experiments on their microfluidic device. Accessibility, though, has always been our biggest goal. We developed this entire workflow with the synthetic biology community in mind. Microfluidics have always been very difficult to fabricate, and costly, with tools for fabrication and design costing nearly $100,000. Further, control infrastructure is also costly, and most software tools to control microfluidics are specialized to single hardware pieces. We developed our workflow to interface with and use only open source, low cost tools. We designed 3D printed hardware for the purpose of providing a more accessible alternative, and we use the MakerFluidics fabrication protocol to keep fabrication costs as low as possible.

Please, follow this link to see the documentation for Neptune, and our hardware pieces.