MétaCan
Menu
Back to cohort
Record W2154204898 · doi:10.5430/air.v2n3p59

A comparison of organization-centered and agent-centered multi-agent systems

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

VenueArtificial Intelligence Research · 2013
Typearticle
Languageen
FieldComputer Science
TopicMulti-Agent Systems and Negotiation
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceJavaMulti-agent systemFocus (optics)Middleware (distributed applications)Character (mathematics)Software engineeringArtificial intelligenceHuman–computer interactionProgramming languageDistributed computing

Abstract

fetched live from OpenAlex

Whereas most classical multi-agent systems have the agent in center, there has recently been a development towards focusing more on the organization of the system, thereby allowing the designer to focus on what the system goals are, without considering how the goals should be fulfilled. We have developed and evaluated two teams of agents for a variant of the well-known Bomberman computer game. One team is based on the basic Jason system, which is an implementation in Java of an extension of the logic-based agent-oriented programming language AgentSpeak. The other team is based on the organizational model Moise+, which is combined with Jason in the middleware called J-Moise+. We have investigated whether taking the organization-oriented approach had any clear advantages to the classical way of implementing multi-agent systems. Although not decisive the investigation did indicate that the agent-oriented approach has a number of advantages when it comes to game-like scenarios with just a few different character types.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.874
Threshold uncertainty score0.919

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.340
GPT teacher head0.438
Teacher spread0.097 · 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