MétaCan
Menu
Back to cohort
Record W2885599890 · doi:10.1061/9780784481288.047

Reaction Time Optimization Based on Sensor Data-Driven Simulation for Snow Removal Projects

2018· article· en· W2885599890 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueConstruction Research Congress 2018 · 2018
Typearticle
Languageen
FieldEngineering
TopicVehicle Routing Optimization Methods
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsTruckSnowComputer scienceGlobal Positioning SystemSnow removalReal-time computingSoftwareReal-time dataEnvironmental scienceTrack (disk drive)SimulationMeteorologyAutomotive engineeringEngineering

Abstract

fetched live from OpenAlex

Reaction time of a snow removal project, which is defined as the duration between the time that snow begins accumulating at a road section and the time that snow is plowed, is a project performance indicator that can be used to evaluate the effectiveness of truck allocation strategies. While sensors, such as truck GPS (global positioning system) and weather RWIS (road weather information system), which track working hours and weather conditions, respectively, are used to collect large amounts of data, these data are not fully utilized to optimize reaction times of snow removal projects. In this research, the relationship between truck performance and weather information was analyzed. Sensor data were extracted, clustered, and refined; stochastic truck travelling speed and stochastic plowing speed were then mined and associated with the weather conditions of corresponding road sections. A data-driven, simulation-based optimization approach, which uses this mined data as input, was also developed to minimize reaction time. A practical case study of a project in Alberta, Canada, was conducted to validate and demonstrate the functionality of the proposed approach, which was simulated and optimized using the in-house simulation software, Simphony.NET. The resultant model allows project managers to predict the impact various truck allocation strategies on project time and cost to ensure that maximum project reaction time is minimized.

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.002
metaresearch head score (Gemma)0.003
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: Methods · Consensus signal: Methods
Teacher disagreement score0.175
Threshold uncertainty score0.934

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.003
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.0000.000
Research integrity0.0000.000
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.115
GPT teacher head0.392
Teacher spread0.277 · 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