MétaCan
Menu
Back to cohort
Record W2793646586 · doi:10.5539/emr.v7n1p17

Optimization of the Merging Area after Toll

2018· article· en· W2793646586 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueEngineering Management Research · 2018
Typearticle
Languageen
FieldEngineering
TopicTraffic control and management
Canadian institutionsnot available
Fundersnot available
KeywordsTollSensitivity (control systems)Bridge (graph theory)Scope (computer science)Mathematical optimizationNonlinear programmingThroughputNonlinear systemComputer scienceFocus (optics)Integer (computer science)Operations researchSimulationMathematicsEngineering

Abstract

fetched live from OpenAlex

In this paper, we focus on the planning of the merging area after toll and have established an optimization model by means of nonlinear integer programming model. With the consideration of factors such as safety, cost, and throughput, we select indexes including traffic flow, vehicle speed, lane width and the number of lanes to calculate and determine the tollbooth and merging area, and depending on the situation, we built modification model and reconstruction model. Then, we select Delaware Memorial Bridge toll plaza as an example to evaluate the effectiveness of our solutions based on the optimal model. We apply the method of computer simulation to solve the model, and we find that some parameters with the fixed value such as forced exchange rate, average expected speed and gradient rate may affect the applicability of the model. Then, we carry out the sensitivity analysis with the three parameters to determine the scope of application of the model. Finally, we further discuss development direction of this model.

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.000
metaresearch head score (Gemma)0.000
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.813
Threshold uncertainty score0.351

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.013
GPT teacher head0.234
Teacher spread0.221 · 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