Jeff Lindborg
8631842
lindborg@wolf
c473bl@coco


Bike-assembly

#3.
 My domain takes a list of parts (a combination of 'stock' parts and optional parts
that are specified by the user) and assembles a bike out of them.  I have a few
stock bike packages such as mountain bike and race bike that adds all the necessary
parts to the bike to create that kind of bike.  The user can then specify a list of
optional parts (such as mirors, squeeze-horns, decals, fenders etc...) that are then
added to the stock model bike.  
   I have gone to great pains to make my domain easy to expand.  For instance it is 
easy to add new types of bike parts and even easier to add new kinds of types (for
instance a special kind of frame or tire) of parts to the state.  You do not need 
to add operators to the domain... only alter my nifty NEEDS list and ATTACHES-TO 
list in the start state (please see the state and domain for further explanation).
All in all it works pretty well.  I did add a few control rules so it is able to 
solve complete, rather complex problems.


#4.
    I spent around 40-45 hours on this.  I was done with it on Thrusday when I 
    decided to change it and started over.  Akk!  The first way was not general
    enough and required too many specail operators that this version does not.


#5-#6.
    The only ideas I got from the other domains was the painting/prime/sand gotten
    from the SCHEDWORLD domain.  They are rather trivial operators though.  The rest
    is from my own, sometimes deeply disturbed, mind.


