View source for EG1004 Lab Manual:Nano-Robotics Challenge (NRC)

{{SLDP: RFP|Nano Robotics Challenge(NRC)}}

{{SLDP: Real-life Scenarios (Robots)}}

= Introduction and Overview =
Nano-robotics is a quickly growing field; robots the size of a nanometer (1*10^-9 m) could very well be the next important breakthrough in medical technology. Currently the interest in nanorobots revolves around their potential application in the medical field to act inside the human body as a cure for various ailments. 

The Center of Disease Control (CDC) has recently had an influx of very sick volunteers willing to try out this novel technology. In response the CDC has reached out to engineers and programmers to develop an autonomous nano-robot that can travel through the bloodstream, diagnose health issues, and cure diseases.

Each research group has been provided with a patient.  Your group's patient is Jesse. Jesse decided to go for a swim in the Gowanus Canal. We can't be sure what possessed them to do that, but here we are. Provided with information on illnesses that Jesse could have, your group will need to program an autonomous nano-robot to detect, find, and cure all the illnesses present in the body. 

= Specifications =
Jesse is represented by a light-up skeleton located in the EG Modelshop at 6 Metrotech Center, Brooklyn, NY 11201.  The nanorobot in Jesse's body can be interacted with via an HTTP API as described in Appendix A.  Most programming languages have some way to send HTTP requests.  For the purposes of this project, Python with the Requests module is recommended.  However, for students completely unfamiliar with programming, an instance of Snap!, a graphical programming language maintained by UC Berkeley, is provided.  

To interact with Jesse, connect to the WiFi network EG_NRC-8913 in the EG Modelshop.  Snap! is available at [http://10.42.0.1:5000/ 10.42.0.1:5000/].
Information on the API Specification and using Snap! is available in the Appendices below.

{{SLDP: Microsoft Project}}
{{SLDP: Milestones and Benchmarks}}

== Milestone 1 ==

Prepare a preliminary assessment of the track system using digital logic (truth table, Karnaugh maps, and Boolean equations), a cost estimate, and an MS Project plan.

'''''Look Ahead'': What tasks are planned between now and Milestone 2?'''

See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.

'''Milestone 1 Deliverables''':
* Presentation:
** Project description
** Design approach
** Mission statement
** Cost estimate
** MS Project schedule
** Progress update: current state of the project
'''Presentation notes''':
* Be sure to include any special features and benefits of your design.


==Benchmark Assessment A==
The purpose of Benchmark A is to demonstrate familiarity with interacting with the API and the ability to do it repeatably through code.  For benchmark A, students must:
*Demonstrate an understanding of the API by building a set of functions (or SNAP! blocks) that allow them to use the API conveniently
*Demonstrate the ability to login
*Demonstrate the ability to tick the game
*Demonstrate the ability to start holding and stop holding
*Demonstrate the ability to change the direction of the nanobot
*Demonstrate the ability to reset the game
==Milestone 2==

'''''Look Ahead''': What tasks are planned between now and Milestone 3?''

See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.

'''Milestone 2 Deliverables''':
* Presentation:
** Project description
** Design approach
** Design changes since Milestone 1
** Mission statement

==Benchmark Assessment B==
Students must ''twice'':
*Defeat the weaker virus
*Reset the game
'''WITHOUT''' manually interacting with their program.

==Milestone 3==

'''''Look ahead''': What tasks are planned between now and the completion of the project?''

See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.

'''Milestone 3 Deliverables''':
* Presentation:
** Project description
** Design approach
** Design changes since Milestone 2
** Mission statement
** Cost estimate (previous and current). What changes were made?
** MS Project schedule (previous and current). What changes were made?
** Progress update: current state of the project (time, budget, etc.)

==Commissioning==
In order to commission students must twice:
*Defeat the stronger virus
*Return to their start node
*Reset the game
'''WITHOUT''' manually interacting with their program.

{{SLDP: Final Presentation}}
* Problem statement
* Solution overview
* Company description and qualifications
* Source code of program
* Cost estimate
* Microsoft Project schedule
* Video demonstration
* Why should the company be awarded this contract?

{{SLDP: Submission}}
** Final presentation
** Final program
** Final MS Project Schedule
** Final cost estimate
** Resume(s) (No fictitious resumes will be accepted.)

{{SLDP: Early Acceptance}}

{{SLDP: Late Delivery}}

= Frequently Asked Questions =

{{Semester-Long Design Project}}