Homework 3: Due Tuesday (2015.11.03) by noon

Part 1: "Cherry-pick"

Turn in: push hw3/p1.cpp in your personal repo to turn in this homework.

To begin this homework you must get everyone's code. Go to the root of the course repo and run the pull_students.sh script:
```
cd path/to/mat201b2015
./pull_students.sh
```
This should take a little while. While it's going and after it's done, keep and eye out for errors and failures.
Look over your classmates' solutions to homework 1 and homework 2. Inspect each running program.

Hint: the following code (to be pasted into a shell) will run the hw2/p3.cpp in every student repo:
```
cd path/to/my/mat201b2015
for x in student/*/hw2/p3.cpp
do
    echo ============ $x ======================
    ./run.sh $x
done
```
Find at least one element that you like from each of at least two different programs (one of which can be your own, but at least one of which has to come from somebody else). You may use my course notes as a guide to which students did what. Feel free also to incorporate code from AlloSystem examples and from the stuff in handouts/examples. Combine them in a new way into a meaningful and functional C++ program named hw3/p1.cpp in your repo.

Start the file with a lengthy comment addressing the following questions for each program that you used:
- Where (from whom) you got it
- What you liked about it
- What portion(s) of the code "did" the "part" you liked
- Did you use this as the starting point for the final version?
- If not, how did importing selected code from this version require integration work with what you already had?

If you fell behind on homework 2, use homework 3 as an opportunity to catch up. Think of it as an extension to homework 2: you have a little more time and you have to look at how others solved challenges. Also, you have my course notes on who did what.

Part 2: Project pre-proposal

Think about what you would like to do for your final project in this class. Next Wednesday (November 4th) you will present a pre-proposal. The full formal project proposal (described below) is due about a week later. Until then it's informal brainstorming mode, but feel free to get started on however much of the actual proposal you're ready for.

Your pre-proposal must include an "elevator pitch" that you will deliver verbally in class in 30-120 seconds. We intend to audio-record these presentations and make the sound files available for class usage.

Your full proposal (due Sunday November 8th and presented Monday November 9th) must include the following:

Title (as long or short as you dare)
1/2 page abstract
1/2 page bio
One or more "sketches" explaining your idea. These can be runnable code showing some aspect of your idea, a mockup done in an image program such as Photoshop or Illustrator, a sound file, text files, or even scanned hand-drawn images, diagrams, etc., of the resulting work.
List of things you need from us to execute your vision.

The pre-proposal is non-binding---You are not committing to anything yet; the point is just to start thinking about possibilities and getting feedback from the instructors and your fellow students.