-
Notifications
You must be signed in to change notification settings - Fork 31
Grading Rubric
Chan Ju Ping edited this page Jun 20, 2025
·
6 revisions
Here is our rubric for scoring Python 2025 projects!
Do note that for every day late in submission of projects, 1 point will be deducted from the team's total score. The final submission date without penalties is on 20250620 at 23:59 hrs.
| Poor (1) | Average (2) | Good (3) | |
|---|---|---|---|
| Hosting | Program not hosted anywhere. | Program not hosted on an accessible git server. Git commands unavailable for downloading project. | Project properly hosted on a publicly accessible git server. git clone <url> function pulls in a complete project. |
| README.md | No README.md found, README.md is unmodified from upstream, or contents of README.md file are irrelevant. | A rudimentary README.md file is included but fails to adequately cover how ComfyUI is modified and used. | A README.md file is included with the project, fully describing how ComfyUI was used and modified for generating the images and video. |
| Wiki | Wiki documentation not done. | Wiki documentation is rudimentary, and does not provide more guidance than that already found in the README.md file. | Wiki properly used to document additional background and usage of project with examples, notes on limitations, and other pieces of information. |
| Functionality | ComfyUI fork doesn't work. | ComfyUI fork works but is unmodified. | ComfyUI was modified and still works. |
| In-line Comments | None or irrelevant comments. | Inconsistent comments, but what is there is useful. | Clear comments that explain what the learner was trying to achieve for each modification. |
| Improvements | No improvements based upon the upstream project was made. | At least one area of improvement was made to the project based on the upstream project it is based on. | Project was improved upon above and beyond what was expected of the learner. |
| Elements | Included none of the following elements:
|
Included some of the following elements:
|
Included most of the following elements:
|
| Presentation | No clear explanation provided. | Presentation is mostly understandable, but missing crucial details that require further clarification. | Provides a clear and thorough explanation of the project such that no additional questions are required. |
| Video Score | Video is irrelevant due to not using ComfyUI or plagiarized without attribution from other sources. | 10 second or shorter video that uses images generated from ComfyUI but is lacking sound, storytelling, or other means that makes a compelling video beyond a tech showcase. | 10 second or less video using ComfyUI generated images that is coherent and entertaining. |
| ComfyUI Workflow | Unchanged default workflow. | Modifications to default workflow. | Exceptional customization to default ComfyUI workflow for the purposes of the participant's project. |
Additional scoring rubric for group efforts:
| Poor (1) | Average (2) | Good (3) | |
|---|---|---|---|
| Bug Reports | No bug reporting ever used to address issues. | Bug reports filed, but lack actionable details. | Bug reports used to highlight important issues with proper debugging information for developers to attempt to duplicate. |
| Pull Requests | No usage of pull request feature. | Usage of pull request feature not done appropriately to address issues. | Proper use of pull request feature that allows improvements to the project efficiently. |
| Merge | No merging of branches or pull requests. | Improper merging of branches or pull requests resulting in faulty code. | Proper usage of merging of branches and pull requests that improves the main project branch without causing unexpected faults. |