AA4MM : Released Code

The current release of AA4MM is called Darjeeling (aa4mm_V0.1). It is intended to build a proof of concept (I.e. tests the Agents and Artefacts concepts developed in my PhD thesis). It relies upon the Java Messaging Service (JMS) in order to deal with shared memory issues (I.e. post, read, filter data...).

Install

In order to test the code and the examples, you need to install a JMS server (there could be one or several). A simple way to do that is to install the JDK and to run the glassfish server provided by sun. Then a few configuration is needed (see JMS Doc).
Note that the aa4mm basic package needs several libraries in oreder to work with jms. See the class paths below:

Class-path with J2EE SDK 5

Class-path with J2EE SDK 6

In order to make JMS bindings work:
  1. path_to_J2EE_6_SDK/mq/lib/jms.jar
  2. path_to_J2EE_6_SDK/glassfish/lib/appserv-rt.jar

Download

The basic API


aa4mm(darjeeling) v0.1 (Synchronization ok, local causality constraint may not be respected when using discrete events simulators)
aa4mm(darjeeling) v0.2 (Synchronization and local causality constraint ok whatever the simulators (discrete event + step-by-step))
Differences between v0.1 and v0.2: coordination model changes.

The examples (v0.1)

In order to run the example, you need the Netlogo API librairies provided by Netlogo (see Netlogo webpage).
  1. Example #1: A single random walk model
  2. Example #2: Two interacting random walk models
  3. Example #3: The sheepfold simulation: sheep vs grass

The examples (v0.2)

  1. Example #1: A single random walk model
  2. Example #2: Two interacting random walk models
  3. Example #3: The sheepfold simulation: sheep vs grass
  4. Example #4: The sheepfold simulation: wolves vs sheep vs grass

Doc (API)

Java doc (v0.1)