From 9fa366e2ad2177b774ce6baae0aa69a4227d609c Mon Sep 17 00:00:00 2001 From: Borja Sotomayor Date: Wed, 15 May 2024 18:55:52 -0500 Subject: [PATCH] Updated website --- projects/project2_rubric.html | 142 ++++++++++++++++++++++++++++++++++ 1 file changed, 142 insertions(+) diff --git a/projects/project2_rubric.html b/projects/project2_rubric.html index ae538d4..da42b85 100644 --- a/projects/project2_rubric.html +++ b/projects/project2_rubric.html @@ -117,6 +117,11 @@
  • Design
  • Style
  • Other Code Quality Issues
  • +
  • Resubmission +
  • @@ -426,6 +431,143 @@

    Other Code Quality Issues +

    Resubmission

    +

    When you receive your graded Project 2B, you can make a resubmission to address +any feedback you received in Projects 2A and/or 2B. This may increase your scores +in those projects.

    +

    Note: You cannot make a resubmission if you got S’s on both Completeness and Code Quality. If you +are in this situation and want additional feedback on your grading, please ask on Ed.

    +

    While the project is divided into two parts (2A and 2B), remember that Project 2B +builds on Project 2A, As such, you should think about your +resubmission as a final cumulative submission that addresses any remaining issues +in your Project 2A and/or 2B submissions (i.e., you should not think in terms +of making two separate resubmissions, one for 2A and another for 2B, with different +code for each submission).

    +

    Making a resubmission involves not just addressing the feedback we gave you, but +also preparing some documentation explaining the changes you made to your code. +You should consider this documentation as important as the changes you are making +to your code: resubmissions that do not include the information requested below +WILL NOT BE GRADED.

    +

    If you decide to make a resubmission, you MUST add a RESUBMISSION.md file +in the root of your repository using the following template: (the exact sections +are explained below)

    +
    Project 1 Resubmission
    +======================
    +
    +Team members:
    +- TEAM MEMBER 1 (CNETID1)
    +- TEAM MEMBER 2 (CNETID2)
    +
    +Resubmission for:
    +[ ] Project 2A
    +[ ] Project 2B
    +
    +Rubric items you have addressed
    +-------------------------------
    +<COMPLETE THIS SECTION>
    +
    +Rubric items you have NOT addressed
    +-----------------------------------
    +<COMPLETE THIS SECTION>
    +
    +Substantial new code added to your submission
    +---------------------------------------------
    +<COMPLETE THIS SECTION>
    +
    +Changes made to pass additional tests
    +-------------------------------------
    +<COMPLETE THIS SECTION>
    +
    +Other changes
    +-------------
    +<COMPLETE THIS SECTION>
    +
    +
    +

    Below you can find more details on each of the sections. If you are not providing any +information in a given section, please do not remove the section. Instead, just write +N/A below it.

    + +

    Once again, if you do not include a RESUBMISSION.md file with the above information, +your resubmission will not be graded.

    +
    +

    Submitting

    +

    For technical reasons, there will be two separate resubmission assignments on Gradescope: “Project 2A (resubmission)” +and “Project 2B (resubmission)”:

    +
      +
    • If you want to improve your score in both Project 2A and 2B, you must submit the same code +to both assignments. We will only review the code in the 2B submission, but will use the 2A +resubmission assignment to convey your updated scores for Project 2A.

    • +
    • If you only need to improve your score in one (but not both) of the assignments, submit +your code only in the corresponding resubmission assignment. e.g., if you are happy with +your Project 2A score, but want to improve your Project 2B score, then you only need to +make a submission to the “Project 2B (resubmission)” assignment on Gradescope.

    • +
    +
    +
    +

    Resubmission Grading

    +

    In general, if you are making a resubmission that only involved addressing rubric items, without adding substantial +new code to your submission, there is a very high likelihood that addressing all the rubric items will bump your Code +Quality score to an S. You may leave up to two non-major rubric items unaddressed.

    +

    On the other hand, if you are making a resubmission that involves adding substantial new code, please bear in mind +that the graders could identify issues in that new code that will impact your Code Quality score. Please +make sure to carefully review the Project 2 Rubric so you know what the graders will be looking at.

    +