MétaCan
Menu
Back to cohort
Record W145585440 · doi:10.5555/2484920.2485185

Model based approach to detect emergent behavior in multi-agent systems

2013· article· en· W145585440 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

VenueAdaptive Agents and Multi-Agents Systems · 2013
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsCarleton UniversityUniversity of Calgary
Fundersnot available
KeywordsAgent-oriented software engineeringComputer scienceUnified Modeling LanguageSequence diagramSoftware engineeringSoftware deploymentMulti-agent systemSoftwareSoftware developmentSystems engineeringArtificial intelligenceEngineering

Abstract

fetched live from OpenAlex

Multi-agent systems (MAS) are efficient solutions for commercial applications such as robotics, business commerce applications, information retrieval and search engines. In MAS, agents are usually designed with distribution of functionality and control. Lack of central control implies that the quality of service of MAS may be degraded because of possible unwanted behavior at runtime, commonly known as emergent behavior. Detecting and removing emergent behavior during the design phase of MAS will lead to huge savings in deployment costs of such systems. Effective and efficient design validation of MAS requires the development of systematic and automated methodologies to review MAS design documents. Although the increasing demand for MAS in the software industry has led to the development of several Agent Oriented Software Engineering (AOSE) methodologies, the AOSE methodologies usually do not fully cover monitoring and testing. In this paper, a technique to help MAS developers verify, test and monitor MAS design is introduced. This method uses MAS analysis and design artifacts created by the MaSE AOSE methodology. In this technique, design artifacts of MaSE are converted to scenario-based specification, which is very similar to UML's sequence diagrams. Then the specifications are used to analyze the system for validating the design of MAS and ensuring the lack of emergent behavior.

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.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: Methods · Consensus signal: none
Teacher disagreement score0.548
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.001
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.182
GPT teacher head0.329
Teacher spread0.146 · 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