User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lab_grading [2019/09/10 15:20] jgoeders [Grade Breakdown] |
lab_grading [2019/09/10 15:24] (current) jgoeders [Coding Standard Grading] |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| The TAs will apply the following grading rubric when evaluating your SystemVerilog source code. The goal is to get you in the habit of writing, readable, reusable, high-quality code. As such the TAs will be quite strict when grading your code. | The TAs will apply the following grading rubric when evaluating your SystemVerilog source code. The goal is to get you in the habit of writing, readable, reusable, high-quality code. As such the TAs will be quite strict when grading your code. | ||
| - | * You start out with 100% credit (10 points) for the code-quality part of your grade. | + | * You start out with 100% credit (10 points) for the code-quality part of your grade. If the lab consists of submitting multiple SystemVerilog modules, they will be worth a combined 10 points (as indicated in LearningSuite). |
| * Each coding infraction reduces the code-quality credit by 1 point. Making the "same mistake multiple times" will result in losing multiple points. (eg. if your ''always_comb'' is missing default values for multiple signals assigned in the block, you will be deducted 1 point for each signal that does not have a default value). | * Each coding infraction reduces the code-quality credit by 1 point. Making the "same mistake multiple times" will result in losing multiple points. (eg. if your ''always_comb'' is missing default values for multiple signals assigned in the block, you will be deducted 1 point for each signal that does not have a default value). | ||
| - | * Your first 3 infractions are freebies. (ie. 5 infractions will results in a grade of 8/10) | + | |
