Problems 1 and 2 must be sumbitted together (due 10/18).
Problem 4 must be submitted separately (due 10/25).
Problem 5 must be submitted separately (due 10/25).
Policy for electronic submission for Assignment 4
You may submit your code up to 3 times to each submission page,
i.e. you have 3 attempts each for Problems 1 and 2 (together) and for
Problem 4. Problem 5 is an exception to this policy; you may submit
an evaluation function as many times as you wish.
Your submission to any submission page should include all
problems for that page. Any omitted problem or procedure will score 0
points.
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.
Your grade will be the maximum of your submissions. Any late
penalties or third submission reductions will be applied separately to
each submission and each submission page. For Problem 5, the current
version of your evaluation function as of 10am Thursday November 1
will be used for testing; therefore there is only one "official"
submission for Problem 5.
We reserve the right to deduct "submission penalties" for any
submission for which we must manually intervene because of submission
errors on your part.
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.
Your code should consist only of define statements.
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. If you stick with the forms covered in the Scheme
handouts, you will have no problem.
Note: the syntax checker is currently not equipped to handle named
lets.
The syntax checker is not foolproof --- just because it passes
the syntax check does not mean that it will run (or even load) without
errors.
Next, your code is checked by a "pretester" to make sure that
your file loads without error and 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 for some reason need your password reset, contact
labstaff@cs.rpi.edu.
Assignments will only be accepted through the web tester.
If you want to check that your Kerberos password works OK before
you make a submission, go to the
web tester tester.
If you want to run the syntax check on your file (which might
help in your debugging if you are having syntax problems), go to the
syntax checker page.
Problems 1 and 2
Ask the
Oracle for correct answers to your inputs.
Submit your solutions to the
Problem 1 & 2 Web Tester.
NOTE: the web tester will deduct a late penalty even if you've
signed up for the automatic extension. We'll add these back in later.
You can upload an evaluation
function as many times as you want; there are no penalties for
repeated submissions. Your statistics (win/loss) are not reset when
you upload a new evaluation function.