(9 intermediate revisions by 2 users not shown) | |||
Line 194: | Line 194: | ||
<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"> | + | <a href="https://2016.igem.org/Team:BostonU_HW/Demonstrate">Demonstration</a> |
− | <a href="https://2016.igem.org/Team:BostonU_HW/Proof"> | + | <a href="https://2016.igem.org/Team:BostonU_HW/Proof">Proof</a> |
− | <a href="https://2016.igem.org/Team:BostonU_HW/Design"> | + | <a href="https://2016.igem.org/Team:BostonU_HW/Design">Design</a> |
<a href="https://2016.igem.org/Team:BostonU_HW/Parts">Parts</a> | <a href="https://2016.igem.org/Team:BostonU_HW/Parts">Parts</a> | ||
Line 214: | Line 214: | ||
<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> | ||
− | + | ||
− | + | ||
</div> | </div> | ||
</li> | </li> | ||
Line 222: | Line 222: | ||
<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"> | ||
− | <a href="https://2016.igem.org/Team:BostonU_HW/ | + | <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> | ||
</div> | </div> | ||
</li> | </li> | ||
+ | |||
+ | <li class="sliding-middle-out dropdown"> | ||
+ | <a href="#" class="dropbtn">MEDAL CRITERIA </a> | ||
+ | <div class="dropdown-content"> | ||
+ | <a href="https://2016.igem.org/Team:BostonU_HW/Bronze">Bronze</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> | ||
+ | |||
+ | </div> | ||
+ | </li> | ||
+ | |||
</ul> | </ul> | ||
</div><!-- /.navbar-collapse --> | </div><!-- /.navbar-collapse --> | ||
Line 366: | Line 377: | ||
<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-10" style="font-size: 3em; line-height: 130%;"> | + | <div class="col-md-10" style="font-size: 3em; line-height: 130%;">IMAGINE, CREATE, EXPLORE</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
Line 376: | Line 387: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-10"> | <div class="col-md-10"> | ||
− | + | <div> | |
<br><br> | <br><br> | ||
<div> | <div> | ||
− | + | Neptune is an open-source software tool available to biologists through Github and Nona using the BSDII license. Specifically, it is a web application that runs on a node.js express server using HTML, JavaScript and CSS. To get the software running, the biologist has to go though a couple of easy steps. First, they would have to download node.js, and our project repository. <br><br> | |
+ | After running our project through node.js, the biologist would be introduced to the home page of Neptune. Here, they could look at documentation or get started with their project. They can either continue working on a pre-existing project, or start a new one. The user would then be redirected to the dashboard page where they can see a layout of the entire workflow. <br><br> | ||
+ | The first step to designing a microfluidic chip would be the specify page. Here they can specify the layout of their chip from a very high level description. This would be a simple verilog-like language. Once the description is mapped onto the chip using an automatic place and route tool, the user can then proceed to the design stage. Here, the user can fine tune their work to edit the experimental setup. Once that is complete, the chip design will be outputed as a JSON and an SVG. The SVG would be used to mill out the chip, and the JSON would help the user control the experiment later on. Following the design page, the user would be redirected to a Build page where they can select their hardware based on their requirements. Once the user maps the hardware to their microfluidic chip, they can proceed to Assembly where they would learn how to put all the pieces together. They can set up their entire experiment here including building the hardware infrastructure, milling out their microfluidic chip and sealing the control and flow layers, and so on. Last is the Control page. Here, they can Control their microfluidic device by opening and closing valves, and dispensing liquid through Neptune's user interface. They can also time their experiments to a certain level by dispensing a certain volume of liquid over some time. Please view our video for more information and a demonstration of our software. | ||
+ | |||
</div> | </div> | ||
</div> | </div> | ||
+ | <div class="row" style="padding-top:50px; padding-right: 50px; padding-bottom:20px;"> | ||
+ | <video width="100%" controls> | ||
+ | <source src="https://static.igem.org/mediawiki/2016/3/34/T--BostonU_HW--SoftwareVideo_rcwolf.mp4" type="video/mp4"> | ||
+ | Your browser does not support the video tag. | ||
+ | </video> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | </div> | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
Line 395: | Line 418: | ||
</div> | </div> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
Latest revision as of 03:17, 20 October 2016
SOFTWARE
IMAGINE, CREATE, EXPLORE
Neptune is an open-source software tool available to biologists through Github and Nona using the BSDII license. Specifically, it is a web application that runs on a node.js express server using HTML, JavaScript and CSS. To get the software running, the biologist has to go though a couple of easy steps. First, they would have to download node.js, and our project repository.
After running our project through node.js, the biologist would be introduced to the home page of Neptune. Here, they could look at documentation or get started with their project. They can either continue working on a pre-existing project, or start a new one. The user would then be redirected to the dashboard page where they can see a layout of the entire workflow.
The first step to designing a microfluidic chip would be the specify page. Here they can specify the layout of their chip from a very high level description. This would be a simple verilog-like language. Once the description is mapped onto the chip using an automatic place and route tool, the user can then proceed to the design stage. Here, the user can fine tune their work to edit the experimental setup. Once that is complete, the chip design will be outputed as a JSON and an SVG. The SVG would be used to mill out the chip, and the JSON would help the user control the experiment later on. Following the design page, the user would be redirected to a Build page where they can select their hardware based on their requirements. Once the user maps the hardware to their microfluidic chip, they can proceed to Assembly where they would learn how to put all the pieces together. They can set up their entire experiment here including building the hardware infrastructure, milling out their microfluidic chip and sealing the control and flow layers, and so on. Last is the Control page. Here, they can Control their microfluidic device by opening and closing valves, and dispensing liquid through Neptune's user interface. They can also time their experiments to a certain level by dispensing a certain volume of liquid over some time. Please view our video for more information and a demonstration of our software.
After running our project through node.js, the biologist would be introduced to the home page of Neptune. Here, they could look at documentation or get started with their project. They can either continue working on a pre-existing project, or start a new one. The user would then be redirected to the dashboard page where they can see a layout of the entire workflow.
The first step to designing a microfluidic chip would be the specify page. Here they can specify the layout of their chip from a very high level description. This would be a simple verilog-like language. Once the description is mapped onto the chip using an automatic place and route tool, the user can then proceed to the design stage. Here, the user can fine tune their work to edit the experimental setup. Once that is complete, the chip design will be outputed as a JSON and an SVG. The SVG would be used to mill out the chip, and the JSON would help the user control the experiment later on. Following the design page, the user would be redirected to a Build page where they can select their hardware based on their requirements. Once the user maps the hardware to their microfluidic chip, they can proceed to Assembly where they would learn how to put all the pieces together. They can set up their entire experiment here including building the hardware infrastructure, milling out their microfluidic chip and sealing the control and flow layers, and so on. Last is the Control page. Here, they can Control their microfluidic device by opening and closing valves, and dispensing liquid through Neptune's user interface. They can also time their experiments to a certain level by dispensing a certain volume of liquid over some time. Please view our video for more information and a demonstration of our software.