Final Project Due, MEOM June 11

Submit your final project to my dropbox by the MEOM, Wednesday June 11.

Zip up your project as usual and MAKE SURE TO INCLUDE A README that explains:

1. How to run your program

2. What your project does/doesn’t do.

3. Anything in particular I should take note of when running project.

A NOTE ON GRADING:

For this project, I’m concerned about it’s execution more than I am about its design or the format of your code.  The focus here is on results more than style.  I may look at the code out of interest, but I will evaluate the work based more on what I see as a user of your program than as a teacher “looking under the hood.”

Cyclist Game Code

Here is the cyclist example from class.

WARNING: code is not clean or well commented.  But it should give you a point of reference for a program that you’ve seen working.

Franke_Speeder.zip 

Graphics Lab :: Due Monday (see below)

Here’s a Lab/Activity for you to do that builds on what we’ve been doing in class and adds animation! Wheeee!

REQUIRMENT: “Tasks” 1 and 2 are due by monday. I will not collect, but you’ll need to have them done. Move on to task 3 if you have time.

Starting files: GraphicsDemo.zip
Assingment Sheet: CyclistLab.pdf

Catching Plagiarists DUE: MEOM Monday, April 28

This assignment carries a SIGNIFICANT portion of your Spring Quarter grade.  This thing should be immaculate.

In particular make sure that:

1. You include a README describing how to use your program, what works and what doesn’t work.  In particular I need to know how large a document set I can test on.

2. Your code should be cleaned up, formatted well, and well-commented.   Comments in the code should explain what complicated sections of code are doing.

3. Also, a second section of the README that *briefly* explains the strategy you used and what data structures you employed to solve the problem.  Please also declare what you think the big-oh running time of your program is, and show how you derived that.

TURN IT IN:

Rename your project : CatchPlagiarists
Zip it up into a file called username.catchPlagiarists.zip
Submit it to my dropbox by the due date.

Lab 23 :: Grid Implementations - Due. Monday, April 21

The assignment is long enough to warrant an assignment sheet: Lab23_GridImplementations.pdf

You should have all of the starting code you need.  You will write these implementations into the same project you wrote your Bee in.

“Review and Do” - Due Friday, Apr. 11

We’ll review by working backwards.  Since we still have some work to do with Grid World, we’ll start with that.

REVIEW:

  1. Read/Review Litvin pp. 151-169 which covers Grid World topics up through “Critters.”  Try the MC questions to see how you do.  NOTE: Litvin’s example MC questions are usually much longer and harder than what you’ll actually find on the exam - do not freak out.
  2. If you need more, it covers the actual case study, parts 1-4 of the Case Study Student Manual.
  3. You *should* have done and played with the examples given in these parts during the labs while I was out of town.

DO:
As an exercise, do the Bee Critter implementation that’s described on p. 167 of Litvin.
You may implement a different Critter than a Bee if you like, but it must be a sub-class of critter and override the appropriate methods  - if you can confirm an alternate implementation if you like.

Turning it in:
You will run a demo of your implementation for me IN CLASS on Friday.

CP Milestone 1:process documents. Due: Monday, Apr. 7 in class

 Assignment: process a directory of text documents, printing out all 6-word chunks from all files.For this assignment, just printing the chunks to the console is adequate.  While you’re at it, you might as well make the chunk-size a variable since you might want to vary that in the future.You can get the document sets from here:http://people.ucls.uchicago.edu/~bfranke/nifty.bfranke/#documentSets  Obviously, if it works for the small set, it will work for the bigger sets.  Please see the HOW-TO for help on How to Process a Directory of Files  Turning it in:You will NOT turn this in.  Rather, you will run a demo for me in class on Monday and I will check off that you’ve done it. 

Lab22 :: Quick HashMap - Due: MEOM Wed. April 2

Implement your own HashMap…quickly!

Do this Lab with a partner.

Starting Files: Lab22_QuickHashMap_stuDistro.zip

Grading: Does it pass all the tests?  If yes, A.  Otherwise,  depends on severity of problem.

Turning it in:
Important: Rename the project folder: lab22.username1.username2
Zip it up and put it in my Dropbox by the due date.

Lab Activity - Java Bat

So as we head into the break I thought I’d show you a great review tool that I found:

http://www.javabat.com

  •  Today: Do as many exercises in javabat as you can in the period.  It’s fun to see how many you can rip throuhg. You may want to set up an account so it can keep track of what you’ve done.  Many problems go in series and you won’t want to have to redo the series to get to the harder problems.
  • To keep yourself fresh over the break, consider “playing” javabat occasionally, maybe do an exercise every day.  Treat it as a game.  If you do, you will find yourself very well prepared for the types of questions they ask on the AP test.

IMPORTANT:

  • I’m going to be finishing my grading in the next few days.  Make sure you have everything turned in.  Check your email.  If there’s something important I don’t have, I’ll try to email you about it.

 HAVE A GREAT BREAK!!!!

Intro to Grid World - Mar. 12,14

This essentially comprises an actual laboratory exercise. You will not have to turn this in, but if you don’t do this you will be totally lost when we do more advanced work with the Grid World that you will have to turn in. So, that being said, here you go….

1. Here is the Grid World Student Manual.
Please don’t print it out - it’s not worth it.

2. Notice that I’ve added the Grid World API documentation to the sidebar on the right.

3. Download the Grid World Code and unzip it.
This is a slightly modified version of the code that comes from the College Board. I modified it so that the sample projects are actually BlueJ projects that will work without modifying your blueJ setup. We’ll talk more about what’s in here at a later time - feel free to explore on your own though.

4. Open the blueJ project called “firstproejct” which can be found in GridWorldCode->projects->firstproject. Compile it and …

STUFF YOU HAVE TO DO:
(Note: when I say “read” below I mean read what you need to. I would recommend first looking at what you have to do and then looking through the reading to find answers to your questions. If you’re the kind of person who likes to read from front to back, then by all means, do that.)

1. You’re now ready to begin READING (YEA!) Part I of the student manual. Do take the time to mess around with the stuff that’s introduced in Part 1.

2. Read part 2 - it refers to “BoxBug” project which can be found in the same folder as the firstproject. As you read at least think about the “Do you know?” questions as you go through it.
DO EXERCISES: 2, 4

3. Read Part 3 and DO the “group activity” - writing the Jumper class and JumperRunner - on your own. There is no example project for this one. You can either make a new project (make sure to include a +Libs folder with gridworld.jar file in it) or just write it into the last project your had working.

Read the “What makes it run?” section at the end of part 3.

4. If you get to this point email me. This is the first year of GridWorld so I have no idea how long it will take.