Homeworks-Summer 2006

Homeworks-Summer 2006

HW1: Create a Picture collage

Due Date: Mon 3 July

Implement a class with a static public void main() method that, when executed, creates and shows a collage of pictures. You need to have one picture appear four times: The original time, then three other times with some image manipulation. You're welcome to add additional pictures if you'd like. Mirroring the canvas horizontally or vertically often improves the composition of the collage, but is not necessary. You must use a Turtle to do some of your drawing.

Your method should use FileChooser.getMediaPath() to access pictures.

Turn in your PictureCollage class, any additional pictures that you add to your media folder to create your collage, and your Picture class if you end up adding any additional methods to it. Turn in via email to guzdial@cc.gatech.edu.

Please consider sharing your collage on the Gallery at Oxford-Summer 2006

HW2: Use Weaving and Repeating to Create Music

DUE DATE: Mon 10 July

Using the methods developed in class to play with linked list of music, create a song.

You must use weave and repeatNext (or repeatNextInserting) to create patterns in your music. (Which means, of course, that you have to use the SongNode and SongPhrase classes.)
You must use weave and either of the repeats A TOTAL of FIVE TIMES in your piece. In other words, repeat a set of nodes, then repeat another set, then repeat another set. Then weave in nodes with one pattern, then weave in nodes with another pattern. That would be five. Or do one Repeat to create a basic tempo, then four weaves to bring in other motifs.
You must use at least four unique riffs from SongPhrase. (It's okay for you to make all four of them yourself.)
You must also create your own riffs in SongPhrase. You can simply type in music, or you can compute your riff – any way you want to do it is fine. Just create at least one phrase (of more than a couple notes) that is interesting and unique.
All told, you must have at least 10 nodes in your final song.

You only have to use SongNode and have a single part with a single instrument.

For +2 points extra credit, use the SongPart class and create your song with more than one part and instrument.

For +5 points extra credit, implement a new kind of repeat or weave – maybe one that weaves two copies each time it does an insert? Include your modified SongNode or SongPart classs in your turnin.

You will create a class (with some cunning name like MyWovenSong) with a main that will assemble your song, then open it with showFromMeOn (or show–whatever you need to do open up the notation View on your masterpiece). Please put comments in your class:

With your name, GT-email address
Explaining what you're doing

Turn in to Mark via email:

Your song class (the .java file)
Your modified SongPhrase class.
If you end up modifying SongNode or SongPart, you can include that, too.
Draw a picture of your resultant list structure. Show us where all the nodes are in your final composition. You can do this by drawing with a tool like Paint or Visio or even PowerPoint, or you can draw it on paper then scan it in. You can turn in JPEG, TIFF, or PPT files.

Please consider sharing your music on the Gallery at Oxford-Summer 2006

HW3: Create a tiled pattern

DUE DATE: Mon 17 July

Using any of the linked lists of pictures that we created (where ordering represented linearity, or layering, or using turtles to walk the list), implement three additional methods (where firstpicturinlist is a node, not actually a picture):

firstpictureinlist.weave(newelement, n) Weave the newelement into the linked list that starts from firstpictureinlist every n nodes until the end of the list.
firstpictureinlist.addToEndNTimes(newelement,n) Put n copies of newelement at the end of the list that starts from firstpictureinlist.

You must also provide a class named PictureTest that has a main() method which utilizes all three of your new methods. When the grader executes the main(), it should (a) show a background with three or more pictures in it, (b) then show a new picture after weaving a new element into it, and (c) a third picture with some new pictures inserted at the end, and finally (d) use these methods to create a long pattern of smallish images via weaving and repeating, in order to create an interesting tiling on a long picture (e.g., at least 50 really-scaled-small nodes long) of at least 1000 pixels long with at least 25 pictures in it. Say "dog, dog, house, dog, dog, tree–repeat a few dozen times."

EXTRA CREDIT: +10 if you can make a tiling along four edges of a large image (say 1024x768).

Please put comments in your class before each of the methods that you create:

With your name, GT-email address
Explaining what you're doing:
- Each method has a comment explaining itself
- Each SECTION of the code, explains itself. For example, "Here's where I'm setting up the original list" and "Here's where I repeat the doggie scaled down to 0.25 five times."
- Variable and method names should be clear and understandable.

Turn in PictureTest, your modified file(s), and any pictures you need extra for your work via email to guzdial@cc.gatech.edu.

Consider saving your final weave to a JPEG file and show it off at the Gallery at Oxford-Summer 2006

HW4: Create an animation with sound effects

DUE DATE: Mon 24 July

Note: This is a big program. Don't leave it for the last minute!

Create an animation with sounds associated with frames.

THERE MUST BE AT LEAST 20 FRAMES IN YOUR ANIMATION.

Here's how you need to do it:

Create a tree of images that describe your scene. I'll refer to this as the scene structure.
Create another list with the sounds to be played during the animation of this tree. (Sounds could be a rest!)
Here's the key part! When you animate your scene (for at least 20 scenes!) and play your sounds, YOU CANNOT MAKE ANY NEW SOUNDS! You must play your sounds out of your list of sounds. In other words, the sounds must be pre-made and assembled in a structure before you start your animation.

You can use and modify any of the data structures that we've described in class. You can create new data structures if you'd like.

You will also need to create a class (maybe AnimationRunner?). Your TA will create an instance of this class (AnimationRunner ar = new AnimationRunner()).

The method setUp() sent to the instance (ar.setUp()) should set up the two data structures.
The method play() send to the instance should play the movie with sound.
The method replay() should replay the FrameSequence, but won't do the sound, too.

From here on, there are SEVERAL ways to handle the animation.
Here's one:

Render the first frame to a FrameSequence instance. (Make sure that the FrameSequence is shown.)
For each frame that you want to generate (There must be at least 20 frames):
- Make a change in the scene structure. Any change you want is acceptable.
- Render the scene structure.
- Play the sound in the frame list element. Use blockingPlay() instead of play() on your sound to make the processing wait (synchronize) until the sound is done before moving on. (Hint: If your sound is over 1/10 of a second long, you can't get 10 frames per second! These will be short sounds! Want something to play over two frames? Play the first half in one frame, and the second half in the next frame.) Note: You don't HAVE to use blockingPlay(). You can use a mixture of play() and blockingPlay() to get better response while still maintaining synchrony.

For 5 points extra credit, use both Sound play() and blockingPlay() in your animation play() – but NOTE that you still can't CREATE any new sounds in your animation play() method. All the sounds still have to be in some kind of linked list data structure before you get started.

For 10 points extra credit, create a new kind of linked list of sounds where there is a variable that indicates whether the sound should be (a) play()-ed or (b) blockingPlay()-ed. Still have one sound per frame, but some sounds will be starting a background sound (those of type (a)) and others will be playing a synchronization sound (those of type (b)).

Please put comments in your classes and before each of the methods that you create:

With your name, GT-email address
Explaining what you're doing
- Each method has a comment explaining itself
- Each SECTION of the code, explains itself. For example, "Here's where I'm setting up the original list" and "Here's where I repeat the doggie scaled down to 0.25 five times."
- Variable and method names should be clear and understandable.

Turn in to guzdial@cc.gatech.edu:

ALL the classes that you're using for your data structures. (You don't have to turn in Picture, Sound, FrameSequence, or its related structures (unless you've changed them), but everything you're using for keeping your sound list and scene structure.)
Any additional sounds or pictures you used, besides those in the MediaSources directory.
Your AnimationRunner class

If you want (let me know in your email to me with all the pieces), I'll create a movie from your animation and post it at Gallery at Oxford-Summer 2006. If you want to do it yourself, here's one way of doing it:

Create a method soundSave that collects all your sound files and saves them to a WAV file.
Using a tool like QuickTime Pro, read in the JPEG frames (saved by the FrameSequence) into a movie. Make sure that you use a number of frames per second that matches your soundtrack! Then add a sound track to the movie.

HW5FINAL PROJECT: Simulate an ecology around Wolves and Deer

~~DUE DATE: Tuesday 1 August~~
DUE DATE: Saturday 5 August at Noon

Using the Simulation Package developed in class, create a simulation of an ecology.

Setup

Create a dozen deer and three wolves to start.
Create three dozen pieces of corn.

When running
Let's consider a timestep to be about a week. Run the simulation for 2 years (104 timesteps). Here are the starting rules.

Deer can smell wolves within 20 steps and will move away from them. (Initial max speed is 20.)
Wolves can smell deer within 15 steps and will move to them, kill the deer, and eat it. (Initial max speed is 25.)
Deer can smell corn within 15 steps and can move to it within a single step. If a Deer lands on a Corn, it eats the corn.
If a Deer goes 2 weeks without corn, it's speed drops by half.
If a Deer goes 4 weeks without corn, it dies.
If Wolves go 5 weeks without a deer, it's speed drops by half.
If Wolves go 10 weeks without a deer, it dies.
If Corn survives for 12 weeks, it grows 2 more Corn plants next to itself (any direction). EVERY 12 weeks, it can have two more children.
Store to a file the number of Wolves, Deer, and Corn each time step.

Experimentation
You need to build Agent and Simulation subclasses to implement this scenario. But you have to explore and try different things in your simulation.

Run this simulation with these rules, three times.
Now try two other sets of rules and run each of those three times, also. Your goal is to reach equilibrium – that there are roughly as many Deer, Corn, and Wolves as you start out with at the end of the Simulation.

Things that you might want to try changing in your rules:

Initial counts	Should there be more Corn, or fewer Deer? Would culling the herd help more survive? Would more Wolves create better equilibrium?
Ranges	Should Deer or Wolves smell only closer, or farther? Should they not be able to jump to Corn or Deer in a single time step?

For +5 Extra Credit: Implement male and female Deer. Every 12 weeks, the female Deer can become pregnant if there is a male Deer within smell range. (You decide if the female jumps to the male, or the male jumps to the female.) Pregnancy lasts for 6 weeks, during which time the female will die if she doesn't get corn every THREE timesteps. At the end of six weeks, a new Deer is produced (randomly selected gender).

For +10 Extra Credit: Implement gendered Deer and male and female Wolves with the same kinds of rules

For +20 Extra Credit: Using the techniques of making the villagers and wildebeests, create an animation of your ecological simulation, where there are character shapes/figures/JPEGs instead of the Turtle shapes.

In addition to your program, you are to produce a Word file with graphs of all NINE of your runs – that's three runs of each of three sets of variables. Show all three variables – Wolves, Deer, and Corn per timestep for all three of the scenarios that you explored. Explain what you changed in each scenario and why you think the results differed from the other scenarios.

Generate this simulation as a series of JPEG frames, so that we can create a movie from them! You can upload your movies to Gallery at Oxford-Summer 2006

Please put comments in your classes and before each of the methods that you create:

With your name, GT-email address
Explaining what you're doing
- Each method has a comment explaining itself
- Each SECTION of the code, explains itself.
- Variable and method names should be clear and understandable.

Turn in to Mark Guzdial:

Your Agent and Simulation subclasses (e.g., DeerAgent, WolfAgent, etc.), including your Simulation class if you changed it. Turn in ONE scenario. The TA doesn't want three sets of Agent and Simulation classes. Turn in ONE of those sets that works for your scenario, so that the TA can check to make sure that it runs.
A Word file containing descriptions of your different runs, with graphs of results, and explanations of what happened.

CANCELLED!!!
!FINAL PROJECT: Running of the Bulls at Pamplona

DUE DATE: Saturday 5 August at Noon

Using the simulation package developed in class, and replacing the turtle with character images, create a simulation of the running of the Bulls in Pamplona.

SetUp

Create a world that is 1000 pixels long, but only 200 pixels wide.
Create 25 runners at x=50 in the world.
Create 5 bulls at x=0

During the Simulation
Let's imagine that a time step is a minute. Run the simulation for 30 minutes. You decide on the parameters like max speed and ranges to create a good looking simulation.

The runners move from the left edge to the right, but they do wander from side-to-side some – always within the lane.
Bulls also move relentlessly from the left edge to the right, but if they get close to a runner, they move toward that runner.
The runners don't want to be bumping into others. If there are three or more people too close (say within 10 steps), a person will get out of there (pick a random direction and move speed distance away – not a random speed, but maximum speed.) (It's pretty hard to set a heading toward open space, but if you can do it, go ahead!)
If a runner gets close to a bull, the runner will double their max speed for one time step just to get ahead of the bull.
If a bull catches a runner, the runner is then injured (maybe dead?) and stops. All of the bulls and the rest of the runners keep going.
Runners change physical position regularly – sometimes they're watching over their left, sometimes over their right, and sometimes they're running straight ahead. You must have at least three different positions for runners that your animations move through.
If at the start of a timestep, you're not facing the right edge, start heading back that way. REMOVEDge your heading by 10 degrees each time step to head toward the right edge (e.g., if your heading is 5, and you want to be 90, change to 15).

Generate this simulation as a series of JPEG frames, so that we can create a movie from them! You can upload your movies to Gallery at Oxford-Summer 2006

Please put comments in your classes and before each of the methods that you create:

With your name, GT-email address
Explaining what you're doing

Each method has a comment explaining itself
Each SECTION of the code, explains itself.
Variable and method names should be iclear/i and iunderstandable/i.

Turn in to Mark Guzdial:

Your Agent and Simulation subclasses
Any JPEG characters that you create.

EXTRA CREDIT: There is no requirement to have different types of runner, but I'll offer up to 5 points extra credit for having two or more types. One type of villager might look younger and move faster, another might look older and move slower. One might be TRYING to get hit by the bulls. Mark Guzdial

Links to this Page

Past Semesters of CS1316 last edited on 2 January 2012 at 8:13 pm by cc-vpn-research84.cc.gatech.edu
Syllabus-Summer 2006 last edited on 12 July 2006 at 2:23 pm by r194.worc.ox.ac.uk