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

Line 318: Line 318:
 
<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%"><img src="https://static.igem.org/mediawiki/2016/7/7d/T--BostonU_HW--bronze_med.png"></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" max-width:50%; max-height:50%;>
 +
</div>
 
<div class="col-md-3"></div>
 
<div class="col-md-3"></div>
 
</div>
 
</div>

Revision as of 16:22, 16 October 2016


MEDAL CRITERIA: BRONZE





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.

Sample Submission: hardware track.

Safety Forms: Complete.

Judging Forms: Complete.

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.

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.

FluigiCore:

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.