Computer Science 101
                                   Final Project
                                 Due Dec 6 at 11:59 pm

Read these directions CAREFULLY.  Failure to follow them PRECISELY will
lead to MAJOR loss of points.

--- Evaluation ---

CORRECT Components will be valued as follows:

Base                 50
Mirror                5
Gray                  5
Fade                  5
Monochrome            5
Resize                5
Bright                5
Smoothing filter      5
Westall/Sobel filter  5
Caption               5
Blended composite     5
Color transfer        5
                    ---
                    105


Missing components score 0 points.  Broken components score
NEGATIVE points (yes, missing is BETTER THAN BROKEN (in both
this class and in "real world" software!!!))

Take particular care to ensure that your program is not
sensitive to the presence or absence of blank lines and
optional comments following an input element in the control
file.

In addition to the project.txt file that you submit
I will test with other input files.

--- Programming standards ---

Adhere to the following programming standards.  Violations will
lead to deductions.

(1) no function should be longer than 30 lines code + whitespace.
(2) the maximum nesting level in any function is TWO
(3) code lines should not extend beyond column 72
(4) no more that one statement may be written on a single line
(5) use reasonably descriptive names for variables and functions
(6) your modules should compile without any warnings with gcc -Wall
(7) indenting should be consistent with logical nesting
(8) diagnostic / debug prints should be disabled/deleted in
    your submission.


--- What to submit ---

Submit code that will build correctly and without warning when I
issue the command:

   gcc -g -Wall *.c

Submit a SINGLE input file named

   project.txt

that will perform ALL of the operations your program supports in
a single run of the program. operation type. Output of one step
MAY BE USED as input to a subsequent step.


Use the following naming conventions for output images:
    user-name.operation.ppm

For example, since my user name is westall and my program implements
all eleven operations my program would create the following image files

   westall.mirror.ppm
   westall.gray.ppm
   westall.fade.ppm
   westall.monochrome.ppm
   westall.resize.ppm
   westall.bright.ppm
   westall.smooth.ppm
   westall.sobel.ppm
   westall.caption.ppm
   westall.composite.ppm
   westall.recolor.ppm

FAILURE TO USE PROPER FILE NAMES MAY CAUSE LOSS OF CREDIT WHEN
IF I DON"T SEE your output!!!!

However, if a student whose user is name is slackr  has a program that
only does gray and fade, his project file would be set up only to
create:

   slackr.gray.ppm
   slackr.fade.ppm

BE SURE TO TURN IN ALL INPUT IMAGES needed by your project.txt
file.

----------- how to turn in

1. From any departmental Solaris system ssh to workstation jmw

2. The submission directories lie in the directory

  /local/jmw2/101/project


3.  After you think you have turned your programs in, its a good idea to
    and make sure your files still compile and work correctly.

4. If you do this,  make sure that no output image files
    files are left in the directory