Diferenças

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

--- geopro:pedro:swarm [2007/07/13 15:41] – pedro
+++ geopro:pedro:swarm [2007/07/17 19:50] (atual) – pedro
@@ Linha 33: / Linha 33: @@
 \\
-//Swarm is a multi-agent software platform for the simulation of complex adaptive
+**Abstract:** Swarm is a multi-agent software platform for the simulation of complex adaptive
 systems. In the Swarm system the basic unit of simulation is the swarm, a collection of agents executing a schedule of actions.
 Swarm supports hierarchical modeling approaches whereby agents can be composed of swarms of other agents in nested
 structures. Swarm provides object oriented libraries of reusable components for building models and analyzing, displaying, and
-controlling experiments on those models.//
+controlling experiments on those models.
-//[...] collection of independent agents interacting via discrete events. [...] There are no domain
+\\
+[...] collection of independent agents interacting via discrete events. [...] There are no domain
 specific requirements such as particular spatial environments, physical phenomena, agent representations, or interaction patterns.
-Swarm simulations have been written for such diverse areas [...]//
+Swarm simulations have been written for such diverse areas [...]
-//The basic unit of a Swarm simulation is the agent. An agent is any actor in a system,
+The basic unit of a Swarm simulation is the agent. An agent is any actor in a system,
 any entity that can generate events that affect itself and other agents. Simulations consist
 of groups of many interacting agents. [...] Simulation of discrete interactions between
 agents stands in contrast to continuous system simulations, where simulated
-phenomena are quantities in a system of coupled equations.//
+phenomena are quantities in a system of coupled equations.
-//In addition to being containers for agents, swarms can themselves be agents. [...]
+In addition to being containers for agents, swarms can themselves be agents. [...]
 an agent can also itself be a swarm: a collection of objects and a schedule of actions.
 In this case, the agent's behavior is defined by the emergent phenomena of the agents inside
-its swarm. Hierarchical models can be built by nesting multiple swarms.//
+its swarm. Hierarchical models can be built by nesting multiple swarms.
 Swarm has the following components:
-  * SwarmObject: All agent classes inherit behavior from it. SwarmObject defines the basic interface for memory management as well as the support for probes.
+  * **SwarmObject**: All agent classes inherit behavior from it. SwarmObject defines the basic interface for memory management as well as the support for probes.
-  * Swarm: Model swarms and observer swarms are written by using code inherited from this base class.
+  * **Swarm**: Model swarms and observer swarms are written by using code inherited from this base class.
-  * Activity: defines the scheduling data structures and execution support.
+  * **Activity**: defines the scheduling data structures and execution support.
-  * Simtools: classes to control the execution of the entire simulation apparatus: a fully graphical and a batch mode.
+  * **Simtools**: classes to control the execution of the entire simulation apparatus: a fully graphical and a batch mode.
-//Ambiguity can occur in partial orders and time-based schedules as a result of two or
+Ambiguity can occur in partial orders and time-based schedules as a result of two or
 more actions scheduled at the same time or in the same relative order. Swarm resolves
 such ambiguity by defining a "concurrent group type," an explicit indication of how to
@@ Linha 67: / Linha 69: @@
 actually running each action concurrently, for future implementation on parallel machines.
 The explicit notation of a concurrent group type helps to expose and remove any hidden
-assumptions in the time structure of a model.//
+assumptions in the time structure of a model.
 __TerraME:__ this control of ambiguity can be very interesting
@@ Linha 169: / Linha 171: @@
   * Object2dDisplay: displays 2d arrays of objects
   * Int2dFiler: (deprecated) save the state of any Discrete2d: object (or a subclass thereof) to a specified file.
 ===== Examples available at swarm wiki=====
@@ Linha 238: / Linha 242: @@
 instead of searching the whole cellular space. We would need functions such as "add" and "remove" to the regions, and
 some support to randomness.
+The creation of a group of agents, by a Model Swarm. Note that the model creates and puts it in the world.
+  for(i = 0; i < 100; i++)
+  {
+      StupidBug* stupidBug = nil;
+      stupidBug = [StupidBug create: modelZone];
+      [stupidBug setWorld: world];
+      [stupidBug setRandPosition];
+      [bugList addLast: stupidBug];
+  }
+__TerraME__: It could be possible to create all the set of agents, and then insert the whole group in the scale. At
+this moment, each agent chooses his position/trajectories in the space.
+=====TODO=====
+Some applications using swarm:
+  * Schelhorn, T., O'Sullivan, D., Hakley, M. and Thurstain-Goodwin, M. (1999), STREETS: An Agent-Based Pedestrian Model, Centre for Advanced Spatial Analysis (University College London): Working Paper 9, London.
+  * Haklay, M., O'Sullivan, D., Thurstain-Goodwin, M. and Schelhorn, T. (2001), '"So Go Downtown": Simulating Pedestrian Movement in Town Centres', Environment and Planning B: Planning and Design, 28(3): 343-359.
+  * Batty, M., Desyllas, J. and Duxbury, E. (2003), 'Safety in Numbers? Modelling Crowds and Designing Control for the Notting Hill Carnival', Urban Studies, 40(8): 1573-1590.
+Swarm learning curve:
+  * Najlis, R., Janssen, M.A. and Parker, D.C. (2001), 'Software Tools and Communication Issues', in Parker, D.C., Berger, T. and Manson, S.M. (eds.), Meeting the Challenge of Complexity: Proceedings of a Special Workshop on Land-Use/Land-Cover Change, Irvine, California.