Assignment 3 Submission

Specific notes for Assignment 3

• The web tester will only run tests on problems 2 and 3.

• You should also submit your ep-heuristic procedure in the same file. We will run tests on this procedure later (offline). I expect that about half the points for problem 4 will be based on your heuristic performance, and the rest will be based on what you did for your heuristic. (E.g. for this other half, someone who implemented a more complicated heuristic will receive more points than someone who implemented a simpler heuristic.)

• The challenge problem should be submitted separately. (See the links below.)

Policy for electronic submission for Assignment 3

• You may submit of your code up to 3 times.

• For your third submission, there will be a 5% reduction in your score. This should encourage you to get it right on one of your first two submissions for which there is no reduction. Any late penalties will also be deducted.

• Your grade will be the maximum of your submissions (with any applicable reductions to each one individually).

How it works

• First, your code is run through a "syntax checker" which ensures that you aren't using certain advanced Scheme constructs that are (for now) prohibited. Your code must pass this test in order to be submitted. If you stick with the forms covered in the Scheme handouts, you will be fine.

  Your code should consist only of define statements.

  The restrictions on advanced Scheme forms are:

  • Certain forms are explicitly prohibited: eval, and any kind of mutator (such as set!). There are other prohibited forms, but you shouldn't have any occasion to use them.
  • The syntax checker is currently not equipped to handle named lets.

• Next, your code is checked to make sure that all the procedures for the assignment are defined (and that they take the correct number of arguments). If there is anything missing, you will get a warning message, but you can still continue the submission.

• Finally, your code is tested.

• You will get your score and some feedback immediately. A full transcript of the tests run on your code will be emailed to you when the assignment is returned.

Submitting your code

• You need a CS account (with Kerberos password) which you should all have by now. If you have a problem with your CS account this weekend, email Prof. Huang. After this weekend, contact Zie Kone (konez@cs.rpi.edu). If for some reason need your password reset, contact labstaff@cs.rpi.edu. They might not be able to help you this weekend.

• To submit problems 2, 3, and 4, go to the Assignment 3 Web Tester. You will probably need to accept the site certificate from the server.

• To submit problem 6 (the challeng problem), go to the Assignment 3 Challenge problem submission page. Use this page to submit your solution for problem 6; it will not run tests on your code --- we will do this offline.