Lab exam and peer eval info for students by novo52 · Pull Request #135 · cmput415/415-docs

novo52 · 2026-08-18T18:36:19Z

Adds a page explaining the lab exams to students and a page explaining the vehicle languages each exam uses.
Adds a page explaining the peer evaluations to students.

The rubric appears both as per-objective tables on the peer evaluation page and as a one-sheet reference chart, so the descriptors live in rubric_data.py and _ext/rubric.py renders them into list-tables at build time. The chart page loads rubric_sheet.css through an html-page-context handler so the full-width, small-type layout applies to that page alone, on screen as well as in print. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FxUWtBXeDptXWdHAzqdJvX

…decisions

…plement it

…e page overclaims

… answers

# Conflicts: # .gitignore # info/conf.py

…TML paths

Renders rubric_data.py as text2qti Markdown: one quiz per evaluation session, covering each evaluated member and the team. Compiles to a QTI package for import into Canvas as a graded survey. Canvas keys a replacing import on an identifier text2qti hashes from the questions alone, so the session name goes in the first question rather than only in the title. In scope: the evaluator's rubric, marks and justifications; the contribution points behind a flag. Out of scope: the pre-lab question list, and pushing marks back to Canvas.

Sir-NoChill · 2026-08-21T17:49:03Z

+"""Directives that render the peer evaluation rubric from ``rubric_data.py``.
+
+Each directive emits a reStructuredText ``list-table`` and hands it back to the
+parser, so the output matches tables written by hand elsewhere in the docs.
+
+- ``rubric-weights``   objective, scope and weight for all six objectives
+- ``rubric-levels``    what each of the four performance levels means
+- ``rubric-anchors``   the mark a given set of rubric placements is worth
+- ``rubric-objective`` one objective: its lead-in and its four descriptors
+- ``rubric-objectives`` every objective of a given scope, in order
+- ``rubric-chart``     all objectives against all levels, as one wide grid
+
+The chart page also gets its own stylesheet, attached here so that the rest of
+the site keeps the theme's usual layout.
+"""


Are there places in the doc where we rewrite these tables manually? Can we refactor the docs to have a single source of truth for these rubrics and point explicitly to the course info page?

Sir-NoChill · 2026-08-21T17:50:03Z

+def setup(app):
+    app.add_directive("rubric-weights", RubricWeights)
+    app.add_directive("rubric-levels", RubricLevels)
+    app.add_directive("rubric-anchors", RubricAnchors)
+    app.add_directive("rubric-objective", RubricObjective)
+    app.add_directive("rubric-objectives", RubricObjectives)
+    app.add_directive("rubric-chart", RubricChart)
+    app.connect("html-page-context", _attach_sheet_css)
+    return {"parallel_read_safe": True, "parallel_write_safe": True}


Do we have other places we can use these?

Sir-NoChill · 2026-08-21T17:50:38Z

-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.


We probably want to keep this little comment for future claude

Sir-NoChill · 2026-08-21T17:59:31Z

+Lab Exams
+=========
+
+Each project is followed by a lab exam: an individual, written-in-person assessment of whether you can work in a compiler codebase yourself. The exact set of exams and the weight each carries in your grade are announced with the course outline.


any way we could link to a persistent course syllabus from which we generate the version that we submit to the department? That would be ideal, then we can point to prior versions of the spec, but this is an @rcunrau call

Sir-NoChill · 2026-08-21T18:04:10Z

+* ``EXAM.md`` contains the exam tasks and their point values.
+* ``tests/`` holds the test configuration and an empty directory for the tests you write. **No reference tests are shipped** — writing the tests that expose the behaviour you are looking for is part of the exam.
+
+Read ``README.md`` first. The tasks are all stated relative to it.


Suggested change

Read ``README.md`` first. The tasks are all stated relative to it.

Read ``README.md`` first. The tasks are all stated relative to the README

Sir-NoChill · 2026-08-21T18:14:18Z

