Check Your Submission
After all of the work you've done, it's important to make sure that your submission is in good shape and that you won't lose points for silly things.
Autograding Tools
We have included some autograding tools in the tar file—btest,
dlc, and driver.pl—to help you check the correctness of your
work. (These tools are also used when evaluating your work, so
passing their tests is important for your grade.)
Remember that your code must compile and run on wilkes. You
should also run the autograding tools against your code on the
server to ensure your code will work when being tested for grading.
btest
This program checks the functional correctness of the functions in
bits.c. To build and use it, type the following two commands:
make
./btest
Notice that you must rebuild btest each time you modify your bits.c file.
You'll find it helpful to work through the functions one at a
time, testing each one as you go. You can use the -f flag to
instruct btest to test only a single function:
./btest -f bitAnd
You can feed it specific function arguments using the option flags
-1, -2, and -3:
./btest -f bitAnd -1 7 -2 0xf
Check the file README for documentation on running the btest
program.
dlc
This is a modified version of an ANSI C compiler from the MIT CILK group that you can use to check for compliance with the coding rules for each puzzle. The typical usage is
./dlc bits.c
You may need to make dlc executable with this command: chmod +x
dlc. Note that the program runs silently unless it detects a
problem, such as an illegal operator, too many operators, or
non-straightline code in the integer puzzles. Running with the -e
switch,
./dlc -e bits.c
causes dlc to print counts of the number of operators used by each
function. Type ./dlc -help for a list of command line options.
driver.pl
This is a driver program that uses btest and dlc to compute the
correctness and performance points for your solution. It takes no
arguments:
./driver.pl
Your instructors will use driver.pl to evaluate your solution.
Submitting Your Work
Be sure you've run BOTH btest and dlc to check for issues before you
submit! Also check that you've included both partners names/logins in
the comments at the top of bits.c and that you've removed any
extraneous print commands.
From the command line on wilkes, in your lab directory, type
cs105submit -a 01 bits.c
You should get a response saying that one file has been submitted and that you will get an email confirming your submission.
Note that you can resubmit as often as you want up to the deadline. Only the most recent submission will be graded.
Do not make any submissions after the deadline unless you are using late days.
(When logged in, completion status appears here.)