FA-94625 / Exam timetabling constraints / Member archive

Consecutive sittings taken in registration order · case 05

Unordered registrations compare non-consecutive exams.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

sits [student, exam, start, end], campus exam -> campus, travel "X|Y" -> minutes stored in either order. For each student's consecutive sittings by start, the needed gap is the travel time between different campuses (0 for the same campus); if the gap from previous end to next start is smaller, report [student, previous exam, next exam, shortfall].

Why this case matters

Multi-campus exam timetables must leave travel time between a student's consecutive sittings.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: sitting order 1	`[["s2", "MATH101", "CHEM120", 270], ["s2", "BIO130", "HIST140", 30], ["s5", "MATH101", "ECON150", 181]]`	`[["s2", "BIO130", "HIST140", 30]]`	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.