Skip to content

Conversation

@otizonaizit
Copy link
Member

No description provided.

README.md Outdated
### Test
Type `grader <DIR>`. This will start the grader interactive CLI.

If you get a bunch of info messages and a prompt, everything is setup correctly.
Copy link
Contributor

Choose a reason for hiding this comment

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

"set up"

README.md Outdated
A *disagreement* between reviewer1 and reviewer2 is an applicant for whom the two reviewers gave diverging grades, i.e.`1` and `-1`. After grading all motivations, you may want to go through all disagreements with other reviewers to check if you simply made a typo or if you really disagree. In case of a real disagreement, a discussion among reviewers will be needed. To go through all disagreements with reviewer `reviewer2` enter grading mode like this:
```
grader> grade -d reviewer2
Copy link
Contributor

Choose a reason for hiding this comment

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

Just grade -d. This goes through all reviewers.

Maybe add an example how to deal with one reviewer.

README.md Outdated
## Use case: setting overrides
While grading you may notice that an applicant has misjudge for example their Python proficiency, by self-rating as `novice/advanced-beginner`, when instead you judge them to be rather `competent/proficient`. In this case you should set an override for this field in their application. You type `o python` while in grading mode.
Note that in grading mode you have tab-completion on applicant fields. Once the field is auto-completed, by hitting `<tab>` again you'll get a list of possible values to select from. This will set a permanent override for this applicant in the `applications.ini`
Copy link
Contributor

Choose a reason for hiding this comment

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

Missing '.'.

README.md Outdated
To make this change permanent, you need to set the formula with:
```
grader> formula -s programming*0.2 + open_source*0.2
Copy link
Contributor

Choose a reason for hiding this comment

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

This goes against the design of the rest of grader, all state changes are "permanent" in the sense that they are saved to applications.ini on exit. The user is expected to have the files under git.

@keszybz keszybz marked this pull request as ready for review April 13, 2025 15:59
@keszybz keszybz merged commit 37bbeb9 into main Apr 13, 2025
4 checks passed
@keszybz keszybz deleted the docs branch April 13, 2025 16:00
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.

3 participants