FA-94374 / Exam timetabling constraints / Member archive

Same-period clash counted as period spread · case 04

Clashing exams add a spread penalty on top of the clash.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Periods are numbered consecutively with spd slots per day (day = p // spd). For each student and each pair of their distinct exams: same day and adjacent periods counts two-in-a-row; same day and further apart counts two-in-a-day (same-period clashes count neither); periods 1..spread apart count period spread regardless of day. w = [row weight, day weight, spread]. Return [row, day, spread count, weighted total].

Why this case matters

Proximity soft constraints are what exam timetabling quality is judged on; each counter has its own boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression: clash not two in day 1	`[0, 0, 2, 2]`	`[0, 0, 1, 1]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.