MétaCan
Menu
Back to cohort
Record W4237670884 · doi:10.1002/spe.809

Developing a software toolkit for urban traffic modeling

2007· article· en· W4237670884 on OpenAlexaff
Gabriel Wainer

Bibliographic record

VenueSoftware Practice and Experience · 2007
Typearticle
Languageen
FieldEngineering
TopicTraffic control and management
Canadian institutionsCarleton University
Fundersnot available
KeywordsComputer scienceParsingTruckGraphicsSoftwareFocus (optics)DEVSSet (abstract data type)Traffic flow (computer networking)Section (typography)Software engineeringSimulationProgramming languageComputer graphics (images)Modeling and simulationOperating systemEngineering

Abstract

fetched live from OpenAlex

Abstract ATLAS is a modeling language that permits a static view of a city section to be defined for simulating traffic in closed areas. We propose a methodology that is focused on the user while being able to improve the software development activities. The models are formally specified, avoiding a high number of errors in the application, thus reducing the problem solving time. Streets are characterized by their traffic direction, number of lanes, etc. Once the urban section is outlined, the traffic flow is automatically set up. Specialized behavior is included to model traffic lights, trucks, traffic signs, railways, etc. The basic idea is to provide a mapping into DEVS and Cell‐DEVS models that can be easily executed with a simulation tool. As the modelers can focus on the problem to solve, development times for the simulators can be dramatically reduced. A front‐end system allows the user to draw city sections (and then parse the drawing to create a valid ATLAS file), and an output subsystem permitting cars to be shown with realistic 3D graphics. Copyright © 2007 John Wiley & Sons, Ltd.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Software · Consensus signal: none
Teacher disagreement score0.010
Threshold uncertainty score0.034

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.006
Meta-epidemiology (narrow)0.0010.002
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0020.001
Science and technology studies0.0010.001
Scholarly communication0.0020.002
Open science0.0030.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0100.005

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.021
GPT teacher head0.270
Teacher spread0.249 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreSoftware

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations10
Published2007
Admission routes1
Has abstractyes

Explore more

Same venueSoftware Practice and ExperienceSame topicTraffic control and managementFrench-language works237,207