MétaCan
Menu
Back to cohort

Tightly-Packed Repetitive Schedules: A Tetris Challenge

2022· article· en· W4210299395 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

VenueIOP Conference Series Materials Science and Engineering · 2022
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsComputer scienceScheduling (production processes)ScheduleVisualizationJob shop schedulingDistributed computingOperations researchIndustrial engineeringArtificial intelligenceOperations managementEngineering

Abstract

fetched live from OpenAlex

Abstract A large portion of new and rehabilitation projects for the civil infrastructure involves repetitive tasks that mandate high degree of synchronization among the resources to meet project constraints. Despite their large need for support, few tools exist commercially. This is due, in part, to the computational and visualization challenges of existing repetitive scheduling techniques, which complicate the process and make it less understood, particularly when the repetitive units are not identical and when resources are limited. This presentation introduces enhancements by dealing with repetitive scheduling as a game of Tetris, where tasks can change geometry to fit tightly together to save project duration. This is demonstrated through novel mathematical formulations, as well as a new heuristic scheduling algorithm (First-Come-First-Serve). It will be shown that the proposed geometrical adjustments are more advantageous in improving repetitive schedules than using expensive accelerations, and the new visuals make the schedule more legible. This research is a step towards making repetitive scheduling a mainstream tool, to benefit the construction industry.

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.006
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.077
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.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.061
GPT teacher head0.298
Teacher spread0.237 · 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