PA Submission Policy

You submit your PAs by (1) uploading your files to Vocareum, and (2) pressing “Submit”. (see "Submitting on Vocareum" section below for submission instructions.)

Here are some policies about PAs submission:

• We will grade only the files that you submit through Vocareum. It is your responsibility to ensure you have uploaded the correct files and submitted them.
• You may submit your code as many times as you want before the deadline. We will grade only your latest submission. We encourage you to begin submission as early as possible, at least several hours before the deadline.
• We will test and grade your code on Vocareum. You must ensure they run correctly on Vocareum before you submit them. You can compile and run them in the Vocareum system. If for some reason you cannot compile and run your code on Vocareum, at least make sure that they work properly on ieng6 server. You should be able to access ieng6 server by either going to the lab or ssh-ing to the server with your cs100xxx account. (ACMS Account lookup tool)
• If you submit your PAs beyond the allowed late days (up to 48 hours, with penalties), OR your code does not compile or run, OR if your files are misnamed, you will receive 0 credit.

Submission Scripts: When you submit your assignment, we will run a script to test parts of your assignment. These tests perform basic testing to ensure you have turned in the correct files and gotten a good part of the functionality working. However, these scripts are not exhaustive. At grading time we will run more comprehensive tests that more rigorously test your code. Just because the submission scripts pass does not mean you will get full credit on the assignment. You are encouraged to write your own tests, and in some cases, this is required as part of the assignment.

How Points are Assigned

Code that compiles and runs on your computer, but not on Vocareum, will NOT receive points.

1. Your code must compile. This is VERY IMPORTANT.
   1. If it does not compile, your code will receive no correctness points and no partial credit. Each non-compilable section receives a 0 for the coding portion.
2. Your code compiles and at runtime is partially correct.
   1. Your code will be run against a number of tests.
   2. Some will test the core functionality of your code. Some tests will test edge cases. If you got your code working to some degree, you should receive points for at least some of these tests.
3. Your code compiles and at runtime is mostly or entirely correct. (Considering normal cases and edge cases)
   1. Most or all points should be given.