FA-67765 / Elevator dispatch scheduling / Member archive

Single car SCAN service simulation: alight before boarding · case 05

Waiting passengers are left behind at a floor where riders are getting out.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

All passengers [id, from, to] wait at time 0. The car starts at start heading up. At each floor it first lets riders alight, then boards waiting passengers (in id order) whose travel direction equals the car direction while load < cap; any alighting or boarding costs one stop_s. If no rider destination or waiting origin lies strictly ahead it reverses in place (and may board again); otherwise it moves one floor (floor_s). Return {id: [board time, alight time]} for delivered passengers.

Why this case matters

Lift group controllers make these decisions many times per minute; a wrong answer strands passengers, wastes trips or overrides a safety rule.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: full car at a floor where a rider alights	`{"a": [0, 11], "b": [16, 27]}`	`{"a": [0, 11], "b": [11, 22]}`	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.