CS81 Project

The project consists of four parts, see the individual due dates given below
Getting started

Go through the following steps to set up your directory for the project.

  1. First you need to run setup81 to create a git repository for the project

    If you want to work alone do:

    setup81 project none
    If you want to work with a partner, then one of you needs to run the following while the other one waits until it finishes.
    setup81 project partnerUsername
    Once the script finishes, the other partner should run it on their account.

  2. Since each project will be unique there is no common starting point code you need to copy over. However, you should create a file called notes where you keep track of what you've accomplished each week. I will pull this file each week and check on your progress. Be sure to update it by noon every Friday. Once you have created this file do:
    cd ~/cs81/project
    git add notes
    git commit -m "project start"
    git push

  3. If you are working with a partner, your partner can now pull the changes in.
    cd ~/cs81/project
    git pull
Possible Project Ideas

Because training an adaptive system is a time consuming process you will probably want to conduct your experiments in simulation. However, if you have an idea about how to effectively use a physical robot, you may try this as well. Whether you use a physical robot or a simulated robot, you will need to carefully consider the environment and the task. What actions and sensory information should be available to the robot? What is your goal?

When conducting research, it is beneficial to work incrementally towards your ultimate goal. In other words, start with the simplest version of your idea that is likely to yield interesting results. If that works, then you can then add another level of complexity. This approach is more effective then beginning immediately with a very complex set up.

Writing tips
1. Proposal (10%), Due by noon on Thursday, Oct. 29

Your project proposal should be 2-4 pages long. It should include a clear description of:

Email me a pdf of your proposal by noon on Thursday, Oct. 29

2. Checkpoint demonstration (5%), Nov. 17, 19, or 20

Each group or individual doing a project will give a demonstration during the week of November 16. Your experiments do not need to be completed at this point, however be prepared to execute some implemented aspect of your system.

You should plan to speak for 10 minutes with an additional 5 minutes for questions. You are encouraged to use slides for this demonstration. Begin by describing your project (cover the same points as in your project proposal) and then demonstrate some aspect of your project.

3. Presentation (10%), Dec. 1, 3, 4, 7, or 8

You will give a 20 minute presentation about your project with an additional 5 minutes for questions. Each group or individual doing a project will be assigned a time to speak during the last two weeks of class.

It may be the case that you are still running experiments at this point. However, you must have some preliminary results to report. If it is a team project, then each team member should speak for an equal portion of the time. You must use slides of some kind.

You should follow these guidelines (put together by Tia Newhall) when creating your talk.

4. Paper (20%), Due by noon on Tuesday, Dec. 15

Your paper should be 8-10 pages long and include the following:

I have provided a LaTeX template for your paper here: /home/meeden/public/latex-example/.

Your grade will not be based on whether or not your experiment succeeds. Negative results are also useful. Your grade will be based on the design and execution of the experiment as well as the thoroughness and readability of the paper.

Email me a pdf version of your paper by noon on Tuesday, Dec. 15

Project etiquette

Your project experiments may require a lot of time to run. Please read the following suggestions for how to conduct your experiments so as not to disrupt the work of other students. Pay special attention to the use of nice and screen.