Line 416: | Line 416: | ||
<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%;"><b style="color: #355E62;">TIMELINE | </b>Building the Neptune Flow</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 441: | Line 426: | ||
<section id="about"> | <section id="about"> | ||
<div class="container"> | <div class="container"> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br><br/> | <br><br/> | ||
<div class="row"> | <div class="row"> | ||
Line 488: | Line 467: | ||
<div class="timeline-heading"> | <div class="timeline-heading"> | ||
<h4>July 2016</h4> | <h4>July 2016</h4> | ||
− | <h4 class="subheading"> | + | <h4 class="subheading">Expanding Horizons</h4> |
</div> | </div> | ||
<div class="timeline-body"> | <div class="timeline-body"> | ||
− | <p class="text-muted"> | + | <p class="text-muted">We started building Neptune piece by piece. From what was initially a GUI designed only to interact with hardware, the idea of Neptune as a full-fledged toolchain arose.</p> |
<a href="https://2016.igem.org/Team:BostonU_HW/Notebook/July" class="btn btn-light">See More </a> | <a href="https://2016.igem.org/Team:BostonU_HW/Notebook/July" class="btn btn-light">See More </a> | ||
</div> | </div> | ||
Line 503: | Line 482: | ||
<div class="timeline-heading"> | <div class="timeline-heading"> | ||
<h4>August 2016</h4> | <h4>August 2016</h4> | ||
− | <h4 class="subheading"> | + | <h4 class="subheading">In the Trenches</h4> |
</div> | </div> | ||
<div class="timeline-body"> | <div class="timeline-body"> | ||
− | <p class="text-muted"> | + | <p class="text-muted">We carved out the major components that make up Neptune today. The Specify, Design, Build, Assemble, and Control pages were built with the end functional goal of each component clearly laid out. Many iterations of control infrastructure prototypes were made and firmware was solidified.</p> |
<a href="https://2016.igem.org/Team:BostonU_HW/Notebook/August" class="btn btn-light">See More </a> | <a href="https://2016.igem.org/Team:BostonU_HW/Notebook/August" class="btn btn-light">See More </a> | ||
</div> | </div> | ||
Line 517: | Line 496: | ||
<div class="timeline-heading"> | <div class="timeline-heading"> | ||
<h4>September 2016</h4> | <h4>September 2016</h4> | ||
− | <h4 class="subheading"> | + | <h4 class="subheading">End-to-end Integration</h4> |
</div> | </div> | ||
<div class="timeline-body"> | <div class="timeline-body"> | ||
− | <p class="text-muted"> | + | <p class="text-muted">Full integration of Neptune software and hardware was made. Neptune software was stress-tested by benchmarks and levels of hardware precision were evaluated and documented.</p> |
<a href="https://2016.igem.org/Team:BostonU_HW/Notebook/September" class="btn btn-light">See More </a> | <a href="https://2016.igem.org/Team:BostonU_HW/Notebook/September" class="btn btn-light">See More </a> | ||
</div> | </div> | ||
Line 532: | Line 511: | ||
<div class="timeline-heading"> | <div class="timeline-heading"> | ||
<h4>October 2016</h4> | <h4>October 2016</h4> | ||
− | <h4 class="subheading"> | + | <h4 class="subheading">Release</h4> |
</div> | </div> | ||
<div class="timeline-body"> | <div class="timeline-body"> | ||
− | <p class="text-muted"> | + | <p class="text-muted">Programming time dedicated to bug-fixing. We validated our work through multiple test cases including a collaboration with the MIT wetlab team. We released our software and hardware as open source on GitHub and NONA.</p> |
<a href="https://2016.igem.org/Team:BostonU_HW/Notebook/October" class="btn btn-light">See More </a> | <a href="https://2016.igem.org/Team:BostonU_HW/Notebook/October" class="btn btn-light">See More </a> | ||
</div> | </div> |
Revision as of 05:32, 19 October 2016
PROOF OF CONCEPT
-
16 - 30 May 2016
Training and Orientation
Our project is part of an existing workflow in our lab, and during training and orientation we learned about the flow and how we fit in. We also started to test tools that we could use to build our graphical user interface and planned out what we could do with the hardware setup.
See More -
June 2016
A GUI is Born
After testing out tools, we decided to implement a web application using a node.js (operating as a local server) framework. We started ordering parts and 3D printing components to set up the hardware.
See More -
July 2016
Expanding Horizons
We started building Neptune piece by piece. From what was initially a GUI designed only to interact with hardware, the idea of Neptune as a full-fledged toolchain arose.
See More -
August 2016
In the Trenches
We carved out the major components that make up Neptune today. The Specify, Design, Build, Assemble, and Control pages were built with the end functional goal of each component clearly laid out. Many iterations of control infrastructure prototypes were made and firmware was solidified.
See More -
September 2016
End-to-end Integration
Full integration of Neptune software and hardware was made. Neptune software was stress-tested by benchmarks and levels of hardware precision were evaluated and documented.
See More -
October 2016
Release
Programming time dedicated to bug-fixing. We validated our work through multiple test cases including a collaboration with the MIT wetlab team. We released our software and hardware as open source on GitHub and NONA.
See More