Skip to content

Conversation

@phrdang
Copy link
Member

@phrdang phrdang commented Oct 13, 2025

  • Add section called Creating Rubrics to Exam Grading article
  • Make "Assigning points" section a subsection of "Creating Rubrics"
  • Add link to Gradescope docs on rubric creation

@phrdang phrdang requested a review from pancakereport October 13, 2025 20:05
Copy link

@erickim555 erickim555 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! This philosophy echoes a lot of what I've used in my courses (and what I've observed as course staff over the years), which is a good sign too. Thanks for writing this!

- `+0.5 Partial: lst[i]`
- `+0 Incorrect`
- `+0 Blank`
- **Be aware that Gradescope autograding feature for online assignments is very particular.** For example, if you have a short answer question box, it will only mark answers correct if the string is an exact match. If there is extra whitespace or difference in uppercase vs. lowercase, it will mark the answer as wrong. Thus, you may wish to manually grade all short answer and long answer text boxes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For "Short Answer" questions, Gradescope does offer two helpful options here: "Strip leading and trailing whitespace", and "Case insensitive match". For coding questions (eg "fill in the blank" style Short Answer), I found that the first option ("Strip leading and trailing whitespace") is super helpful, and I typically enable it for my exams.

"Case insensitive match" is less useful, as Python is a case-sensitive language, so I usually leave this as disabled.

Suggestion: perhaps add a quick note in this doc about this. To enable/disable these, go to the "Settings" page of the assignment in question.

Screenshot 2025-10-13 134027

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also: in case it's helpful, I have a section on Gradescope grading in this doc: https://docs.google.com/document/d/1QUxRzhDuJr2lnv8Nl1-Ac517P_XxawQDBb2H4_jk7RM/edit?tab=t.0#heading=h.bnbz6tovqhgk

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also wrote this "Exam grading philosophy" for Data C88C SU25 that happens to echo many of your points here too (hooray!), maybe it'll be helpful as well: https://docs.google.com/document/d/1R6JCP23kRE-y-LhZWfViD9od8TZ8ghSii9lZ1GmdcBg/edit?tab=t.0#heading=h.2cs3mq5gmekm

(Not sure if it's worth linking these docs as additional resources in an "Appendix" section or something)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the tip on assignment settings! For the 2 docs you linked, I can definitely add it as an appendix-like section to this article. Is it okay to make both viewable by anyone with a Berkeley email? Also do you want to share the entirety of both docs or do you prefer to create a new separate doc with just the stuff related to exam grading, and then I can link those?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually since C88C is doing rubric writing right now I'm going to merge this PR but I can make a separate PR to include the links to the docs you wrote later!

Copy link
Collaborator

@pancakereport pancakereport left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Rebecca. Go ahead and merge when you're ready.

@phrdang phrdang merged commit 274554c into main Oct 14, 2025
5 checks passed
@phrdang phrdang deleted the rubric-writing branch October 14, 2025 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants