MétaCan
Menu
Back to cohort
Record W2078438985 · doi:10.5555/1400549.1400661

Using simulation to evaluate traffic engineering management services in maritime networks

2008· article· en· W2078438985 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

VenueSpring Simulation Multiconference · 2008
Typearticle
Languageen
FieldComputer Science
TopicNetwork Traffic and Congestion Control
Canadian institutionsCarleton UniversityCommunications Research Centre Canada
Fundersnot available
KeywordsNetwork traffic simulationComputer scienceTraffic generation modelComputer networkQuality of serviceTraffic engineeringMultiprotocol Label SwitchingNetwork traffic controlTraffic shapingInternet traffic engineeringQueueing theoryTraffic optimizationFloating car dataEngineeringTransport engineeringTraffic congestion

Abstract

fetched live from OpenAlex

One of the critical problems in maritime tactical networks is how to maximize the Quality of Service (QoS) achieved by critical traffic while dealing with mobile and limited-capacity links. As part of a research effort to provide enhanced communications capabilities in a maritime tactical network, a number of traffic-engineering techniques have been investigated using the OPNET discrete-event simulation (DES) tool. In this paper, we describe the model developed to simulate the maritime environment and the impact on network traffic of three traffic-engineering based management services: first, a traffic-monitoring service matches the amount of traffic it produces with its knowledge of the current load of the network; second, a traffic-prioritisation service uses weighted fair queuing (WFQ) to prioritize critical traffic; and finally, an adaptive-routing service uses multi-path labelled switching (MPLS) to divert traffic from overloaded links. The effect of these services on network traffic has been simulated and the results are described in this paper.

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 categoriesMeta-epidemiology (narrow)
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.533
Threshold uncertainty score1.000

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.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.035
GPT teacher head0.279
Teacher spread0.244 · 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