Final Project Assignment 2: Exploration (FP2)

DUE Wednesday, March 23, 2016

Exactly like Exploration 1: https://github.com/oplS16projects/FP1. Do a different library. Explore something different, either related or completely not. Try something else out. This is also an individual assignment. Be sure to do your write up in the FP2 repository, and pull request against it to turn in.

During this assignment, start looking for teammates! Use the email list! When posting on the email list, be sure to include:

• what you're interested in doing
• what libraries you looked at for FP1 and FP2
• when you will be able to meet to work on project

The following libraries are not allowed for project explorations:

• games/cards
• racket/gui
• racket/draw

You can still use these in your project, but you must explore different libraries for this assignment.

##DELETE THIS AND EVERYTHING ABOVE IT BEFORE SUBMITTING

My Library: (library name here)

My name: Write what you did! Remember that this report must include:

• a narrative of what you did
• highlights of code that you wrote, with explanation
• output from your code demonstrating what it produced
• at least one diagram or figure showing your work

The narrative itself should be no longer than 350 words. Yes, you need at least one image (output, diagrams). Images must be embedded into this md file. We should not have to click a link to see it. This is github, handling files is awesome and easy!

Code should be delivered in two ways:

1. Full files should be added to your version of this repository.
2. Key excerpts of your code should be copied into this .md file, formatted to look like code, and explained.

Ask questions publicly in the email group.

How to Prepare and Submit this assignment

1. To start, fork this repository.
2. (This assignment is just one README.md file, so you can edit it right in github)
3. Modify the README.md file and commit changes to complete your report.
4. Add your racket file to the repository.
5. Ensure your changes (report in md file, and added rkt file) are committed to your forked repository.
6. Create a pull request on the original repository to turn in the assignment.

Project Schedule

This is the first part of a larger project. The final project schedule is here