MétaCan
Menu
Back to cohort
Record W4307562660 · doi:10.1139/cjce-2022-0299

Multicontractor multiproject matching optimization for planning modular school construction programs

2022· article· en· W4307562660 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.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2022
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsGovernment of AlbertaUniversity of Alberta
Fundersnot available
KeywordsComputer scienceModular designScheduling (production processes)Multi-objective optimizationMatching (statistics)Operations researchContext (archaeology)Project managementOperations managementEngineeringSystems engineeringMachine learningMathematics

Abstract

fetched live from OpenAlex

In a practical context of construction management, a number of special contractors are selected to deliver a multiproject program in a definitive time frame. Research has yet to address how well contractors are matched to projects in scheduling and how to evaluate this criterion in scheduling optimization analysis. This research formulates a novel resource scheduling optimization problem termed multicontractor multiproject matching optimization problem (MCMPMO) based on the current practice of planning modular school development programs. The particular goal of MCMPMO is to determine which contractor is a better match for delivering which project in such a way that the program would be completed by available resources in time, resulting in the highest chances of completing the whole program to the satisfaction of all the stakeholders. A bi-objective optimization formulation for MCMPMO is proposed in the application context of planning modular school development programs. A computer program was prototyped to identify a Pareto front of the MCMPMO problem in a case study.

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.003
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.643
Threshold uncertainty score0.737

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.048
GPT teacher head0.293
Teacher spread0.245 · 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