+Submitting your work
+--------------------
+
+**You are graded on what has reached GitHub by the end of the exam.** Not your working tree, not your local commits.


Suggested change

**You are graded on what has reached GitHub by the end of the exam.** Not your working tree, not your local commits.

**You are graded on what has reached GitHub by the end of the exam.**

Sir-NoChill · 2026-08-21T18:15:58Z

+
+**You are graded on what has reached GitHub by the end of the exam.** Not your working tree, not your local commits.
+
+Push early and push often. A commit sitting unpushed on a lab machine when time is called is not a submission, and "it was finished locally" is not something anyone can verify afterwards. A series of pushes across the hour is also the cheapest insurance you have against the machine failing at minute fifty.


Suggested change

Push early and push often. A commit sitting unpushed on a lab machine when time is called is not a submission, and "it was finished locally" is not something anyone can verify afterwards. A series of pushes across the hour is also the cheapest insurance you have against the machine failing at minute fifty.

Push early and push often. A commit sitting unpushed on a lab machine when time is called is not a submission. Note that **we _cannot_ verify the validity of timestamps in a local git repository as they can be spoofed**. A series of pushes across the hour is also the cheapest insurance you have against the machine failing.

Sir-NoChill · 2026-08-21T18:17:52Z

+If something goes wrong
+-----------------------
+
+Machine and network failures happen. If yours fails during the exam, tell an invigilator immediately rather than trying to recover on your own — how much time you lose depends on how quickly it is reported.


Suggested change

Machine and network failures happen. If yours fails during the exam, tell an invigilator immediately rather than trying to recover on your own — how much time you lose depends on how quickly it is reported.

Machine and network failures happen. If yours fails during the exam, tell an invigilator immediately. The teaching team can adjust your allocated time if and only if you inform them immediately.

Sir-NoChill · 2026-08-21T18:19:13Z

+* **Do your share of the project.** The exam asks for the same skills the project asks for, on a codebase you have never seen. There is no shortcut around having practised them.
+* **Practise reading unfamiliar code.** Getting oriented in a codebase you did not write — finding where a construct is handled and following it through — is the first thing you do in the exam and the thing time pressure punishes most.
+* **Practise debugging from a failing test.** Given wrong output, be able to work backwards to which part of the implementation produced it.
+* **Know the commands.** Configuring a build, rebuilding after an edit, running ``dragon-runner``, committing and pushing — you should be typing these without stopping to think. Fumbling the build costs exam time that is not coming back.


Suggested change

* **Know the commands.** Configuring a build, rebuilding after an edit, running ``dragon-runner``, committing and pushing — you should be typing these without stopping to think. Fumbling the build costs exam time that is not coming back.

* **Know the commands.** Configuring a build, rebuilding after an edit, running ``dragon-runner``, committing and pushing. You may want to explore various text search utilities like `grep` and `rg` (ripgrep), which will be useful in searching documentation.

Sir-NoChill · 2026-08-21T18:20:44Z

+
+A vehicle is never your own submission or your teammates'. The project is graded on a working compiler, and nobody can tell from a repository alone which member of a team understood which part of it. Because the vehicle is unfamiliar, you cannot fall back on code you happen to remember writing, and a team whose work was unevenly divided does not get to hide that in the exam.
+
+Being unfamiliar does not mean being undocumented. Everything you need in order to work out what a vehicle *should* do is in its repository — most importantly a spec that plays the same role as ``README.md``/``littleC_spec.md`` does for the projects: it defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.


Suggested change

Being unfamiliar does not mean being undocumented. Everything you need in order to work out what a vehicle *should* do is in its repository — most importantly a spec that plays the same role as ``README.md``/``littleC_spec.md`` does for the projects: it defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.

Everything you need in order to work out what a vehicle *should* do is in its repository — most importantly a spec,``README.md`` and ``littleC_spec.md`` for respective vehicles, defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.

novo52 and others added 11 commits August 17, 2026 13:50

Add the Gazprea peer evaluation page and rubric chart

a938087

Add the lab exam page

