Bibliographic record
Abstract
Distributed simulation is defined as real-time functional or platform-level war-gaming on multiple host computers. This simulation is composed of self-sufficient monolithic applications designed to communicate only across a standard interface such as High Level Architecture (HLA), Testing and Training Enabling Architecture (TENA), the Distributed Interactive Simulation (DIS) protocol or Link 16. The applications may represent up to Command, Control, Communication, Computer, Intelligence, Surveillance, and Reconnaissance (C4ISR) simulation applications. The Discrete-EVent System Specifications (DEVS) formalism has been extensively to study discrete event systems. Cellular-Discrete EVent System Specification (Cell-DEVS) is a DEVS-based formalism that combines cellular automata and DEVS allowing implementation of cellular models with timing delays. CD++ is a modeling and simulation toolkit used to build DEVS and Cell-DEVS models with a RESTful web-based interface in a distributed systems context. The distributed simulations and distributed systems are incompatible to directly interface which each other without refactoring either side. A thin client technique has been proposed to allow interoperability between the two M&S frameworks. This work studies HyperText Markup Language -version 5 (HTML5), JavaScript, multithreading, WebSockets, the presentation and extraction of Cell-DEVS data, the interfaces of distributed simulations and the WebLVC protocol in order to expose the Cell-DEVS data housed on the RESTful Interoperable Simulation Environment (RISE) into a distributed simulation. As an example, it presents the design and implementation of a web-based thin client as a mash-up of services between the RISE service and the distributed simulation. The proposed web-based client technique takes advantage of web service technologies in order to execute complex Cell-DEVS models within a distributed environment. In addition, the technique exposes distributed simulations to other simulation types beyond the Cell-DEVS discrete event models. The web-based client technique depends on the network connectivity but relies on the HTML5 WebSocket for providing full-duplex communications over a single Transport Control Protocol (TCP) connection to the distributed simulation.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
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".