📄️ Overview
Programming assignments are the core of Pawtograder. Each assignment consists of a "handout" repository, and optionally, a "grader" repository. When an assignment is released, Pawtograder automatically creates a new private repository for each student based on that handout. Pawtograder automatically manages permissions for all of these repositories, allowing staff to view all of a course's repositories, and ensuring students can only view their own repositories.
📄️ Creating and Managing Rubrics
Rubrics: Instructor Guide
📄️ Testing an Assignment
Although Pawtograder does not provide a feature to "impersonate" a student, it does provide a robust feature to allow staff to test an assignment. This feature provisions staff with a repository just like any other student would have, but it does not show up in the list of student submissions. You can even mark up the submission with rubric checks to perform a complete end-to-end test of the assignment.
📄️ Handgrading
Instructors can define multiple handgrading rubrics for each assignment, although the most typical mechanism is to simply use the "Grading Rubric" (which, combined with the autograder score, is used to compute the score for each submission).
📄️ Assigning Grading Tasks
Pawtograder has a robust feature to allow instructors to assign grading tasks to staff. When a grading task is assigned, the instructor can set a due date for that task, and re-assign the task to a different grader if needed. Pawtograder will also automatically allow any other grader to complete the task if the original grader is unable to complete it (without needing to re-assign the task).
📄️ Configuring Autograders
To be written.