FA-95140 / Warehouse slotting and bin packing / Member archive

Re-slot plan: two SKUs sent to one slot · case 05

Two accepted moves target the same destination slot.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

cands [[sku, from_slot, to_slot, weekly_picks, travel_from, travel_to]]. Weekly benefit = picks*(travel_from - travel_to); keep candidates with benefit >= move_cost; rank by benefit desc, sku, from, to. Greedily accept up to max_moves: each SKU moves once, each target is used once, and a target that is the from_slot of any candidate is occupied unless that slot was already vacated by an accepted move. Return [[sku, to_slot, benefit]].

Why this case matters

Periodic re-slotting moves SKUs whose velocity changed toward better locations.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
shared target	`[["A", "S9", 400], ["B", "S9", 300]]`	`[["A", "S9", 400]]`	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.