MétaCan
Menu
Back to cohort
Record W2746233697 · doi:10.1177/0037549717718258

Practical aspects of the DesignDEVS simulation environment

2017· article· en· W2746233697 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

VenueSIMULATION · 2017
Typearticle
Languageen
FieldDecision Sciences
TopicSimulation Techniques and Applications
Canadian institutionsAutodesk (Canada)
Fundersnot available
KeywordsDEVSComputer scienceFormalism (music)ScalabilityEnforcementSoftware engineeringDiscrete event simulationModeling and simulationBest practiceSystems engineeringManagement scienceRisk analysis (engineering)SimulationEngineering

Abstract

fetched live from OpenAlex

DesignDEVS is a simulation development environment based on the Discrete Event System Specification (DEVS) formalism. This paper provides an in-depth overview of the software while focusing on the practical considerations influencing its design. Practitioners who stand to benefit from systems engineering will approach formalism-based simulation tools with little knowledge of the underlying theory. It is therefore important that theoretical principles, such as the separation of model and simulator, be emphasized by the user interface. Other practical aspects of DesignDEVS include the simplicity of atomic model code, a focus on coupling for collaboration purposes, the enforcement of essential modeling constraints, and a reliance on best practices in cases where strict enforcement might inconvenience users. In DesignDEVS, an issue we refer to as the Insidious Pointer Problem is aggressively tackled through run-time error handling. By contrast, the separation of output values from state transitions is left as a best practice for the sake of user convenience. The design decisions explained in this paper are relevant to developers of other formalism-based tools seeking widespread adoption of scalable modeling and simulation practices.

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.004
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.878
Threshold uncertainty score0.485

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.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.305
GPT teacher head0.503
Teacher spread0.198 · 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