Introduction
Check the Assignment 2 grade on the ZINC Online Submission System.
Your submission record will state all test case failures (if any) and their expected values.
If you are unable to see the test case failure details, please check back later, as the ZINC Web GUI Student View might be desynchronized from the server database.
We have late submission penalty for PA2. Your grade will be scaled by a factor linearly decrease from 100% to 0% for 48h. The grade after scaling is not available yet on ZINC. If you want a non-latest version to be graded, please contact TA in charge.
There are 28 test cases in total. The subscores are as follows.
- Revealed: 1-4, 0 + 0 (correctness + memory) each.
- Task 2: 5-12, 3 + 0.75 each, 24 + 6 total.
- Task 3: 13-19, 4 + 1 each, 28 + 7 total.
- Task 4: 20-26, 2 + 0.5 each, 14 + 3.5 total.
- Task 5: 27-28, 7 + 1.75 each, 14 + 3.5 total.
For grade appeals, please follow the listed procedure below.
Appeals with incomplete information and/or not following the listed procedure will not be processed:
-
Read the list of common errors and appeal cases, and follow their sub-instructions (if applicable).
-
No partial credit within a test-case. The score of a test case can only be (correctness+memory), (correctness) or 0.
-
Check the test cases for more details of what each test-case is doing.
-
Send an email to the TA in-charge, ZHANG, Jingyang, jzhangbs@connect.ust.hk,
with the subject header "COMP2012H PA2 Grade Appeal".
-
State which test-case(s) you wish to appeal. Briefly state your reasoning for why your code should have passed those test-case(s).
-
You may propose changes to your source code. Attach your code snippet with the proposed changes in your email.
However, you may not be able to reclaim all the points. Generally speaking, TA will only accept the cases that your original code is conceptually correct but failed the test case because of trivial mistakes (not related to the learning objectives of this assignment). The amount of points you can reclaim is also related to the type of your mistake.
-
The TA in-charge reserves the right to reject any and all source code changes, as the solution has already been released.
-
DO NOT attach any .exe/executable file(s) in your email.
-
Appeal deadline is 20 Nov 2020 Friday 23:59 HKT. No late appeals will be processed.
-
Finalized scores will be uploaded to Canvas after all appeals are processed.
Common Errors and Appeal Cases:
- If you don't finish the proof properly, the program will keep asking an input, which will not be provided by the predefined inputs. As a result, your program will timeout.
- If you find your program don't crash on your own machine, additionally test it on cs lab 2 machines running linux. (Because of the reasons below)
- Uninitialized variables will have garbage (random) values in C++. Sometimes it will be 0,
sometimes it will not. In that case, your program may generate different results on
different machines or different runs if your logic depend on an uninitialized value. If you have
assumed them to be 0 or something specific (e.g. a very large value), your code is faulty
and will get random results.
- If your function doesn't have a return statement for some cases, the returned value is
undefined (can be random) for those cases.
- Retrieving values from deleted/unallocated dynamic memory, or index out-of-bounds, may not always crash your
program but may give random values.
-
Compilation errors will result in 0 marks for this assignment.
This should not occur as revealed test cases were already provided to test your code on ZINC.
Exceptions will only be given for compilation errors that are the fault of the TA's testing code.
- Runtime errors and crashes due to incorrect memory access / memory allocation / memory
deallocation / missing variable initialization / missing return values / out-of-bound array access / etc,
may not occur all the time on all machines. However, even though you may not encounter the error/crash when
you test your program, if your program crashes during any of the test cases on ZINC,
the corresponding test cases will be considered as failed and will receive 0 marks.