MétaCan
Menu
Back to cohort
Record W2117887438 · doi:10.1002/atr.5670360304

Verification process and its application to network traffic simulation models

2002· article· en· W2117887438 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

VenueJournal of Advanced Transportation · 2002
Typearticle
Languageen
FieldEngineering
TopicSimulation and Modeling Applications
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceProcess (computing)Verification and validation of computer simulation modelsSimple (philosophy)Traffic simulationSimulation modelingNetwork traffic simulationNetwork simulationSimulationSoftware engineeringDistributed computingProgramming languageEngineeringNetwork traffic control

Abstract

fetched live from OpenAlex

Abstract This paper summarizes a standardized verification process for network traffic simulation models. After the general introduction of philosophy of verification, we explain detailed processes of the verification and its application to several well‐known simulation models. “Verification” here means several examination tests of simulation models using virtual data on a simple network so as to confirm their fundamental functions. In the course of model development, the developers have to examine whether the model performance is consistent with the specifications that they intend and also with the well‐authorized traffic engineering theory. Because of several constraints in putting the model specifications into the computer programming such as discretizing of time and space and simplifying vehicle behaviors to some degree, the intended model specifications may not be fully achieved in a computer. Therefore, we strongly recommend the verification before applying the models to a real network.

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: Empirical
Teacher disagreement score0.375
Threshold uncertainty score0.430

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.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.018
GPT teacher head0.263
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