Checking your work and hints
|
Submit the following files:
readme.txt htree.c art.c input1.txt input2.txt
Do not use different file names or capitalization,
even for your artistic creation.
Be sure that your
htree.c reads in the single integer n from stdin.
Be sure that you submitted the two companion input files
for your art.c program.
Your turtle graphics output must do the following, or you
may receive severe penalties:
view and print properly (via turtle and ghostview).
If it doesn't, name your C programs
htree-bad.c or art-bad.c so that we do
not waste paper and time trying to print them.
stay within the 512 x 512 box.
be less than 3MB in size.
The readme.txt file should contain the following information.
Here is a
template readme file:
Name, precept number, high level description of code,
any problems encountered, and whatever help
(if any) your received.
Description of your artistic creation and how you
went about creating it.
Although it is not mentioned in the assignment, we'll award extra
credit if you follow the above instructions to create an image for
the Display Wall. This requires no programming and can be alot of fun!
The two extra credit opportunities below are
intended to challenge the more advanced
students. If you are still struggling with
the basics of recursion, you will probably benefit more
by understanding the recursion examples in the lecture notes
and readings than by attempting the extra credit.
Combine the two main concepts you have been using and
write a recursive PostScript program (not for the
squeamish)! Name your PostScript program extra.ps.
Or "un-recursify" your program in a bottom-up
manner. Name your program extra.c.
Here are the display wall submissions from
Spring 2001,
Fall 2001, and
Spring 2002.
Kevin Wayne