Computer Science 23
The Sensor-bot Group Project
There are no lectures during the last two weeks of the course.
During this time you will be working in teams programming Gracia
robots.
The project will pull on all the skills you have developed so far but
will provide a set of new skills needed to do cross development and
embedded systems programming and debugging.
This completes the hackers toolkit that you can be proud of. We will do
distributed programming using sockets, mutable threads for embedded
Linux.
We
have added a mote sensor to the bot that allows it to interact with a
sensor network built across the CS department. We have also added a
camera to the bot. You will write the controller that runs on your
laptop and the server side on the rob - all in C and Linux. Once your
ready your bot will go on a treasure hunt. The final task is the CS23
remote controlled bot race.
These notes represent key resources for the project and update notes on issues.
Resources
Checkout the following important links - not that the project blog is the more important
Project teams
Project description
Project blog news, announcements and clarifications with the final project. Please refer to this page for the latest information.
Kick off day - what you should do today?
1) get your bot; 2) review the
material on the project web page; 3) set up a team meeting to discuss
the design review, who is doing what, set up git, essentially, get
organized. We have two TAs for the project. Check out the project blog
for who is your project TA. Also, Jonghoon Choi
<Jonghoon.Choi@Dartmouth.EDU> is ready to help you with
gtk questions.
Milestones
The
following set of deadlines are important for the progress of the
project. Please note that you need to provide documentation (see below) for the
design and code reviews and the final project submission.
4-7 PM Thursday May 21 design review.The
project review should include requirements, Design Spec
(inputs/outputs, data flow, data structures, pseudo-code) and
functional decomposition; How the project implementation breaks down,
who is doing what. The project review material is due 12 PM day before
review Send tarball documentation to realcs23@cs.dartmouth.edu
4-7 PM Wednesday May 27 code review. The
code review should include the Implementation Spec, unit tests and
whatever code is written up until the review point. The code review
material is due 12 PM day before review. Send git tarball (documentation and
source tree) to realcs23@cs.dartmouth.edu
4-6 PM Tuesday June 2 demo or die day. Project presentation (design overview, lessons learnt, etc) and demo of project.
12 AM Wednesday June 3 project reports due. You
need to send us the URL to clone your git repository for the project.
The source tree should include a sub directory called
/report with report.tex (the latex for your report) and the
report.pdf (produced from latex). Your report has to be in tex.
The report should be 10 pages max: include
1) Thread design of client and server
2) Design Specs
3) Implementation Specs
4) GUI screen dump
5) Lesson learnt
Mail realcs23@cs.dartmouth.edu by midnight Wednesday.
The source tree must have all the make, source and header files, and scripts you have
written. We should be able to make and run your system. We will verify this.
source tree
/project/report
/project/portal
/project/robot
You should but this in your public-html with appropriate permissions - as with search engine.
e.g.,
http://www.cs.dartmouth.edu/~campbell/project/
Some photos from the "battle robotica" over previous years.
Matt at the start line of the first semi-annual CS23 bot race. One your marks, get set, ....
A CS23 Garcia bot with a wireless sensor (the gray thingy at the top)
and a camera (the eye).
Some more pictures from last terms demo or die day.