MétaCan
Menu
Back to cohort
Record W3126136843

Combining Integer Programming and the Randomization Method to Schedule Employees

2009· article· en· W3126136843 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSSRN Electronic Journal · 2009
Typearticle
Languageen
FieldDecision Sciences
TopicScheduling and Timetabling Solutions
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsScheduleMathematical optimizationInteger programmingComputer scienceInteger (computer science)StaffingGenerator (circuit theory)Iterated functionConstraint (computer-aided design)Interval (graph theory)Fraction (chemistry)Service (business)Operations researchAlgorithmMathematicsPower (physics)
DOInot available

Abstract

fetched live from OpenAlex

We describe a method to find low cost employee shift schedules that guarantee that the fraction of customers who wait less than a specified time (the service level) is always at or above a specified minimum. Most previous approaches used a two-step procedure: (1) determine employee requirements, and (2) find a minimum cost schedule that provides the required number of employees in every period. Due to approximations used in the first step, the two-step approach sometimes results in infeasible or suboptimal solutions. Our method iterates between a schedule evaluator and a schedule generator. An iteration begins with the schedule evaluator using the randomization method to calculate transient service levels and identify infeasible intervals, where the service level is lower than desired. The schedule generator solves a series of integer programs to produce schedules. One constraint is added to the integer program for every infeasible interval, in an attempt to eliminate infeasibility without eliminating the optimal solution. The procedure terminates when a feasible solution is found. We present results for 18 test problems and discuss factors that make our approach more likely to outperform previous approaches. 1.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.029
metaresearch head score (Gemma)0.005
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.898
Threshold uncertainty score0.989

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0290.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0010.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.036
GPT teacher head0.379
Teacher spread0.343 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it