Computer Science 60
Principles of Computer Science
Spring 2011


Assignment 9: Fun (and Games) with Prolog!
Due Monday, April 4 by 11:59pm

Individual or pairs    This week's problems may be done individually or in pairs (on a per-problem basis). Please be sure to indicate your partner if you do work in pairs, and make sure that you share the work fairly, as noted in the syllabus's pair-programming guidelines.

Typically puzzles ask the user to satisfy a set of constraints -- and this is precisely what prolog was designed to do. In this assignment you will be using prolog to solve several different types of puzzles. The work involved is primarily in representing the puzzles and their rules. In order to help the graders, please check that you name your prolog rules (predicates) as they're specified in the assignment.

Feel free to use Prolog's built-in predicates in solving these puzzles. In particular, Prolog has a built-in length(L, N) which is true if and only if list L has length N. member( X, L ) is built-in to at least some versions of Prolog. You may use your removeOne from the previous hw (or use this one:

removeOne(X,[X|R],R).
removeOne(X,[F|R],[F|S]) :- removeOne(X,R,S).
Also, Prolog also has a built-in append(A, B, C) which is true if and only if the result of appending list B to the end of list A results in list C.

And certainly feel free to define your own helper rules as needed!


Submission    Please submit your problems in separate files named

You will find starter files for each of these parts at the top-level assignment page.



Part 1: Einstein's logic-constraint puzzles (25 Points)

Note on spelling: Be careful with the various names in this problem -- you'll want to keep the spelling consistent. In particular, be sure collette is with two l's and two t's. (We've tried to be consistent ourselves; if you see any problems, let us know!)



