(19 intermediate revisions by the same user not shown) | |||
Line 476: | Line 476: | ||
height: 280px; | height: 280px; | ||
} | } | ||
+ | |||
+ | .imgSquareOpenSource{ | ||
+ | background: url('https://static.igem.org/mediawiki/2016/9/9b/T--BostonU_HW--openSourceSquareDownsized_rcwolf.jpg') no-repeat; | ||
+ | -webkit-background-size: 95% auto; | ||
+ | -moz-background-size: 95% auto; | ||
+ | -o-background-size: 95% auto; | ||
+ | background-size: 95% auto; | ||
+ | height: 280px; | ||
+ | } | ||
+ | |||
+ | .imgSquareOurTeam{ | ||
+ | background: url('https://static.igem.org/mediawiki/2016/7/76/T--BostonU_HW--walkingTeamDownsized_rcwolf.png') no-repeat; | ||
+ | -webkit-background-size: 95% auto; | ||
+ | -moz-background-size: 95% auto; | ||
+ | -o-background-size: 95% auto; | ||
+ | background-size: 95% auto; | ||
+ | height: 280px; | ||
+ | } | ||
+ | |||
+ | .imgSquareTutorial{ | ||
+ | background: url('https://static.igem.org/mediawiki/2016/7/72/T--BostonU_HW--tutorialTypingDownsized_rcwolf.png') no-repeat; | ||
+ | -webkit-background-size: 95% auto; | ||
+ | -moz-background-size: 95% auto; | ||
+ | -o-background-size: 95% auto; | ||
+ | background-size: 95% auto; | ||
+ | height: 280px; | ||
+ | } | ||
+ | |||
+ | |||
.navImg{ | .navImg{ | ||
max-width: 100%; | max-width: 100%; | ||
Line 520: | Line 549: | ||
text-align: center !important; | text-align: center !important; | ||
transform: rotateY(180deg); | transform: rotateY(180deg); | ||
− | + | margin-left: -22px !important; | |
− | margin-left: - | + | |
/* font-size: 30px;*/ | /* font-size: 30px;*/ | ||
} | } | ||
Line 536: | Line 564: | ||
<div class="col-md-3 card"> | <div class="col-md-3 card"> | ||
<div class="cubeHeight"> | <div class="cubeHeight"> | ||
− | <div class="navBlockTxt side | + | <div class="navBlockTxt side imgSquareOpenSource"> Open Source <br> <img src="https://static.igem.org/mediawiki/2016/7/71/T--BostonU_HW--openSourceIcon_rcwolf.png" > |
</div> | </div> | ||
− | <div class="side back"> | + | <div class="side back" style="top: 15%"> |
− | Neptune is completely open-source | + | <h4>Neptune is completely open-source</h4> |
<br> | <br> | ||
− | <a href=""><button type="button" class="btn btn-primary">learn more</button></a> | + | <a href=""><button type="button" class="btn btn-primary" >learn more</button></a> |
</div> | </div> | ||
</div> | </div> | ||
Line 552: | Line 580: | ||
<div class="col-md-3 card"> | <div class="col-md-3 card"> | ||
<div class="cubeHeight"> | <div class="cubeHeight"> | ||
− | <div class="navBlockTxt side | + | <div class="navBlockTxt side imgSquareTutorial"> Tutorials <br> <img src="https://static.igem.org/mediawiki/2016/a/a4/T--BostonU_HW--tutorialsIcon_rcwolf.png" > |
</div> | </div> | ||
− | <div class="side back"> | + | <div class="side back" style="top: 15%"> |
− | + | <h4>Watch our Neptune tutorial</h4> | |
<br> | <br> | ||
<a href=""><button type="button" class="btn btn-primary">learn more</button></a> | <a href=""><button type="button" class="btn btn-primary">learn more</button></a> | ||
Line 568: | Line 596: | ||
<div class="col-md-3 card"> | <div class="col-md-3 card"> | ||
<div class="cubeHeight"> | <div class="cubeHeight"> | ||
− | <div class="navBlockTxt side | + | <div class="navBlockTxt side imgSquareOurTeam"> Our Team <br> <img src="https://static.igem.org/mediawiki/2016/4/49/T--BostonU_HW--ourTeamIcon_rcwolf.png" > |
</div> | </div> | ||
− | <div class="side back"> | + | <div class="side back" style="top: 15%"> |
− | + | <h4>Meet the team behind the magic</h4> | |
<br> | <br> | ||
<a href=""><button type="button" class="btn btn-primary">learn more</button></a> | <a href=""><button type="button" class="btn btn-primary">learn more</button></a> | ||
Line 585: | Line 613: | ||
<div class="navBlockTxt side imgSquare"> Demonstration <br> <img src="https://static.igem.org/mediawiki/2016/d/da/T--BostonU_HW--demonstrationIcon_rcwolf.png" > | <div class="navBlockTxt side imgSquare"> Demonstration <br> <img src="https://static.igem.org/mediawiki/2016/d/da/T--BostonU_HW--demonstrationIcon_rcwolf.png" > | ||
</div> | </div> | ||
− | <div class="side back"> | + | <div class="side back" style="top: 15%"> |
− | See | + | <h4>See how Neptune is being used in other labs</h4> |
<br> | <br> | ||
<a href=""><button type="button" class="btn btn-primary">learn more</button></a> | <a href=""><button type="button" class="btn btn-primary">learn more</button></a> |
Latest revision as of 20:52, 4 August 2016
SPECIFY
DESIGN
BUILD
Begin by defining which inputs and outputs your microfluidic chip will have.
Declare any limitations in terms of port size, channel width. Neptune will efficiently place and route the features of your chip.
The mapper (MM) tool within the place and routing functionality has been made completely by the iGEM Team.
Check and visualize your device layout using the Neptune graphical user interface.
Edit the design if you so desire. Establish a control sequence to move fluids through the microfluidic chip.
The interface has been made completely by the iGEM Team.
Assemble your microfluidic system. Import our design files into a 3D Printer and CNC mill to make the chip and the pump setup.
Change the setup using our parameterized designs to fit your specific needs.
The design of the setup is BU iGEM work, whilst the chip manufacturing is the work of our mentors.
OUR PROJECT
Neptune is a specify, design, and build tool for the development of continuous flow microfluidics. With Neptune, users can specify microfluidic devices through a high level description of liquid flow relations. Our application will automatically place and route the design schematic of the microfluidic and, when used in conjunction with low cost and readily available CAD tools, a user can build their custom microfluidic system in-lab.
The Boston University 2016 iGem Hardware Team is encapsulating this entire workflow through a graphical user interface. Users can write files that specify the function of the microfluidic, preview and edit their microfluidic design generated by the application, use this application directly with CAD tools such as a CNC mill to fabricate their device, and physically control valves and ports on the microfluidic chip. The iGem team is also complementing this workflow by developing and releasing open source designs of our hardware, including parametric 3D print files and firmware for microcontrollers that actuate the microfluidic valves. Finally, the iGem team is also involved in the development of the place and route software that converts a high level description of liquid flow relations into a microfluidic netlist that can that be converted into a design schematic.