MétaCan
Menu
Back to cohort
Record W2119566353 · doi:10.1504/ijes.2015.069997

A flexible control study of variable speed limit in connected vehicle systems

2015· article· en· W2119566353 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

VenueInternational Journal of Embedded Systems · 2015
Typearticle
Languageen
FieldEngineering
TopicTraffic control and management
Canadian institutionsUniversity of Alberta
FundersNational Science Foundation
KeywordsSpeed limitFlexibility (engineering)Software deploymentLimit (mathematics)Computer scienceVariable (mathematics)Automotive engineeringIntelligent transportation systemTraffic congestionElectronic speed controlRoad traffic controlControl (management)Real-time computingSimulationTransport engineeringEngineeringMathematicsElectrical engineeringStatisticsArtificial intelligence

Abstract

fetched live from OpenAlex

Traffic congestion has already been a distinctly serious problem in both developed and developing countries. Among the proposed methods to solve the traffic congestion problem, variable speed limit (VSL) is considered as one of the most promising methods. But to the traditional VSL, the speed limit sign and the control distance is fixed, which makes VSL lack deployment and control flexibility. Whereas, in connected vehicle (CV), which is a crossing field of intelligent transportation systems (ITS) and internet of things (IoT), control and deployment flexibility can both be achieved. Furthermore, a big data environment is formed in CV to solve the traffic problems. In this paper, connect vehicle-based variable speed limit (CV-VSL) is proposed, and a simulation platform SimIVC is used to study the influence of control distance. The results show that the improvement of traffic performance increases 0.72% when the control distance is 270 metres than that of 250 metres, which means that the traffic performance can be further improved by CV-VSL.

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.001
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: Empirical
Teacher disagreement score0.048
Threshold uncertainty score0.498

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
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.024
GPT teacher head0.251
Teacher spread0.227 · 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