For this problem, your task is to write a set of prolog rules that will solve the following logic puzzle (in the spirit of Einstein's Zebra Puzzle):

/*
 * algird, bruno, collette, dino, and edwina are each from different
 * one of five colleges: pomona, pitzer, hmc, cmc, and scripps.
 *
 * Each one brings a different snack:  jots, chocolate, donuts, pez, and spam.
 * They are all on the train together in seats 1 through 5.
 *
 * We want to know which student is in each seat, what college does each
 * student attend, what did each student bring for a snack?
 * Determine whether there is a solution, and if so, whether it is unique.
 *
 * 1.  bruno and dino sat in the end seats.
 * 2.  algird sat next to the student from hmc.
 * 3.  collette sat next to friends with chocolate and donuts.
 * 4.  The hmc student brought spam as a snack and sat in the middle seat.
 * 5.  chocolate was immediately to the left of pez.
 * 6.  bruno, dino, and algird do not go to Scripps.
 * 7.  The pomona student sat between the persons with jots and spam.
 * 8.  dino did not sit next to the person with donuts.
 * 9.  The cmc student did not sit next to edwina.
 *
 * Note that negation constraints don't generate values -- they can
 * only check for consistency of already-instantiated values. Thus,
 * they must be tested _after_ variables are instantiated with values.
 *
 * Here is the solution (which is helpful to have for debugging!)
 *
 * Seats =
   [[bruno,cmc,jots],          % Seat 1
    [algird,pomona,donuts],    % Seat 2
    [collette,hmc,spam],       % Seat 3
    [edwina,scripps,chocolate],% Seat 4
    [dino,pitzer,pez]]         % Seat 5
 *
 */

Be sure to format your output in an easy-to-read manner. In addition, make sure that you leave a comment for the graders so that they know how to generate and print the solution to the puzzle. As an example, consider the solve predicate in the einstein.pl example. It first generates the solution to the Zebra puzzle, and then it prints the five houses in a reasonable fashion:

solve :-
  einstein( [ H1, H2, H3, H4, H5 ] ),
  write( ' first house: '), write(H1), nl,
  write( 'second house: '), write(H2), nl,
  write( ' third house: '), write(H3), nl,
  write( 'fourth house: '), write(H4), nl,
  write( ' fifth house: '), write(H5), nl.
This zero-argument predicate solve is called as follows:
?- solve.

 first house: [norwegian, cat, dunhill, water, yellow]
second house: [dane, horse, marlboro, tea, blue]
 third house: [brit, bird, pallmall, milk, red]
fourth house: [german, zebra, rothmans, coffee, green]
 fifth house: [swede, dog, winfield, beer, white]

Yes

Please submit this part of the assignment in a file called logicpuzzle.pl.




Part 2: The Game of 24! (25 Points)

This problem asks you to use Prolog to provide a solver for a generalized version of the game "Twenty-Four". In the original game, players view a card with four numbers on it and try to make an arithmetic combination of the numbers using the operators +, -, *, / so that the result is 24 (parentheses are allowed but are implicit). Each number must be used exactly once. Each operator can be used any number of times.

In our generalization of the game, the fixed number 24 is replaced with a variable, the set of operators is specified in a list, and the list of numbers can have any length, not just 4. (By definition, no result can be made if the list is empty.)

Define a 4-ary predicate solve such that

     solve(Ops, Values, Result, Tree)
  
will solve for an arithmetic tree named Tree using operators Ops among the integers in Values to give the final value Result. For example,
 solve(['+', '*', '-'], [2, 3, 4, 5], 24, Tree).

 Tree = [*,[+,[-,3,2],5],4] 
 

This means that we have found a solution Tree using operators +, *, and - such that the solution combines the numbers in the list [2, 3, 4, 5] to yield 24.

You may assume that the set of operators will always be a subset of ['+', '*', '-', '/'] and that '/' denotes integer division. In prolog, integer division is performed using // (which is why 1-line comments in prolog are prefaced by % and not //).

Here is an eval predicate (for evaluating trees of opreations) that will be helpful in solving this problem. You may copy this code and use it freely. Note that eval can handle numbers and it can handle trees that are bound to some value (using the nonvar predicate) Thus, the eval predicate can not generate trees. Allowing eval to generate trees can lead to infinite recursion, as it looks in the (unbounded) space of trees for operations possibly leading to R.

    eval(R, R) :- number(R).
    eval(['+', A, B], R) :- nonvar(A), nonvar(B), eval(A, AR), eval(B, BR), R is AR + BR.
    eval(['*', A, B], R) :- nonvar(A), nonvar(B), eval(A, AR), eval(B, BR), R is AR * BR.
    eval(['-', A, B], R) :- nonvar(A), nonvar(B), eval(A, AR), eval(B, BR), R is AR - BR.
    eval(['/', A, B], R) :- nonvar(A), nonvar(B), eval(A, AR), eval(B, BR), BR\==0, R is AR // BR.
 
You may use any of Prolog's built-in rules and any helper rules that you like (including those that we wrote in class).

Here are some other examples of solve in action. Warning: You may especially want to check the second of these. In particular, a common partially working solution to this problem handles the first example below, but not the second example. Note how the list of values is being split into sublists in the second case:

  solve(['+', '*', '-'], [1, 2, 3, 4], 24, Tree).

  Tree = [*,1,[*,2,[*,3,4]]]    % other solutions are certainly possible!



  solve(['+','-','*','/'], [2,8,22,424], 42, Tree).  % only one solution possible!

  Tree = [-,[/,424,8],[/,22,2]]



  solve(['+'], [1, 1, 1, 1], 24, Tree).   % no solution

  No.



  solve(['+'], [24], 24, Tree).    % base case

  Tree = 24
 
Notice that a plain integer is the simplest possible solution tree (not the one-element list, [24]). Also, there are many more answers to the first example above.

For 20 points, your solve predicate should work as above, generating trees (with a value provided for Result). For the final 5 points, your predicate should also be able to generate the Result value (as well as the tree):

?- solve(['+', '*', '-'], [1, 10,100, 1000], N, Tree).

N = 1111,
Tree = [+,1,[+,10,[+,100,1000]]] ;

N = 1110,
Tree = [*,1,[+,10,[+,100,1000]]] ;

N = -1109,
Tree = [-,1,[+,10,[+,100,1000]]] ;

N = 11001,
Tree = [+,1,[*,10,[+,100,1000]]]   % and many, many more...
Note that the eval predicate given can check or generate the result value R.

Please submit this part of the assignment in a file called twentyfour.pl.




Part 3: Mudder, Alien, Spampede, Spam! (25 Points)

In this part of the assignment (riverpuzzle.pl), you will write a Prolog program to solve the famous Mudder, Alien, Spampede, and Spam puzzle described in class (this is similar, but far superior to, a puzzle known as "Man, Fox, Hare, and Lettuce" problem you may have sen before). Please submit your solution in a file called riverpuzzle.pl.

You should carefully review the solution to the Towers of Hanoi problem that we developed in class. The big ideas in the two programs are very similar.

Your solution should specify valid moves in this puzzle and Prolog should use these rules to infer at least one correct solution to the puzzle. It need not be the shortest solution, but it must be valid. Moreover, Prolog (in its "infinite" wisdom) may give you the same solution many times. That's just Prolog being Prolog and it's OK!

Here are the details:

When your program is done, you will be able to run it like this:

?- solve([[mudder, alien, spampede, spam], []], X).

X = [mudder_takes_spampede_right, mudder_goes_left, mudder_takes_alien_right, 
     mudder_takes_spampede_left, mudder_takes_spam_right, 
     mudder_goes_left, mudder_takes_spampede_right]

true
A few notes on this program:

Tips!   

Submit this problem under assignment #9 as riverpuzzle.pl.



Part 4: Grammars in Prolog (25 Points)

In Assignment 4 you wrote a recursive descent parser in Rex for a grammar for arithmetic expressions involving addition, multiplication, and exponentiation. In this assignment you will write a general "parse engine" in Prolog which will allow you to determine if a given string can be successfully parsed by virtually ANY grammar that you give it! Amazing, but true!

Here, the goal is not to determine a parse tree, but we DO want to know if there EXISTS a parse tree for a given string using the given grammar. For example, IF we had a grammar for the English language, we would be able to ask our parser if a particular sentence was valid in English. The neat thing is that we won't tell Prolog how to parse, we'll just tell it what a grammar is and what string we're interested in and ask: "Hey Prolog, can this string be parsed by the given grammar?"

Take a look at the files g0.pl,g1.pl, g2.pl, g3.pl and g4.pl supplied to you at the top-level assignment directory. Each of these files specifies a different grammar. A grammar is specified by declaring the variables, terminals, and rules.

For example, consider the grammar for valid additions of 0's and 1's. (This is the grammar specified in the file g0.pl.)

s -> v + s | v
v -> 0 | 1 
Here, s and v are the variables and 0 and 1 are the terminals. Notice that no upper-case letters are used. This is important, as Prolog uses upper-case letters to represent its own variables.

You can see how this grammar is specified in file g0.pl Our convention is as follows: Variables are stated as facts. These facts simply state the names of the variables. In this example, the facts state that s and v are variables as shown below.

variable(s).
variable(v).
We also specify which symbols are terminals as shown below.
terminal(0).
terminal(1).
terminal(+).

Finally, the grammar rules are stated as ordered pairs, where the first element is the left-hand-side of a rule and the second argument is the LIST of elements appearing on the right-hand-side of that rule. For the grammar above, these rules are stated as shown below.

rule(s, [v, +, s]).
rule(s, [v]).
rule(v, [0]).
rule(v, [1]).

Your task is to write a general-purpose parser. This file will contain the rules for a predicate called parse. As described in class, parse takes as input a sentential form, i.e., lists of terminals and nonterminals, as its first argument. The second argument will be a list of symbols (terminals) to parse. Then, parse should respond Yes if and only if the sentential form derives the list of symbols using a leftmost derivation for the grammar.

In particular, we will only test your parse predicate with two fully-instantiated lists: the first will be the list of the grammar's start variable (not a Prolog variable) and the second will be a list of symbols to be parsed by that grammar (also not a Prolog variable).

For example, here are some sample inputs and outputs:

| ?- [parser].            <--- HERE WE ARE LOADING IN OUR parse PROGRAM
yes 

| ?- [g0].            <--- HERE WE ARE LOADING IN A GRAMMAR
yes

| ?- parse([s], [1, +, 0, +, 1]).   <--- note that everything is instantiated...
yes

| ?- parse([s], [1, +]).
no

| ?- parse([s], [1, 0, +]).
no

You should write the parse inference rules in a file called parser.pl and submit that file. Keep in mind that although we will only call parse with a one-element list (of the start symbol) as a first argument, you may want to write the predicate more generally than this to help with the recursion... .

Your code will assume that there are facts already defined for the grammar using the names variable, terminal, and rule as illustrated above. Keep your code simple and elegant and be sure to test it thoroughly on the supplied grammars before submitting it. This can be done using only three lines of code for parse:



Optional Bonus Problems

You may submit either or both of these two problems for +5 and +10 points, respectively. The first one you should include in your parser.pl file. The second one should be submitted in a file named puzzle.pl.

Generating parsable statements (token lists)

For this problem, add a predicate named parseGen to your parser.pl file. This parseGen predicate should be identical in interface to problem #4's parse predicate. However, it should be able to generate all of the valid statements (actually, lists of tokens) that the second input represents. That is, parseGen should be able to be called as

parseGen( [s], TokenList ).
and should respond with all of the TokenLists that can be parsed starting from the sentential form in the first input. The first input will still be a nonvar, as it is with parse.

All?    Note that there are likely to be infinitely many token lists that work. Prolog will be OK with this and your parseGen should be happy to keep generating new ones, as long as you're willing to type semicolons. However, because there are infinitely many, testing with setof will not work.

Include a comment next to parseGen that explains your approach and why it will, given enough time and memory, generate any valid (parsable) token list.



Choose-your-own-puzzle

We've seen several puzzles and the solutions for these puzzles written in Prolog. For up to +10 bonus points (depending on the complexity), write a Prolog program to solve your favorite puzzle. Here are the requirements: