Submission

How to Submit

To submit your project, all you need to do is leave your files in your Gamesman directory and not touch them and then fill out the form on ucwise to tell us where to find them. If you are working on Gamesman from home, it is imperative that you copy all your files back to your CS3 account when you're finished AND test them in the lab (since that's where we'll be grading your projects). We will use the Unix command ls -l ~/ucwise/gamesman to determine when the files (listed below) that are required for the Submission were updated last. Please run this command now. As you can see, the next-to-last column contains the date and time each file in your Gamesman directory was modified.

• Final project is due on Saturday, December 6, 2003 @ 11:59 pm. You should not modify the required files after this time.

Opening a file in an editor (and saving) will change its last updated time, so don't do it. If you would like to open the files for any reason, you should copy them and open the copies. For instance, if you would like to keep working on your GUI or other cool features after Wednesday, just copy your game module mx.scm to, say, mx-demo.scm and keep working on the demo:

% cp mkonane.scm mkonane-demo.scm

You can press "O" in Gamesman's Load Menu to load this demo file; Gamesman will not know to load it automatically because the file name is not of the form mx.scm. But remember, we will look only at the mx.scm. You should not need to copy the game trees since their modification date is not updated when they're read in by Gamesman.

What to Submit

Your Submission should consist of the following:

1. Your game module. Please make sure it is called mnorthcott.scm, mkonane.scm, msurround.scm or mknightsdance.scm and loads smoothly through Gamesman.
2. Game trees. You should provide us with four game trees named as below:
   1. standard.tree -- the standard game; no special rules.
   2. misere.tree -- the misére game; no special rules.
   3. compulsory.tree -- game with only the rule that you were required to implement.
   4. user.tree -- game with only the rule you created yourself; if you implemented several rules, choose the one you like best.
   Feel free to include one or two other game trees that you think are fun. You can name them anything you want. These may illustrate your other rules, or a neat combination of rules that you have encountered. Any trees in addition to the above four are utterly optional.
3. isolation.txt A file containing tests of your functions outside Gamesman. You should have 6-10 tests for the six main functions, 4-8 tests for important helpers and under four tests of any remaining procedures. Use your judgment to guide the thoroughness of your testing. Most of your functions need to be tested, but not all of them. We don't need to see testing of the trivial helpers. Functions that produce graphics need not be tested. You can call set-rule! and get-rule outside of Gamesman (just make sure Gamesman is loaded) to test your functions under various rules.
   There is no specific format for isolation.txt. You need not include comments (but you can if you want). Use copy/paste to help generate this file.
4. overall.txt This file should contain one or two sessions with Gamesman. Use it to show off your final product. Show us how your print-help changes under the various rules. Show us the cool rules you have, etc. Of course, there is no way you can show us your graphics here. We'll look them over ourselves.
5. overview.txt This file should contain a very brief description of your project. We mean brief: less than 24 lines if you can help it. The overview.txt should have:
   1. Yours and your partner's (if you have one) name and login
   2. The name of your game
   3. How you split up the work (if partnership)
   4. A description of the extra rule(s) you've come up with
   5. A description of any fancy graphics you did
   6. Anything else you think we need to know
   But remember to keep it brief. It should look more or less like this example overview.

All files you turn in should be plain text files. Do not submit MS Word documents. Your file is in plain text if you can view it through the more Unix utility:

% more overview.txt

To re-name a file foo.txt to bar.txt, use the mv Unix utility:

% mv foo.txt bar.txt

Gamesman ©2003 Dan Garcia. All rights reserved. Site design by Steven Chan. Site maintained by Hesam Samimi.