29fdaf3

Ground the lab exam page in the confirmed room, schedule, and access …

5e9f125

…decisions

Describe the exam session as the monitor and Classroom 50 actually im…

b3d7c26

…plement it

State the closed-internet rule and the git exception it needs

e8b4592

State the exam as open-computer and closed-internet, and trim what th…

487c49c

…e page overclaims

Describe grading by hidden test suite, mutant comparison, and written…

f63a484

… answers

Add an exam vehicles page explaining Sweep and the three littleCs

d25e057

Removed mistakenly committed files

b943852

Fixed wording

2d4e07d

novo52 requested a review from rcunrau August 18, 2026 18:41

novo52 changed the title ~~Lab exam info~~ Lab exam and peer eval info for students Aug 18, 2026

novo52 added 5 commits August 18, 2026 16:47

Merge remote-tracking branch 'origin/master' into info/lab-exam

03651f5

# Conflicts: # .gitignore # info/conf.py

Resolve the lab exam cross-references through Sphinx instead of raw H…

d9a2c70

…TML paths

Three peer evaluations, with pairings and rooms published on Canvas

7e8430b

Emphasise live code navigation in the peer evaluation Q&A

e6f21be

Sir-NoChill requested changes Aug 21, 2026

View reviewed changes

Navigation Menu

Uh oh!

Lab exam and peer eval info for students - #135

Lab exam and peer eval info for students#135
novo52 wants to merge 16 commits into
masterfrom
info/lab-exam

novo52 commented Aug 18, 2026 •

edited

Loading

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Sir-NoChill Aug 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	Read ``README.md`` first. The tasks are all stated relative to it.
	Read ``README.md`` first. The tasks are all stated relative to the README

	You are graded on what has reached GitHub by the end of the exam. Not your working tree, not your local commits.
	You are graded on what has reached GitHub by the end of the exam.


		You are graded on what has reached GitHub by the end of the exam. Not your working tree, not your local commits.

		Push early and push often. A commit sitting unpushed on a lab machine when time is called is not a submission, and "it was finished locally" is not something anyone can verify afterwards. A series of pushes across the hour is also the cheapest insurance you have against the machine failing at minute fifty.

	Machine and network failures happen. If yours fails during the exam, tell an invigilator immediately rather than trying to recover on your own — how much time you lose depends on how quickly it is reported.
	Machine and network failures happen. If yours fails during the exam, tell an invigilator immediately. The teaching team can adjust your allocated time if and only if you inform them immediately.

	* Know the commands. Configuring a build, rebuilding after an edit, running ``dragon-runner``, committing and pushing — you should be typing these without stopping to think. Fumbling the build costs exam time that is not coming back.
	* Know the commands. Configuring a build, rebuilding after an edit, running ``dragon-runner``, committing and pushing. You may want to explore various text search utilities like `grep` and `rg` (ripgrep), which will be useful in searching documentation.


		A vehicle is never your own submission or your teammates'. The project is graded on a working compiler, and nobody can tell from a repository alone which member of a team understood which part of it. Because the vehicle is unfamiliar, you cannot fall back on code you happen to remember writing, and a team whose work was unevenly divided does not get to hide that in the exam.

		Being unfamiliar does not mean being undocumented. Everything you need in order to work out what a vehicle should do is in its repository — most importantly a spec that plays the same role as ``README.md``/``littleC_spec.md`` does for the projects: it defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.

	Being unfamiliar does not mean being undocumented. Everything you need in order to work out what a vehicle should do is in its repository — most importantly a spec that plays the same role as ``README.md``/``littleC_spec.md`` does for the projects: it defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.
	Everything you need in order to work out what a vehicle should do is in its repository — most importantly a spec,``README.md`` and ``littleC_spec.md`` for respective vehicles, defines correct behaviour, and it is what you check the implementation against. Read it first; every exam task is stated relative to it.

Uh oh!

Conversation

novo52 commented Aug 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

novo52 commented Aug 18, 2026 •

edited

Loading