Diferenças

Aqui você vê as diferenças entre duas revisões dessa página.

--- geopro:pedro:platforms [2007/07/21 21:32] – pedro
+++ geopro:pedro:platforms [2008/06/12 18:35] (atual) – pedro
@@ Linha 1: / Linha 1: @@
-====== MAS infrastructures======
+====== ABM Discussions and Requirements======
+====Anatomy of a Toolkit: A comprehensive compendium of various agent-based modelling toolkits, on the market today====
+|C. Nikolay, G. Madey, 2007| Proceedings of Agent2007: Complex interaction and social emergence, 87-97| [[http://leg.ufpr.br/~pedro/papers/anatomy-toolkit.pdf|pdf]]|
+\\
+**Abstract:** With so many toolkits available, the choice of which one is best suited for your project
+can be overwhelming. Moreover, different communities of users prefer different aspects
+of a toolkit. This paper is a survey of the toolkits that are available today and how they
+compare to each other from a multi-stakeholder perspective. Our goal is to provide users
+the ability to better choose a suitable toolkit based on the features abstracted from various
+documentation and the first hand experiences of a broad range of communities of users
+and compiled into an easy to use compendium. In addition, we expand the Agent Based
+Modeling body of knowledge to include information about a breadth of characteristically
+and historically diverse platforms.
+\\
 ====Evaluation of free Java-libraries for social-scientific agent based simulation====
@@ Linha 312: / Linha 330: @@
 Issues: comparing multiple model runs, loading or calibrating models from data, automatically generating large numbers of cases
 from experimental designs, collecting and statistically analyzing the results of large numbers of experiments.
@@ Linha 328: / Linha 347: @@
 communicate, interact and interoperate, while the single agent infrastructure is the generic parts of an agent that enable it to be part of a multiagent society.
-The infrastructure is clearly for modelling agents in different machines, but the semantics is the same as for simulating.
+[The infrastructure is clearly for modelling agents in different machines, but we can use the same concepts for simulating.]
 Some of the layers presented are (the complete list is [[http://leg.ufpr.br/~pedro/figures/retsina-infrastructure.jpg|here]]):
-  - ACL (Agents Communication Language)
+  - ACL (Agents Communication Language): it enables agents to be implemented in almost any language
   - Mapping names to agent locations
   - Performance measurement
+  - Locating agents by capability
+When an agent first comes up in an open environment, it may want to register itself with agent name services.
+Instead of having hardwired IP addresses for such services, the MAS infrastructure
+and the corresponding single agent infrastructure can facilitate the discovery of existing registered agents.
+__TerraME:__ Instead of having the possibility of finding agents according to the capability, the agents can be located according
+to a tag, that can store the "class" of the agent. Or perhaps the agent can registry itself using another argument representing
+this tag.
+This information is called the agent’s capability advertisement and is provided by the agent to a middle agent.
+When an agent needs another that has some required capability, it sends a middle agent a
+request specifying the desired capability. The middle agent matches requests and
+advertisements. In general, there could be a variety of middle agents that exhibit different
+matching behaviors. we have identified 28 middle agent types and have experimented with different performance
+characteristics.
+__Discussion:__ How to locate an middle agent?
+**Open systems** allow agents to enter, and exit, the system dynamically and unpredictably, while **closed systems**
+employ a  fixed set of agents that are known a priori. In closed MAS each agent knows the name, location and capability
+of the others. Thus agent interactions can be statically predefined. This makes agent design and construction
+simple, but makes the MAS brittle and not  extensible.