submit
system.
Each submission must also have a makefile and a log file (see below for log file requirements).
assert
s or (C++) uncaught exceptions.
valgrind
should report no errors.
makeit
and testit
(see below).
Project | Due Date (yyyy-mm-dd) |
Description |
---|---|---|
1 | 2017-09-13 | Distance Calculator |
2 | 2017-09-27 | SpinOut |
3 | 2017-10-11 | Conway's Soldiers |
4 | 2017-10-25 | Cooccurrence Matrix |
5 | 2017-11-08 2017-11-10 |
Polymorphic Game |
6 | 2017-11-29 | Game Framework I |
7 | 2017-12-11 | Game Framework II |
% /c/cs427/bin/submit 1 Makefile tokenize.c unique.c time.logsubmits the named source files as your solution to Homework #1;
% /c/cs427/bin/check 2lists the files that you have submitted for Homework #2;
% /c/cs427/bin/unsubmit 3 error.submit bogus.solutiondeletes the named files that you had submitted previously for Homework #3 (i.e., withdraws them from submission, which is useful if you accidentally submit the wrong file);
% /c/cs427/bin/makeit 4 tokenize uniqueruns "make" on the files that you submitted previously for Homework #4;
% /c/cs427/bin/protect 5 tokenize.c time.logprotects the named files that you submitted previously for Homework #5 (so they cannot be deleted accidentally);
% /c/cs427/bin/unprotect 6 unique.c time.logunprotects the named files that you submitted previously for Homework #6 (so they can be deleted); and
% /c/cs427/bin/diffit 7 unique.c time.loguses /usr/bin/diff to compare the named source files with the versions that you submitted previously for Homework #7; and
% /c/cs427/bin/retrieve 8 Csquash.cretrieves copies of the named files that you submitted previously for Homework #8 (in case you accidentally delete your own copies).
ESTIMATE of time to complete assignment: 10 hours Time Time Date Started Spent Work completed ---- ------- ---- -------------- 8/01 10:15pm 0:45 read assignment and played several games to help me understand the rules. 8/02 9:00am 2:20 wrote functions for determining whether a roll is three of a kind, four of a kind, and all the other lower categories 8/04 4:45pm 1:15 wrote code to create the graph for the components 8/05 7:05pm 2:00 discovered and corrected two logical errors; code now passes all tests except where choice is Yahtzee 8/07 11:00am 1:35 finished debugging; program passes all public tests ---- 7:55 TOTAL time spent I discussed my solution with: Petey Salovey, Biddy Martin, and Biff Linnane (and watched four episodes of Futurama). Debugging the graph construction was difficult because the size of the graph made it impossible to check by hand. Using asserts helped tremendously, as did counting the incoming and outgoing edges for each vertex. The other major problem was my use of two different variables in the same function called _score and score. The last bug ended up being using one in place of the other; I now realize the danger of having two variables with names varying only in punctuation -- since they both sound the same when reading the code back in my head it was not obvious when I was using the wrong one.but MUST contain
This log will generally be worth 5-10% of the total grade. To facilitate analysis, the log file MUST be the only file submitted whose name contains the string "log" and the estimate / total MUST be on the only line in that file that contains the string "ESTIMATE" / "TOTAL".