Docs update.
diff --git a/documentation/amp.html b/documentation/amp.html
index 4faed8f..0b23189 100644
--- a/documentation/amp.html
+++ b/documentation/amp.html
@@ -22,77 +22,96 @@
</p>
<dl>
<dt>
-<span class="chapter"><a href="#Introduction">1. Introduction</a></span>
+<span class="chapter"><a href="#Modeler.27s_Guide">1. Modeler's Guide</a></span>
</dt>
<dd>
<dl>
<dt>
-<span class="section"><a href="#Agent-Based_Modeling">Agent-Based Modeling</a></span>
+<span class="section"><a href="#Introduction">Introduction</a></span>
</dt>
<dt>
-<span class="section"><a href="#Agent_Modeling_Framework">Agent Modeling Framework</a></span>
+<span class="section"><a href="#Structure">Structure</a></span>
</dt>
<dt>
-<span class="section"><a href="#Other_Uses">Other Uses</a></span>
+<span class="section"><a href="#Actions_2">Actions</a></span>
+</dt>
+<dt>
+<span class="section"><a href="#Functions">Functions</a></span>
</dt>
</dl>
</dd>
<dt>
-<span class="chapter"><a href="#Structure">2. Structure</a></span>
+<span class="chapter"><a href="#Creating_Agent_Models">2. Creating Agent Models</a></span>
</dt>
<dd>
<dl>
<dt>
-<span class="section"><a href="#Design">Design</a></span>
-</dt>
-<dt>
-<span class="section"><a href="#Details">Details</a></span>
-</dt>
-<dt>
-<span class="section"><a href="#Reference">Reference</a></span>
+<span class="section"><a href="#Getting_Started">Getting Started</a></span>
</dt>
</dl>
</dd>
<dt>
-<span class="chapter"><a href="#Actions">3. Actions</a></span>
+<span class="chapter"><a href="#Exploring_Agent_Models">3. Exploring Agent Models</a></span>
+</dt>
+<dt>
+<span class="chapter"><a href="#Programer.27s_Guide">4. Programer's Guide</a></span>
</dt>
<dd>
<dl>
<dt>
-<span class="section"><a href="#Background">Background</a></span>
+<span class="section"><a href="#Overview">Overview</a></span>
</dt>
<dt>
-<span class="section"><a href="#Design_2">Design</a></span>
+<span class="section"><a href="#Getting_Started_2">Getting Started</a></span>
</dt>
<dt>
-<span class="section"><a href="#Details_3">Details</a></span>
+<span class="section"><a href="#Installation">Installation</a></span>
</dt>
<dt>
-<span class="section"><a href="#Example">Example</a></span>
+<span class="section"><a href="#Exploring_Example_ABM_Models">Exploring Example ABM Models</a></span>
</dt>
<dt>
-<span class="section"><a href="#Reference_2">Reference</a></span>
+<span class="section"><a href="#Developing_Models">Developing Models</a></span>
</dt>
</dl>
</dd>
<dt>
-<span class="chapter"><a href="#Functions">4. Functions</a></span>
+<span class="chapter"><a href="#Reference_4">5. Reference</a></span>
</dt>
<dd>
<dl>
<dt>
-<span class="section"><a href="#Reference_3">Reference</a></span>
+<span class="section"><a href="#Converting_Existing_Ascape_models">Converting Existing Ascape models</a></span>
+</dt>
+</dl>
+</dd>
+<dt>
+<span class="chapter"><a href="#More_Information">6. More Information</a></span>
+</dt>
+<dd>
+<dl>
+<dt>
+<span class="section"><a href="#Obtaining_Example_Models">Obtaining Example Models</a></span>
</dt>
</dl>
</dd>
</dl>
</div>
-<div class="chapter" title="Chapter 1. Introduction">
+<div class="chapter" title="Chapter 1. Modeler's Guide">
<div class="titlepage">
<div>
<div>
<h2 class="title">
-<a name="Introduction"></a>Chapter 1. Introduction</h2>
+<a name="Modeler.27s_Guide"></a>Chapter 1. Modeler's Guide</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Introduction">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Introduction"></a>Introduction</h2>
</div>
</div>
</div>
@@ -102,8 +121,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Agent-Based_Modeling"></a>Agent-Based Modeling</h2>
+<h3 class="title">
+<a name="Agent-Based_Modeling"></a>Agent-Based Modeling</h3>
</div>
</div>
</div>
@@ -155,34 +174,54 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Agent_Modeling_Framework"></a>Agent Modeling Framework</h2>
+<h3 class="title">
+<a name="Agent_Modeling_Framework"></a>Agent Modeling Framework</h3>
</div>
</div>
</div>
<p>The Eclipse Platform provides many unique features that make it ideal for an ABM platform. AMF provides easy to use and powerful tools and techniques for designing Agent-Based Models, including a common representation, editors, generators and development environment.</p>
-<p>The Agent Modeling Framework (AMF) provides high level representations for common ABM constructs, and introduces novel ways of representing agents and their behaviors. As detailed in other documentation sections, the Agent Modeling Framework and related tools have been designed to allow researchers to explore complex models in an intuitive way. One of our major design goals has been to create tools that non-programmers can use to create sophisticated models. It has been our experience that using Model-Driven Software Development (MDSD) techniques increase productivity for all developers regardless of skill level. For those familiar with Model-Driven Development tools, AMF is analogous to EMF but is targeted toward the design and execution of models composed of agents. The AMF meta-model (currently "MetaABM", but in the process of evolving to a new compatible "Acore" specification) is defined in Ecore but provides a more direct and high-level ABM representation of agents, including spatial, behavioral and functional features sufficient to generate complete executable models for the target platforms.</p>
+<p>The Agent Modeling Framework (AMF) provides high level representations for common ABM constructs, and introduces novel ways of representing agents and their behaviors. As detailed in other documentation sections, the Agent Modeling Framework and related tools have been designed to allow researchers to explore complex models in an intuitive way. One of our major design goals has been to create tools that non-programmers can use to create sophisticated models. It has been our experience that using Model-Driven Software Development (MDSD) techniques increase productivity for all developers regardless of skill level. </p>
+<p>The foundation of the Agent Modeling Framework is "Acore". The current version uses an interim version of Acore called "MetaABM". We refer to the AMF models as "meta-models" because they are used to define
+ <span class="italic">how</span> Agent-Based Models are themselves modeled. For those familiar with Eclipse Model-Driven Development tools, AMF is analogous to EMF but is targeted toward the design and execution of models composed of agents. Acore and MetaABM are defined in Ecore but provide a more direct and high-level ABM representation of agents, including spatial, behavioral and functional features sufficient to generate complete executable models for the target platforms. AMF is fully integrated with the Eclipse IDE platform, but Acore models themselves need have no dependencies on any particular technology beyond XML/XSD.
+ </p>
<p>Models designed in AMF are transparently converted to Java code for leading Agent-Based Modeling tools, such as the Escape tools which are included in AMP and allow direct execution of models within the AMP environment, and Repast Simphony, another popular Java based ABM tool. These tools create Java code that can then be compiled, executed and event modified in these environments just as with any other Java program. AMF's generative capability is designed to be pluggable and modular so that other developers can create AMF generators for their own tools. In fact, targets can be designed that have no inherent dependencies on Eclipse or even on a traditional platform.</p>
+<p>The Acore / MetaABM meta-model is made up of three main packages. This is all based on MetaABM, and while names and important details will change for Acore, the core design should be quite similar.</p>
</div>
<div class="section" title="Other Uses">
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Other_Uses"></a>Other Uses</h2>
+<h3 class="title">
+<a name="Other_Uses"></a>Other Uses</h3>
</div>
</div>
</div>
<p>Many kinds of objects share characteristics of ABM agents -- after all, software agents are used in many other contexts. The Agent Modeling Framework meta-modeling support is potentially suitable (or extendible) for a number of approaches outside of ABM; for example business rules, object interactions, systems dynamics models and traditional discrete event models. Similarly, AMP execution and graphic support can be used for modeling natural systems but could also be used to manage other software agents -- for example independent reasoning tasks or dynamic visualization support.</p>
<p>We hope you enjoy using the tool, and we look forward to your comments and feedback and most of all participation!</p>
</div>
-</div>
-<div class="chapter" title="Chapter 2. Structure">
+<div class="section" title="Credits">
<div class="titlepage">
<div>
<div>
-<h2 class="title">
-<a name="Structure"></a>Chapter 2. Structure</h2>
+<h3 class="title">
+<a name="Credits"></a>Credits</h3>
+</div>
+</div>
+</div>
+<p>The AMF meta-model started life as
+ <a class="ulink" href="/wiki/http://www.agent2005.anl.gov/2006procpdf/Parker_Agent_2006.pdf" target="_new">"score"</a>, a component of the Repast Simphony environment. It wasn't fully utilized within Simphony, and migrated from there to the MetaABM project. The MetaABM project defined a complete editor, code-generation and model execution suite that formed the initial AMP AMF contribution. Argonne National Labs supported the initial development of score and Metascape, LLC continues development of MetaABM and both agreed to contribute the relevant IP to the Eclipse project in 2009.
+ </p>
+<p>Miles Parker is a consultant and software developer with over ten years of experience in the agent-based modeling field and twenty years developing object-oriented tools and frameworks. Metascape, LLC provides Agent-Based Modeling tools, including sophisticated tools based on the AMF platform, and comprehensive consulting services. For more information on Metascape products and services visit
+ <a class="ulink" href="http://metascapeabm.com" target="_new">http://metascapeabm.com</a>.
+ </p>
+</div>
+</div>
+<div class="section" title="Structure">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Structure"></a>Structure</h2>
</div>
</div>
</div>
@@ -190,8 +229,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Design"></a>Design</h2>
+<h3 class="title">
+<a name="Design"></a>Design</h3>
</div>
</div>
</div>
@@ -202,8 +241,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Details"></a>Details</h2>
+<h3 class="title">
+<a name="Details"></a>Details</h3>
</div>
</div>
</div>
@@ -211,8 +250,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="General"></a>General</h3>
+<h4 class="title">
+<a name="General"></a>General</h4>
</div>
</div>
</div>
@@ -221,8 +260,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Named_Entities"></a>Named Entities</h4>
+<h5 class="title">
+<a name="Named_Entities"></a>Named Entities</h5>
</div>
</div>
</div>
@@ -230,8 +269,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Label"></a>Label</h5>
+<h6 class="title">
+<a name="Label"></a>Label</h6>
</div>
</div>
</div>
@@ -241,8 +280,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="ID"></a>ID</h5>
+<h6 class="title">
+<a name="ID"></a>ID</h6>
</div>
</div>
</div>
@@ -253,8 +292,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Description"></a>Description</h5>
+<h6 class="title">
+<a name="Description"></a>Description</h6>
</div>
</div>
</div>
@@ -264,8 +303,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Plural_Label"></a>Plural Label</h5>
+<h6 class="title">
+<a name="Plural_Label"></a>Plural Label</h6>
</div>
</div>
</div>
@@ -277,8 +316,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Agents"></a>Agents</h3>
+<h4 class="title">
+<a name="Agents"></a>Agents</h4>
</div>
</div>
</div>
@@ -286,8 +325,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Simple_Agents"></a>Simple Agents</h4>
+<h5 class="title">
+<a name="Simple_Agents"></a>Simple Agents</h5>
</div>
</div>
</div>
@@ -296,19 +335,19 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Attributes"></a>Attributes</h5>
+<h6 class="title">
+<a name="Attributes"></a>Attributes</h6>
</div>
</div>
</div>
<p>As described in the attribute sections above.</p>
</div>
-<div class="section" title="Actions=">
+<div class="section" title="Actions">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Actions.3D"></a>Actions=</h5>
+<h6 class="title">
+<a name="Actions"></a>Actions</h6>
</div>
</div>
</div>
@@ -318,8 +357,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Styles"></a>Styles</h5>
+<h6 class="title">
+<a name="Styles"></a>Styles</h6>
</div>
</div>
</div>
@@ -330,8 +369,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Context_Agents_.28Contexts.29"></a>Context Agents (Contexts)</h4>
+<h5 class="title">
+<a name="Context_Agents_.28Contexts.29"></a>Context Agents (Contexts)</h5>
</div>
</div>
</div>
@@ -340,8 +379,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Agents_2"></a>Agents</h5>
+<h6 class="title">
+<a name="Agents_2"></a>Agents</h6>
</div>
</div>
</div>
@@ -351,8 +390,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Spaces"></a>Spaces</h5>
+<h6 class="title">
+<a name="Spaces"></a>Spaces</h6>
</div>
</div>
</div>
@@ -364,8 +403,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Attributes_2"></a>Attributes</h3>
+<h4 class="title">
+<a name="Attributes_2"></a>Attributes</h4>
</div>
</div>
</div>
@@ -375,8 +414,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Basic_Attributes"></a>Basic Attributes</h4>
+<h5 class="title">
+<a name="Basic_Attributes"></a>Basic Attributes</h5>
</div>
</div>
</div>
@@ -385,36 +424,36 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Type"></a>Type</h5>
+<h6 class="title">
+<a name="Type"></a>Type</h6>
</div>
</div>
</div>
<p>These can be anyone of the following: </p>
-<table id="N100C4">
+<table id="N100E0">
<tr>
-
+
<td>Boolean</td>
- <td>A value that is simply true or false. Note that unless this value really is a simple binary value, you should consider using state instead. (See details below.) For example, rather than representing gender as a 'Female' boolean value, define a 'Gender' state with values 'Male' and "Female'. Generated artifacts and documentation will be much clearer, and you'll be able to easily modify the model later if for example you discover that there are more than two potential gender categories that are relevant to your model.</td>
-
+ <td>A value that is simply true or false. Note that unless this value really is a simple binary value, you should consider using state instead. (See details below.) For example, rather than representing gender as a 'Female' boolean value, define a 'Gender' state with values 'Male' and "Female'. Generated artifacts and documentation will be much clearer, and you'll be able to easily modify the model later if for example you discover that there are more than two potential gender categories that are relevant to your model.</td>
+
</tr>
<tr>
-
+
<td>Integer</td>
- <td>A discrete whole number value, such as "100", "-1", "10029920". It's generally a good idea to represent any value that can never have a decimal value as an integer.</td>
-
+ <td>A discrete whole number value, such as "100", "-1", "10029920". It's generally a good idea to represent any value that can never have a decimal value as an integer.</td>
+
</tr>
<tr>
-
+
<td>Real</td>
- <td>A continuous number value. While these are typically represented in software as floating point numbers, they can conceivably represent numbers at any arbitrary precision and in any scheme. Note that while technically speaking we should be representing irrational numbers, this is not currently supported for default values and users should simply use the closest decimal approximation.</td>
-
+ <td>A continuous number value. While these are typically represented in software as floating point numbers, they can conceivably represent numbers at any arbitrary precision and in any scheme. Note that while technically speaking we should be representing irrational numbers, this is not currently supported for default values and users should simply use the closest decimal approximation.</td>
+
</tr>
<tr>
-
+
<td>Symbol</td>
- <td>A string representing some state. More precisely, a computationally arbitrary value with contextual meaning. This could be any kind of identifier. For example, you might use it to store some kind of input coding from data that is then converted into an object state. Or it could simply be an agent's name. But theoretically (though this is not currently supported) one could imagine a symbol using an idiogram, an icon or even a sound that identifies or represents the agent in question.</td>
-
+ <td>A string representing some state. More precisely, a computationally arbitrary value with contextual meaning. This could be any kind of identifier. For example, you might use it to store some kind of input coding from data that is then converted into an object state. Or it could simply be an agent's name. But theoretically (though this is not currently supported) one could imagine a symbol using an idiogram, an icon or even a sound that identifies or represents the agent in question.</td>
+
</tr>
</table>
<p>(Undefined and Numeric types should not be used within a well-defined model.)</p>
@@ -423,8 +462,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Default_Value"></a>Default Value</h5>
+<h6 class="title">
+<a name="Default_Value"></a>Default Value</h6>
</div>
</div>
</div>
@@ -434,8 +473,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Gather_Data"></a>Gather Data</h5>
+<h6 class="title">
+<a name="Gather_Data"></a>Gather Data</h6>
</div>
</div>
</div>
@@ -445,8 +484,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Immutable"></a>Immutable</h5>
+<h6 class="title">
+<a name="Immutable"></a>Immutable</h6>
</div>
</div>
</div>
@@ -456,8 +495,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Units"></a>Units</h5>
+<h6 class="title">
+<a name="Units"></a>Units</h6>
</div>
</div>
</div>
@@ -468,8 +507,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Arrays"></a>Arrays</h4>
+<h5 class="title">
+<a name="Arrays"></a>Arrays</h5>
</div>
</div>
</div>
@@ -478,8 +517,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Size"></a>Size</h5>
+<h6 class="title">
+<a name="Size"></a>Size</h6>
</div>
</div>
</div>
@@ -490,8 +529,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="States"></a>States</h4>
+<h5 class="title">
+<a name="States"></a>States</h5>
</div>
</div>
</div>
@@ -500,8 +539,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="State_Options"></a>State Options</h5>
+<h6 class="title">
+<a name="State_Options"></a>State Options</h6>
</div>
</div>
</div>
@@ -511,8 +550,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Default_Option"></a>Default Option</h5>
+<h6 class="title">
+<a name="Default_Option"></a>Default Option</h6>
</div>
</div>
</div>
@@ -524,8 +563,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Spaces_2"></a>Spaces</h3>
+<h4 class="title">
+<a name="Spaces_2"></a>Spaces</h4>
</div>
</div>
</div>
@@ -534,8 +573,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Space_.28Continuous.29"></a>Space (Continuous)</h4>
+<h5 class="title">
+<a name="Space_.28Continuous.29"></a>Space (Continuous)</h5>
</div>
</div>
</div>
@@ -544,43 +583,36 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Border_Rule"></a>Border Rule</h5>
+<h6 class="title">
+<a name="Border_Rule"></a>Border Rule</h6>
</div>
</div>
</div>
<p>A value representing what happens to an agent when that agent is asked to move beyond its extent.</p>
-<table id="N1013F">
-<tr>
-
-<td>Periodic</td>
- <td>When encountering an edge, the agent will treat the space as wrapping around to the other side of the space. For example, if the agent at location
- <a class="ulink" href="1,2" target="_new">1,2</a> (0-based) within a Moore space (see grid discussion below) of size
- <a class="ulink" href="10,10" target="_new">10,10</a> is asked to find some other agent within distance 3, the agent look in the square defined between
- <a class="ulink" href="8,9" target="_new">8,9</a> and
- <a class="ulink" href="4,5" target="_new">4,5</a>. An agent asked to move beyond the confines of the space will simply stop when it reaches the edge. You can imagine this as taking a piece of graph paper and connecting the opposite edges. You can't actually do that with paper, but if you could you would have a toroidal (donut) shape in three dimensions defining the shape in two.
- </td>
-
-</tr>
-<tr>
-
-<td>APeriodic</td>
- <td>When encountering an edge, the agent treats it as the edge of the space. For example, if the agent at location
- <a class="ulink" href="1,2" target="_new">1,2</a> is asked to find some other agent within distance 3, the agent look between
- <a class="ulink" href="0,0" target="_new">0,0</a> and
- <a class="ulink" href="4,5" target="_new">4,5</a>. An agent asked to move beyond the confines of the space will simply stop when it reaches the edge.
- </td>
-
-</tr>
-</table>
+<div class="variablelist">
+<dl>
+<dt>
+<span class="term">Periodic</span>
+</dt>
+<dd>
+<p>When encountering an edge, the agent will treat the space as wrapping around to the other side of the space. For example, if the agent at location {1,2} (0-based) within a Moore space (see grid discussion below) of size {10,10} is asked to find some other agent within distance 3, the agent look in the square defined between {8,9} and {4,5}. An agent asked to move beyond the confines of the space will simply stop when it reaches the edge. You can imagine this as taking a piece of graph paper and connecting the opposite edges. You can't actually do that with paper, but if you could you would have a toroidal (donut) shape in three dimensions defining the shape in two.</p>
+</dd>
+<dt>
+<span class="term">APeriodic</span>
+</dt>
+<dd>
+<p>When encountering an edge, the agent treats it as the edge of the space. For example, if the agent at location {1,2} is asked to find some other agent within distance 3, the agent look between {0,0} and {4,5}. An agent asked to move beyond the confines of the space will simply stop when it reaches the edge.</p>
+</dd>
+</dl>
+</div>
<p>The "Strict" and "Bouncy" values are obsolete and should not be used.</p>
</div>
<div class="section" title="Dimensionality">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Dimensionality"></a>Dimensionality</h5>
+<h6 class="title">
+<a name="Dimensionality"></a>Dimensionality</h6>
</div>
</div>
</div>
@@ -591,8 +623,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Grid"></a>Grid</h4>
+<h5 class="title">
+<a name="Grid"></a>Grid</h5>
</div>
</div>
</div>
@@ -602,8 +634,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Multi-Occupant"></a>Multi-Occupant</h5>
+<h6 class="title">
+<a name="Multi-Occupant"></a>Multi-Occupant</h6>
</div>
</div>
</div>
@@ -613,40 +645,44 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Neighborhood"></a>Neighborhood</h5>
+<h6 class="title">
+<a name="Neighborhood"></a>Neighborhood</h6>
</div>
</div>
</div>
<p>This value determines what constitutes a region within a particular distance from the agent. The value for this is often critical in obtaining particular behavior from a model, and shouldn't be overlooked. There are three possible values:</p>
-<table id="N10190">
-<tr>
-
-<td>Euclidian</td>
- <td>The distance between any two cells is taken to be the "real" distance. For example, if an agent was within a chess board, and we wanted to find all agents within distance three of it, we could determine that by taking a string of length 3, tacking it to the center of the source square, and including all cells whose centers we can reach with the other string end. Note that although Euclidean space may seem the most reasonable neighborhood configuration to choose, this really isn't the case. Euclidean space is continuous whereas grid space is discrete, and mapping the two to each other can create unexpected issues. Still, this is a good choice for models representing notional real spaces.</td>
-
-</tr>
-<tr>
-
-<td>Moore</td>
- <td>Here, the distance between any two cells is defined by the number of edge <span style="color: red"><i>or</i></span> corner adjacent cells crossed to get between them. To continue the chess board analogy, this is the set of moves that a king can make. Note that this does not map well to real space at all, as a cell at distance 1 in a moore space is at distance sqrt(2) in "real" space.</td>
-
-</tr>
-<tr>
-
-<td>Von-Neumann</td>
- <td>Here, the distance between any two cells is defined by the number of edge adjacent cells crossed to get between them. This is the set of moves that a rook might make on a chess board -- if a rook could only move one square at a time. It is also often referred to as a Manhattan distance for the self-evident reason.</td>
-
-</tr>
-</table>
+<div class="variablelist">
+<dl>
+<dt>
+<span class="term">Euclidean</span>
+</dt>
+<dd>
+<p>The distance between any two cells is taken to be the "real" distance. For example, if an agent was within a chess board, and we wanted to find all agents within distance three of it, we could determine that by taking a string of length 3, tacking it to the center of the source square, and including all cells whose centers we can reach with the other string end. Note that although Euclidean space may seem the most reasonable neighborhood configuration to choose, this really isn't the case. Euclidean space is continuous whereas grid space is discrete, and mapping the two to each other can create unexpected issues. Still, this is a good choice for models representing notional real spaces.</p>
+</dd>
+<dt>
+<span class="term">Moore</span>
+</dt>
+<dd>
+<p>Here, the distance between any two cells is defined by the number of edge
+ <span class="italic">or</span> corner adjacent cells crossed to get between them. To continue the chess board analogy, this is the set of moves that a king can make. Note that this does not map well to real space at all, as a cell at distance 1 in a moore space is at distance sqrt(2) in "real" space.
+ </p>
+</dd>
+<dt>
+<span class="term">Von-Neumann</span>
+</dt>
+<dd>
+<p>Here, the distance between any two cells is defined by the number of edge adjacent cells crossed to get between them. This is the set of moves that a rook might make on a chess board -- if a rook could only move one square at a time. It is also often referred to as a Manhattan distance for the self-evident reason.</p>
+</dd>
+</dl>
+</div>
</div>
</div>
<div class="section" title="Network">
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Network"></a>Network</h4>
+<h5 class="title">
+<a name="Network"></a>Network</h5>
</div>
</div>
</div>
@@ -656,8 +692,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Directed"></a>Directed</h5>
+<h6 class="title">
+<a name="Directed"></a>Directed</h6>
</div>
</div>
</div>
@@ -668,8 +704,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Geography"></a>Geography</h4>
+<h5 class="title">
+<a name="Geography"></a>Geography</h5>
</div>
</div>
</div>
@@ -681,8 +717,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Reference"></a>Reference</h2>
+<h3 class="title">
+<a name="Reference"></a>Reference</h3>
</div>
</div>
</div>
@@ -690,8 +726,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Diagrams"></a>Diagrams</h3>
+<h4 class="title">
+<a name="Diagrams"></a>Diagrams</h4>
</div>
</div>
</div>
@@ -700,19 +736,19 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Meta-Classes"></a>Meta-Classes</h4>
+<h5 class="title">
+<a name="Meta-Classes"></a>Meta-Classes</h5>
</div>
</div>
</div>
<p>Our first diagram depicts the core structural design of the model. </p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/StructureComplexDiagram.png"></div>
<p>
-
+
</p>
<div class="literallayout">
<p>There seems to be a lot going on here, but the basic components are pretty straightforward as we can see in the next diagram.<br>
@@ -724,18 +760,18 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Key_Collaborations"></a>Key Collaborations</h4>
+<h5 class="title">
+<a name="Key_Collaborations"></a>Key Collaborations</h5>
</div>
</div>
</div>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/StructureSimpleDiagram.png"></div>
<p>
-
+
</p>
<div class="literallayout">
<p>Core interactions are in Red. The meta-model structure is essentially a Composite pattern. <br>
@@ -747,8 +783,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Details_2"></a>Details</h4>
+<h5 class="title">
+<a name="Details_2"></a>Details</h5>
</div>
</div>
</div>
@@ -778,12 +814,12 @@
</div>
</div>
</div>
-<div class="chapter" title="Chapter 3. Actions">
+<div class="section" title="Actions">
<div class="titlepage">
<div>
<div>
-<h2 class="title">
-<a name="Actions"></a>Chapter 3. Actions</h2>
+<h2 class="title" style="clear: both">
+<a name="Actions_2"></a>Actions</h2>
</div>
</div>
</div>
@@ -792,34 +828,34 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Background"></a>Background</h2>
+<h3 class="title">
+<a name="Background"></a>Background</h3>
</div>
</div>
</div>
<p>Actions allow the definition of behavior for agents at a very high level. You can think of actions as being analogous to methods in a traditional object-oriented model but that analogy only goes so far. In the same way that methods are defined as part of objects, actions belong to particular agents. (Though even more expressive ways of defining actions are contemplated in future releases.) In the next section we go into detail about what Actions are and how they can be used to define all agent behavior. They are also conceptually more challenging as unlike with structure they have no direct analogies to past agent representations.</p>
<p>An action provides simple, well-defined details that a model can use to determine what steps to take in model execution. That definition seems general enough to be almost useless, but its important to understand that an action is not equivalent to an instruction, a method or a query. In fact, actions can have aspects of all of these. But an action is not in itself an instruction specifying exactly
- <span class="italic">how</span> the modeling engine should do something -- instead an action represents
- <span class="italic">what</span> the modeler intends for the agents to do. (Technically, we might say that Actions takes a "declarative" approach instead of an 'imperative' approach, but that's not quite true, because actions do allow us to define behavior in a richer way than most declarative approaches, and many action constructs map directly to imperative approaches.)
- </p>
+ <span class="italic">how</span> the modeling engine should do something -- instead an action represents
+ <span class="italic">what</span> the modeler intends for the agents to do. (Technically, we might say that Actions takes a "declarative" approach instead of an 'imperative' approach, but that's not quite true, because actions do allow us to define behavior in a richer way than most declarative approaches, and many action constructs map directly to imperative approaches.)
+ </p>
<p>Actions are connected together in a series of sources and targets. (Technically, an acyclic directed graph.) In an abstract sense that is similar to the way any programming language is defined although that structure isn't usually obvious because of the constraints of textual representations. But unlike a typical programming language, in Actions it is not the execution thread (the processor) that moves from one instruction to the next, but the result of the previous action. In this way, action results "flow" from the output of one action into the next action.</p>
<p>Why are these distinctions between traditional Object-Oriented and the Action approaches important? They give us the advantages of simplicity, clarity and flexibility that
- <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Dataflow_programming" target="_new">data-flow approaches</a> like spreadsheets and some query languages have, but with less restrictions. At the same time, they can bring us much of the power and expressiveness of
- <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Functional_programming" target="_new">functional languages</a> like Lisp or
- <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Logical_programming" target="_new">logical languages</a> like Prolog, but without the level of complexity and obscurity that such languages can have.
- </p>
+ <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Dataflow_programming" target="_new">data-flow approaches</a> like spreadsheets and some query languages have, but with less restrictions. At the same time, they can bring us much of the power and expressiveness of
+ <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Functional_programming" target="_new">functional languages</a> like Lisp or
+ <a class="ulink" href="/wiki/http://en.wikipedia.org/wiki/Logical_programming" target="_new">logical languages</a> like Prolog, but without the level of complexity and obscurity that such languages can have.
+ </p>
<p>We can get a better idea for how Actions work by thinking about how a spreadsheet works. In a spreadsheet, we might define a cell A that adds up a row of data, say "Income". We might define another cell C ("Profit") that takes A and adds it to another cell B that adds up another row of data ("Expenses"). Now, if we change a value in any of the rows, all of the other rows are added up and we get the results in A and B updated automatically. We never had to write code that said something like "for each cell in row X, where...". In fact, we don't really care
- <span class="italic">how</span> our Spreadsheet program adds up the numbers -- it could have added them all up at once but in backward order, or stored a running total somewhere and updated just the difference in value for the cell we changed -- what we care about is
- <span class="italic">what</span> the result is, and whether it is correct.
- </p>
+ <span class="italic">how</span> our Spreadsheet program adds up the numbers -- it could have added them all up at once but in backward order, or stored a running total somewhere and updated just the difference in value for the cell we changed -- what we care about is
+ <span class="italic">what</span> the result is, and whether it is correct.
+ </p>
<p>But Actions are much more powerful than a spreadsheet, because what is flowing from Action A to Action B is not just a number, but any model component such as a space or a set of agents that we need to use in target actions.</p>
</div>
<div class="section" title="Design">
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Design_2"></a>Design</h2>
+<h3 class="title">
+<a name="Design_2"></a>Design</h3>
</div>
</div>
</div>
@@ -828,84 +864,84 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Kinds_of_Actions"></a>Kinds of Actions</h3>
+<h4 class="title">
+<a name="Kinds_of_Actions"></a>Kinds of Actions</h4>
</div>
</div>
</div>
<p>Before getting into the details of how each Actions work together, or the various kinds of Actions, it will be helpful to take a broad overview of how they all fit together. As discussed above, actions are strung together in a sequence or flow. They're always composed of two parts, though those parts can be assembled and intermixed in many different ways. First, we search for a collection of agents, and then we do something with that selection. We refer to these two parts as Selections and Commands. (For the technically minded, another useful way of looking at the Actions approach is as a Query Transformation language, as with SQL and Stored Procedures. Except again, the results of the queries along with the transformations flow through from one query to the next.) Selections find the agents we want to do something with, and the commands do it. We need some way to start the whole chain of actions off, and so we have a kind of Selection called a Root Selection, or simply a Root. Secondly, we need some way to actually make the agents exist in the model in the first place, so we have a Create Agents action. Finally, we have special commands called builders that allow us to create the spaces that the agents will occupy. All of these are discussed in detail in the section that follows this one.</p>
<p>These are all summarized in the diagram below:</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsBlocks.png"></div>
<p>
-
+
</p>
</div>
<div class="section" title="Flow">
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Flow"></a>Flow</h3>
+<h4 class="title">
+<a name="Flow"></a>Flow</h4>
</div>
</div>
</div>
<p>First, let's look at how actions define the basic path that agents take during a model run. As with any programming language, the path we take through the program specification is what determines our state when we get there. In a pure object oriented program, the path just defines the control flow -- what we are doing. The actual state of our model is defined within the object itself. If we call a method B from another method A, we'll be relying on method A to set the values that we need into the object state itself. In a purely functional program the path defines how we are going to deal with whatever has been explicitly passed in to a function that has been called, that is the function parameters. In fact, most languages such as Java combine aspects of both approaches.</p>
<p>In Actions, the path itself implicitly carries all of the context of prior execution with it. This means that we don't have to worry about storing context in the object -- as we would in an object-oriented language -- or passing the correct values from one method call to the next as we would in a functional language. Instead, Actions can use the implicit context of the path of flow to determine what the current state of execution is.</p>
<p>Again, behaviors in Actions are always defined by a set of
- <span class="italic">selections</span> and
- <span class="italic">queries</span>. In the following diagram, we can see the pattern.
- </p>
+ <span class="italic">selections</span> and
+ <span class="italic">queries</span>. In the following diagram, we can see the pattern.
+ </p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSequence.png"></div>
<p>
-
+
</p>
<p>First, we define a Root Selection for a Rule, Schedule or other triggering event. Then, we might add a series of Query and Logic Actions to define the specific agents that we are interested in. These are all part of the Selection. Next, we might define a series of Commands to determine what to do with those agents. Or, we could use the result of that selection to immediately define another selection, for example if we are searching for an agent that is near another agent. The next diagram depicts a simple example.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSimpleSequence.png"></div>
<p>
-
+
</p>
<p>Here, we create a rule, and then check the results of two queries. For any agents that meet those criteria, we'll evaluate some function based on their state, and then set some value on them. In the next example, we'll first create the rule, and then create a new selection with a set of criteria. Finally, we'll do a move based on those queries.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSimpleSequence2.png"></div>
<p>
-
+
</p>
<p>In the following example, we've defined a set of actions and their relationships. We have a selection, a few queries and a couple of logic operators leading to a Set Action. We'll describe in detail below how Logic Actions are used in conjunction with other actions to assemble any kind of query structure needed. But for now, we'll focus on the control flow itself.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsFlowSimple.png"></div>
<p>
-
+
</p>
<p>As you have probably already guessed, the agents that have the Set Action applied to them could take one of two paths through the Action flow. Readers with experience with programming or formal logic will note that this looks just like a parse tree, and while that's basically what it is, there are important differences. For example, if we looked at the following structure as a definition of control flow for a single agent we'd take them to be equivalent. Both would evaluate the statement (Query 1 AND Query 2) OR Query 3 for each agent.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsFlowUnion.png"></div>
<p>
-
+
</p>
<p>Within Actions in many cases these two approaches will also act equivalently. If we are simply setting a value, it doesn't matter how an agent gets to that Set Action, as long as it gets there. All sources that flow into a given target Action act like a logical union since any of the paths might reach that target. But note that we have two flows moving in parallel in the flow on the right. What happens when the conditions for
- <span class="italic">both</span> branches are true? As the set of agents flow through each branch the Set Action on the left will be evaluated once, while the one on the right will be evaluated twice. Again, this often ends up with the same behavior, but not always. If for example, the evaluate Action uses the value of the attribute that we are setting as input, we can get different results. Of course, you can write code in any language that accomplishes the same thing, but the code will look quite different. For example, if we wrote the same basic logic in Java, in the first case we'd have something like:
- </p>
+ <span class="italic">both</span> branches are true? As the set of agents flow through each branch the Set Action on the left will be evaluated once, while the one on the right will be evaluated twice. Again, this often ends up with the same behavior, but not always. If for example, the evaluate Action uses the value of the attribute that we are setting as input, we can get different results. Of course, you can write code in any language that accomplishes the same thing, but the code will look quite different. For example, if we wrote the same basic logic in Java, in the first case we'd have something like:
+ </p>
<div class="literallayout">
<p>if ((query1.evaluate() && query2.evaluate()) || query3.evaluate()) {<br>
doSomething();<br>
@@ -930,29 +966,29 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Selections"></a>Selections</h3>
+<h4 class="title">
+<a name="Selections"></a>Selections</h4>
</div>
</div>
</div>
<p>Selections are a key concept in Actions. Put simply, selections define what we are searching for and where. They are defined by a combination of Select, Query and Logic Actions. Each time we create a new Select Action, we define a new selection. Queries can be used to further refine selections either immediately after or later in the Action flow, as described in the next section. Logic Actions are used to combine and organize the Action flow defined by Query Actions. In order to understand how these three pieces work together, we need to understand the idea of selection boundaries.</p>
<p>A selection boundary determines the set of selection actions that are used to determine what agents to apply target actions to. For example, in the following diagram, we can see the extent of the boundary for a straightforward selection.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSelBoundarySimple.png"></div>
<p>
-
+
</p>
<p>Each time we create a new selection, we define a new set of boundaries.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSelBoundary2Parts.png"></div>
<p>
-
+
</p>
<p>A very important aspect of boundaries is that they apply to a group of actions that begin with a Query Action, and not just such a group that begins with a Select Action. This is because Query Actions can be directly part of a selection definition, but they can also refine selections, as we'll see. So where does one selection boundary end and the next one begin? The simple rule is that the end of the boundary is defined for a given Action by the place where:</p>
<div class="orderedlist">
@@ -967,73 +1003,73 @@
</div>
<p>In other words, as soon as a Logic Action occurs in a path leading to an Action, any following Query will define a new boundary, as we can see in the following example. </p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSelBoundary11A.png"></div>
<p>
-
+
</p>
<p>Note that we refer to "Selection 1" and Selection 1A". This is because Selection 1A is a refinement of Selection 1 along its particular path of flow. When a query appears for the same selection but past a particular boundary, you can think of it as a sort of filter on the selection contents. We don't have a "Selection 2" here because any Actions that refer to "Selection 1" along the current path of flow will be acting on the selection defined by Selection 1 and Selection 1A.</p>
-<p>These rules allow actions to be defined in the simplest possible way, but it is important to understand their implication as they result in behavior that can be different from what someone used to and imperative programming environment such as Java might expect. In a simple case the distinction might not matter. For example, if we are using a Query 1 to test whether an agent's attribute a = x and attribute b = y, we would get the same outcome if we placed intersected the queries as if we simply put them in sequence. Internally we would actually be searching for agents with a = x, and
- <span class="italic">then</span> taking those agents and choosing those agents with b=y, but the outcome would be the same. But consider a more sophisticated case, where we are searching for neighboring available cells.
- </p>
+<p>These rules allow actions to be defined in the simplest possible way, but it is important to understand their implication as they result in behavior that can be different from what someone used to and imperative programming environment such as Java might expect. In a simple case the distinction might not matter. For example, if we are using a Query 1 to test whether an agent's attribute a == x and attribute b == y, we would get the same outcome if we placed intersected the queries as if we simply put them in sequence. Internally we would actually be searching for agents with a == x, and
+ <span class="italic">then</span> taking those agents and choosing those agents with b==y, but the outcome would be the same. But consider a more sophisticated case, where we are searching for neighboring available cells.
+ </p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsSelBoundaryComplex.png"></div>
<p>
-
+
</p>
<p>In the first case, we execute a search for all agents that meet the two criteria. This means that if there are
- <span class="italic">any</span> neighboring cells which are available, we're guaranteed to find one (random) cell. In the second case, we first search for all cells that are neighbors. This will match any agents that include both available and non available agents. Now, at this point since our search returns one agent (in the current AMF design -- richer behavior will be supported in the future) the randomly selected agent could be either available or not. So in the second case, we might end up with no cell to move to, and thus make no move at all. This then becomes an important aspect of model design. For example, if one were defining a model where neighbors played a game with each other, one might want to instruct agents to play the game only with neighbors that have a certain wealth threshold. In the real-world situation that we are modeling, we might simply search for neighbors who are over a given wealth threshold and then play the game with them. This would imply that information about other agent's wealth is open knowledge. Or, we might simply select a random neighbor, and ask that neighbor to play a game with us. Upon discovering that our neighbor does not meet our wealth criteria, we would then choose not to play with them. Here we are modeling a cost in time to obtain information about another agent's wealth, because we might miss an opportunity to play the game with another agent on that round.
- </p>
+ <span class="italic">any</span> neighboring cells which are available, we're guaranteed to find one (random) cell. In the second case, we first search for all cells that are neighbors. This will match any agents that include both available and non available agents. Now, at this point since our search returns one agent (in the current AMF design -- richer behavior will be supported in the future) the randomly selected agent could be either available or not. So in the second case, we might end up with no cell to move to, and thus make no move at all. This then becomes an important aspect of model design. For example, if one were defining a model where neighbors played a game with each other, one might want to instruct agents to play the game only with neighbors that have a certain wealth threshold. In the real-world situation that we are modeling, we might simply search for neighbors who are over a given wealth threshold and then play the game with them. This would imply that information about other agent's wealth is open knowledge. Or, we might simply select a random neighbor, and ask that neighbor to play a game with us. Upon discovering that our neighbor does not meet our wealth criteria, we would then choose not to play with them. Here we are modeling a cost in time to obtain information about another agent's wealth, because we might miss an opportunity to play the game with another agent on that round.
+ </p>
</div>
<div class="section" title="Weaving">
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Weaving"></a>Weaving</h3>
+<h4 class="title">
+<a name="Weaving"></a>Weaving</h4>
</div>
</div>
</div>
<p>Now, let's put the concepts of Actions sequences and boundaries together to see how we can easily define complex interactions between multiple selections. When we define a Select, the state of its selection flows through and with any subsequent selections. So for example, if we have a Root Action rule, and then do a selection based on it, we'll have access to the agent from the original context as well as all of the subsequent selections. We can refer to any previous selection for any subsequent action. For example, instead of setting the value for the rule agent, we might instead set a value for an agent we've found in a target selection.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsWeavingSetAnother.png"></div>
<p>
-
+
</p>
<p>Inputs to functions also use selections. (We'll discuss more details in the functions section.) In the following example, we're adding the wealth of the Selection 1 agent to the wealth of the Selection 2 agent and using that value to set some other value. (Here, perhaps we are modeling an agent in a winner takes all game, in which case we'd also add a Set Action on Selection 2 and set the second agent's wealth to 0.)</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsWeavingEvaluate.png"></div>
<p>
-
+
</p>
<p>But we can also use selections in defining Query Actions themselves. So in the following example, we select a neighbor agent and then compare the age of our Rule agent with the age of the Selection 2 agent. If and only if those ages are the same will we execute the target Set Action. This example also demonstrates why we refer to the data flow as weaving. Query Actions can be used to refine selections at any point in the data flow. Selections and their uses are interwoven throughout an action sequence.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsWeaving1A.png"></div>
<p>
-
+
</p>
<p>Finally, we can put all of these concepts together by weaving selections together with flows. As we discussed in the flow section, if we use multiple paths in the Query, the agents that flow through from any prior Query can follow multiple paths at once. And as we discussed in the selection section, the selection and its boundaries determine what agents we will be working with at any given evaluation point in the flow. Now, consider the following example:</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsWeaving2.png"></div>
<p>
-
+
</p>
<p>Before going into further details we need to introduce one more important concept. As we'll see in the detailed explanation of each Action below, Transformation Actions such as Move or Connect take multiple selections. The first selection defines the set of agents that will be performing the action. In the case of a Move agent, this refers to the mover. The second selection, which for Move we call "destination", refers to the selection that will be receiving the action. In the case of movement this is the agent or location that the Rule agent will be moving to. If we follow the flows through, we can note two important outcomes of our model design -- a Rule agent might move twice if it meets the criteria for both the blue path and the red path and that it might move to a different location each time.</p>
</div>
@@ -1042,27 +1078,27 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Details_3"></a>Details</h2>
+<h3 class="title">
+<a name="Details_3"></a>Details</h3>
</div>
</div>
</div>
<p>In this section, we'll dig into the specific role of each of the Actions. From the design discussion we hopefully have some sense of how these all fit together in general.
- Let's look at the overall view again amd then dig into the details.</p>
+ Let's look at the overall view again amd then dig into the details.</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsBlocks.png"></div>
<p>
-
+
</p>
<div class="section" title="Selections">
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Selections_2"></a>Selections</h3>
+<h4 class="title">
+<a name="Selections_2"></a>Selections</h4>
</div>
</div>
</div>
@@ -1071,8 +1107,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Select"></a>Select</h4>
+<h5 class="title">
+<a name="Select"></a>Select</h5>
</div>
</div>
</div>
@@ -1081,8 +1117,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Selection"></a>Selection</h5>
+<h6 class="title">
+<a name="Selection"></a>Selection</h6>
</div>
</div>
</div>
@@ -1092,8 +1128,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Agent"></a>Agent</h5>
+<h6 class="title">
+<a name="Agent"></a>Agent</h6>
</div>
</div>
</div>
@@ -1103,8 +1139,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Space"></a>Space</h5>
+<h6 class="title">
+<a name="Space"></a>Space</h6>
</div>
</div>
</div>
@@ -1115,8 +1151,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="For"></a>For</h5>
+<h6 class="title">
+<a name="For"></a>For</h6>
</div>
</div>
</div>
@@ -1127,8 +1163,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Query"></a>Query</h4>
+<h5 class="title">
+<a name="Query"></a>Query</h5>
</div>
</div>
</div>
@@ -1137,20 +1173,20 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Function"></a>Function</h5>
+<h6 class="title">
+<a name="Function"></a>Function</h6>
</div>
</div>
</div>
-<p>A query function is evaluated to determine the results of a particular selection. Functions can represent very simple search criteria such as "My Age = Your Age", but they can also represent complex and inter-related concepts such as spatial relationships. See the functions section for more information on specific functions.</p>
+<p>A query function is evaluated to determine the results of a particular selection. Functions can represent very simple search criteria such as "My Age == Your Age", but they can also represent complex and inter-related concepts such as spatial relationships. See the functions section for more information on specific functions.</p>
</div>
</div>
<div class="section" title="Logic">
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Logic"></a>Logic</h4>
+<h5 class="title">
+<a name="Logic"></a>Logic</h5>
</div>
</div>
</div>
@@ -1160,8 +1196,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Intersection"></a>Intersection</h4>
+<h5 class="title">
+<a name="Intersection"></a>Intersection</h5>
</div>
</div>
</div>
@@ -1171,8 +1207,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Union"></a>Union</h4>
+<h5 class="title">
+<a name="Union"></a>Union</h5>
</div>
</div>
</div>
@@ -1182,8 +1218,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Difference"></a>Difference</h4>
+<h5 class="title">
+<a name="Difference"></a>Difference</h5>
</div>
</div>
</div>
@@ -1193,8 +1229,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Roots"></a>Roots</h4>
+<h5 class="title">
+<a name="Roots"></a>Roots</h5>
</div>
</div>
</div>
@@ -1204,8 +1240,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Build"></a>Build</h4>
+<h5 class="title">
+<a name="Build"></a>Build</h5>
</div>
</div>
</div>
@@ -1215,8 +1251,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Initialize"></a>Initialize</h4>
+<h5 class="title">
+<a name="Initialize"></a>Initialize</h5>
</div>
</div>
</div>
@@ -1226,8 +1262,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Rule"></a>Rule</h4>
+<h5 class="title">
+<a name="Rule"></a>Rule</h5>
</div>
</div>
</div>
@@ -1237,18 +1273,18 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Schedule"></a>Schedule</h4>
+<h5 class="title">
+<a name="Schedule"></a>Schedule</h5>
</div>
</div>
</div>
-<p>A schedule is executed on a recurring basis, according to the values detailed below. Note that schedules are often overused. In most agent-based models it makes sense to have any behaviors occur at the same granularity using a Rule. Please note that Schedules are not currently supported in the Escap target, but that support should be available soon. In the following descriptions we refer to period as the current iteration of the model, that is where time = t.</p>
+<p>A schedule is executed on a recurring basis, according to the values detailed below. Note that schedules are often overused. In most agent-based models it makes sense to have any behaviors occur at the same granularity using a Rule. Please note that Schedules are not currently supported in the Escap target, but that support should be available soon. In the following descriptions we refer to period as the current iteration of the model, that is where time == t.</p>
<div class="section" title="Start">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Start"></a>Start</h5>
+<h6 class="title">
+<a name="Start"></a>Start</h6>
</div>
</div>
</div>
@@ -1258,8 +1294,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Interval"></a>Interval</h5>
+<h6 class="title">
+<a name="Interval"></a>Interval</h6>
</div>
</div>
</div>
@@ -1269,8 +1305,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Priority"></a>Priority</h5>
+<h6 class="title">
+<a name="Priority"></a>Priority</h6>
</div>
</div>
</div>
@@ -1280,8 +1316,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Pick"></a>Pick</h5>
+<h6 class="title">
+<a name="Pick"></a>Pick</h6>
</div>
</div>
</div>
@@ -1292,8 +1328,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Watch"></a>Watch</h4>
+<h5 class="title">
+<a name="Watch"></a>Watch</h5>
</div>
</div>
</div>
@@ -1302,8 +1338,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Attribute"></a>Attribute</h5>
+<h6 class="title">
+<a name="Attribute"></a>Attribute</h6>
</div>
</div>
</div>
@@ -1315,8 +1351,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Commands"></a>Commands</h3>
+<h4 class="title">
+<a name="Commands"></a>Commands</h4>
</div>
</div>
</div>
@@ -1324,8 +1360,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Evaluate"></a>Evaluate</h4>
+<h5 class="title">
+<a name="Evaluate"></a>Evaluate</h5>
</div>
</div>
</div>
@@ -1334,8 +1370,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Selection_2"></a>Selection</h5>
+<h6 class="title">
+<a name="Selection_2"></a>Selection</h6>
</div>
</div>
</div>
@@ -1345,8 +1381,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Function_2"></a>Function</h5>
+<h6 class="title">
+<a name="Function_2"></a>Function</h6>
</div>
</div>
</div>
@@ -1356,8 +1392,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Inputs"></a>Inputs</h5>
+<h6 class="title">
+<a name="Inputs"></a>Inputs</h6>
</div>
</div>
</div>
@@ -1368,8 +1404,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Move"></a>Move</h4>
+<h5 class="title">
+<a name="Move"></a>Move</h5>
</div>
</div>
</div>
@@ -1378,8 +1414,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Selection_3"></a>Selection</h5>
+<h6 class="title">
+<a name="Selection_3"></a>Selection</h6>
</div>
</div>
</div>
@@ -1390,8 +1426,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Set"></a>Set</h4>
+<h5 class="title">
+<a name="Set"></a>Set</h5>
</div>
</div>
</div>
@@ -1403,8 +1439,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Example"></a>Example</h2>
+<h3 class="title">
+<a name="Example"></a>Example</h3>
</div>
</div>
</div>
@@ -1433,21 +1469,21 @@
</div>
<p>Now, notice that although it's convenient to speak as if there is only one "Find Partner" and one "Partner Neighbor" in step 4 above, in fact selections are flowing through for each of the results of each of the previous action sequences, and we can refer to each of the directly. We could represent these behaviors in many different ways. For example, we might want to specify the model in a (hand-drawn) graphical language or in a (made-up) textual language:</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsExample.png"></div>
<p>
-
+
</p>
<p>This is how it looks in an actual model:</p>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsExampleNew.png"></div>
<p>
-
+
</p>
<p>And here is how this works in detail:</p>
<div class="orderedlist">
@@ -1473,7 +1509,7 @@
<div class="orderedlist">
<ol class="orderedlist" type="a">
<li class="listitem">
-<p>We want to search for someone who is the same age as us. This highlights the importance of the idea of the Selection in the Actions design. We're qualifying Age by our <span style="color: red"><font>Partner</font></span> and <span style="color: red"><font>ourselves</font></span>. The selection carries throughout the flow of execution and this context is an explicit part of the entire structure. Note that this is very different from the way control flow works in a traditional imperative language such as Java.</p>
+<p>We want to search for someone who is the same age as us. This highlights the importance of the idea of the Selection in the Actions design. We're qualifying Age by the rule agent's partner for the first input and by the rule agent for the second. The selection carries throughout the flow of execution and this context is an explicit part of the entire structure. Note that this is very different from the way control flow works in a traditional imperative language such as Java.</p>
</li>
<li class="listitem">
<p>We also want to search using a function for nearness, "within", which takes a parameter of vision. Note that the spatial functions are all polymorphic -- if we decided later on that we would rather search within say "Kevin Bacon space", that is a graph structure representation of space, we would only need to change the space we've defined in Select Partner.</p>
@@ -1523,8 +1559,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Reference_2"></a>Reference</h2>
+<h3 class="title">
+<a name="Reference_2"></a>Reference</h3>
</div>
</div>
</div>
@@ -1532,8 +1568,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Diagrams_2"></a>Diagrams</h3>
+<h4 class="title">
+<a name="Diagrams_2"></a>Diagrams</h4>
</div>
</div>
</div>
@@ -1542,26 +1578,26 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Meta-Classes_2"></a>Meta-Classes</h4>
+<h5 class="title">
+<a name="Meta-Classes_2"></a>Meta-Classes</h5>
</div>
</div>
</div>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/ActionsDiagram.png"></div>
<p>
-
+
</p>
</div>
<div class="section" title="Details">
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Details_4"></a>Details</h4>
+<h5 class="title">
+<a name="Details_4"></a>Details</h5>
</div>
</div>
</div>
@@ -1595,12 +1631,12 @@
</div>
</div>
</div>
-<div class="chapter" title="Chapter 4. Functions">
+<div class="section" title="Functions">
<div class="titlepage">
<div>
<div>
-<h2 class="title">
-<a name="Functions"></a>Chapter 4. Functions</h2>
+<h2 class="title" style="clear: both">
+<a name="Functions"></a>Functions</h2>
</div>
</div>
</div>
@@ -1633,8 +1669,8 @@
<div class="titlepage">
<div>
<div>
-<h2 class="title" style="clear: both">
-<a name="Reference_3"></a>Reference</h2>
+<h3 class="title">
+<a name="Reference_3"></a>Reference</h3>
</div>
</div>
</div>
@@ -1642,8 +1678,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Function_Library"></a>Function Library</h3>
+<h4 class="title">
+<a name="Function_Library"></a>Function Library</h4>
</div>
</div>
</div>
@@ -1651,8 +1687,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Operators"></a>Operators</h4>
+<h5 class="title">
+<a name="Operators"></a>Operators</h5>
</div>
</div>
</div>
@@ -1661,8 +1697,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Logical_Operators"></a>Logical Operators</h4>
+<h5 class="title">
+<a name="Logical_Operators"></a>Logical Operators</h5>
</div>
</div>
</div>
@@ -1670,8 +1706,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Not"></a>Not</h5>
+<h6 class="title">
+<a name="Not"></a>Not</h6>
</div>
</div>
</div>
@@ -1681,8 +1717,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Equal"></a>Equal</h5>
+<h6 class="title">
+<a name="Equal"></a>Equal</h6>
</div>
</div>
</div>
@@ -1692,8 +1728,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Identical"></a>Identical</h5>
+<h6 class="title">
+<a name="Identical"></a>Identical</h6>
</div>
</div>
</div>
@@ -1703,8 +1739,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Greater"></a>Greater</h5>
+<h6 class="title">
+<a name="Greater"></a>Greater</h6>
</div>
</div>
</div>
@@ -1714,8 +1750,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Lesser"></a>Lesser</h5>
+<h6 class="title">
+<a name="Lesser"></a>Lesser</h6>
</div>
</div>
</div>
@@ -1725,8 +1761,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Greater_or_Equal"></a>Greater or Equal</h5>
+<h6 class="title">
+<a name="Greater_or_Equal"></a>Greater or Equal</h6>
</div>
</div>
</div>
@@ -1736,8 +1772,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Lesser_or_Equal"></a>Lesser or Equal</h5>
+<h6 class="title">
+<a name="Lesser_or_Equal"></a>Lesser or Equal</h6>
</div>
</div>
</div>
@@ -1747,8 +1783,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="True"></a>True</h5>
+<h6 class="title">
+<a name="True"></a>True</h6>
</div>
</div>
</div>
@@ -1758,8 +1794,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="False"></a>False</h5>
+<h6 class="title">
+<a name="False"></a>False</h6>
</div>
</div>
</div>
@@ -1769,8 +1805,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Identity"></a>Identity</h5>
+<h6 class="title">
+<a name="Identity"></a>Identity</h6>
</div>
</div>
</div>
@@ -1780,8 +1816,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Different"></a>Different</h5>
+<h6 class="title">
+<a name="Different"></a>Different</h6>
</div>
</div>
</div>
@@ -1792,8 +1828,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Numeric_Operators"></a>Numeric Operators</h4>
+<h5 class="title">
+<a name="Numeric_Operators"></a>Numeric Operators</h5>
</div>
</div>
</div>
@@ -1801,8 +1837,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Negative_Value"></a>Negative Value</h5>
+<h6 class="title">
+<a name="Negative_Value"></a>Negative Value</h6>
</div>
</div>
</div>
@@ -1812,8 +1848,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Add"></a>Add</h5>
+<h6 class="title">
+<a name="Add"></a>Add</h6>
</div>
</div>
</div>
@@ -1823,8 +1859,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Subtract"></a>Subtract</h5>
+<h6 class="title">
+<a name="Subtract"></a>Subtract</h6>
</div>
</div>
</div>
@@ -1834,8 +1870,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Multiply"></a>Multiply</h5>
+<h6 class="title">
+<a name="Multiply"></a>Multiply</h6>
</div>
</div>
</div>
@@ -1845,8 +1881,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Divide"></a>Divide</h5>
+<h6 class="title">
+<a name="Divide"></a>Divide</h6>
</div>
</div>
</div>
@@ -1856,8 +1892,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Power"></a>Power</h5>
+<h6 class="title">
+<a name="Power"></a>Power</h6>
</div>
</div>
</div>
@@ -1867,8 +1903,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Modulo"></a>Modulo</h5>
+<h6 class="title">
+<a name="Modulo"></a>Modulo</h6>
</div>
</div>
</div>
@@ -1878,8 +1914,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Increment"></a>Increment</h5>
+<h6 class="title">
+<a name="Increment"></a>Increment</h6>
</div>
</div>
</div>
@@ -1889,8 +1925,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Decrement"></a>Decrement</h5>
+<h6 class="title">
+<a name="Decrement"></a>Decrement</h6>
</div>
</div>
</div>
@@ -1900,8 +1936,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Unit_Value"></a>Unit Value</h5>
+<h6 class="title">
+<a name="Unit_Value"></a>Unit Value</h6>
</div>
</div>
</div>
@@ -1911,8 +1947,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Zero_Value"></a>Zero Value</h5>
+<h6 class="title">
+<a name="Zero_Value"></a>Zero Value</h6>
</div>
</div>
</div>
@@ -1922,8 +1958,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Original_Value"></a>Original Value</h5>
+<h6 class="title">
+<a name="Original_Value"></a>Original Value</h6>
</div>
</div>
</div>
@@ -1934,8 +1970,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Spatial"></a>Spatial</h4>
+<h5 class="title">
+<a name="Spatial"></a>Spatial</h5>
</div>
</div>
</div>
@@ -1943,8 +1979,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Nearest"></a>Nearest</h5>
+<h6 class="title">
+<a name="Nearest"></a>Nearest</h6>
</div>
</div>
</div>
@@ -1954,8 +1990,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Toward"></a>Toward</h5>
+<h6 class="title">
+<a name="Toward"></a>Toward</h6>
</div>
</div>
</div>
@@ -1965,8 +2001,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Within"></a>Within</h5>
+<h6 class="title">
+<a name="Within"></a>Within</h6>
</div>
</div>
</div>
@@ -1982,8 +2018,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Neighbor"></a>Neighbor</h5>
+<h6 class="title">
+<a name="Neighbor"></a>Neighbor</h6>
</div>
</div>
</div>
@@ -1993,8 +2029,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Include_Self"></a>Include Self</h5>
+<h6 class="title">
+<a name="Include_Self"></a>Include Self</h6>
</div>
</div>
</div>
@@ -2004,8 +2040,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Within_2D_Boundary"></a>Within 2D Boundary</h5>
+<h6 class="title">
+<a name="Within_2D_Boundary"></a>Within 2D Boundary</h6>
</div>
</div>
</div>
@@ -2021,8 +2057,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Here"></a>Here</h5>
+<h6 class="title">
+<a name="Here"></a>Here</h6>
</div>
</div>
</div>
@@ -2032,8 +2068,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Available"></a>Available</h5>
+<h6 class="title">
+<a name="Available"></a>Available</h6>
</div>
</div>
</div>
@@ -2043,8 +2079,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Distance"></a>Distance</h5>
+<h6 class="title">
+<a name="Distance"></a>Distance</h6>
</div>
</div>
</div>
@@ -2060,8 +2096,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Away"></a>Away</h5>
+<h6 class="title">
+<a name="Away"></a>Away</h6>
</div>
</div>
</div>
@@ -2071,8 +2107,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Minimize"></a>Minimize</h5>
+<h6 class="title">
+<a name="Minimize"></a>Minimize</h6>
</div>
</div>
</div>
@@ -2082,8 +2118,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Maximize"></a>Maximize</h5>
+<h6 class="title">
+<a name="Maximize"></a>Maximize</h6>
</div>
</div>
</div>
@@ -2093,8 +2129,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Location_2D"></a>Location 2D</h5>
+<h6 class="title">
+<a name="Location_2D"></a>Location 2D</h6>
</div>
</div>
</div>
@@ -2111,8 +2147,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Boundary_2D"></a>Boundary 2D</h5>
+<h6 class="title">
+<a name="Boundary_2D"></a>Boundary 2D</h6>
</div>
</div>
</div>
@@ -2130,8 +2166,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Random"></a>Random</h4>
+<h5 class="title">
+<a name="Random"></a>Random</h5>
</div>
</div>
</div>
@@ -2139,8 +2175,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_In_Range"></a>Random In Range</h5>
+<h6 class="title">
+<a name="Random_In_Range"></a>Random In Range</h6>
</div>
</div>
</div>
@@ -2159,8 +2195,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_To_Limit"></a>Random To Limit</h5>
+<h6 class="title">
+<a name="Random_To_Limit"></a>Random To Limit</h6>
</div>
</div>
</div>
@@ -2178,8 +2214,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_Unit"></a>Random Unit</h5>
+<h6 class="title">
+<a name="Random_Unit"></a>Random Unit</h6>
</div>
</div>
</div>
@@ -2195,8 +2231,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_Boolean"></a>Random Boolean</h5>
+<h6 class="title">
+<a name="Random_Boolean"></a>Random Boolean</h6>
</div>
</div>
</div>
@@ -2206,8 +2242,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_Weighted"></a>Random Weighted</h5>
+<h6 class="title">
+<a name="Random_Weighted"></a>Random Weighted</h6>
</div>
</div>
</div>
@@ -2225,8 +2261,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_Member"></a>Random Member</h5>
+<h6 class="title">
+<a name="Random_Member"></a>Random Member</h6>
</div>
</div>
</div>
@@ -2244,8 +2280,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Random_State"></a>Random State</h5>
+<h6 class="title">
+<a name="Random_State"></a>Random State</h6>
</div>
</div>
</div>
@@ -2264,8 +2300,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Graphic"></a>Graphic</h4>
+<h5 class="title">
+<a name="Graphic"></a>Graphic</h5>
</div>
</div>
</div>
@@ -2273,8 +2309,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Oval"></a>Shape Oval</h5>
+<h6 class="title">
+<a name="Shape_Oval"></a>Shape Oval</h6>
</div>
</div>
</div>
@@ -2284,8 +2320,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Rectangle"></a>Shape Rectangle</h5>
+<h6 class="title">
+<a name="Shape_Rectangle"></a>Shape Rectangle</h6>
</div>
</div>
</div>
@@ -2295,8 +2331,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Inset"></a>Shape Inset</h5>
+<h6 class="title">
+<a name="Shape_Inset"></a>Shape Inset</h6>
</div>
</div>
</div>
@@ -2312,8 +2348,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Marker"></a>Shape Marker</h5>
+<h6 class="title">
+<a name="Shape_Marker"></a>Shape Marker</h6>
</div>
</div>
</div>
@@ -2323,8 +2359,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Marker_2"></a>Shape Marker 2</h5>
+<h6 class="title">
+<a name="Shape_Marker_2"></a>Shape Marker 2</h6>
</div>
</div>
</div>
@@ -2334,8 +2370,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Shape_Marker_3"></a>Shape Marker 3</h5>
+<h6 class="title">
+<a name="Shape_Marker_3"></a>Shape Marker 3</h6>
</div>
</div>
</div>
@@ -2345,8 +2381,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_RGB"></a>Color RGB</h5>
+<h6 class="title">
+<a name="Color_RGB"></a>Color RGB</h6>
</div>
</div>
</div>
@@ -2364,8 +2400,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Red"></a>Color Red</h5>
+<h6 class="title">
+<a name="Color_Red"></a>Color Red</h6>
</div>
</div>
</div>
@@ -2375,8 +2411,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Yellow"></a>Color Yellow</h5>
+<h6 class="title">
+<a name="Color_Yellow"></a>Color Yellow</h6>
</div>
</div>
</div>
@@ -2386,8 +2422,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Blue"></a>Color Blue</h5>
+<h6 class="title">
+<a name="Color_Blue"></a>Color Blue</h6>
</div>
</div>
</div>
@@ -2397,8 +2433,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Orange"></a>Color Orange</h5>
+<h6 class="title">
+<a name="Color_Orange"></a>Color Orange</h6>
</div>
</div>
</div>
@@ -2408,8 +2444,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Green"></a>Color Green</h5>
+<h6 class="title">
+<a name="Color_Green"></a>Color Green</h6>
</div>
</div>
</div>
@@ -2419,8 +2455,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Purple"></a>Color Purple</h5>
+<h6 class="title">
+<a name="Color_Purple"></a>Color Purple</h6>
</div>
</div>
</div>
@@ -2430,8 +2466,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Black"></a>Color Black</h5>
+<h6 class="title">
+<a name="Color_Black"></a>Color Black</h6>
</div>
</div>
</div>
@@ -2441,8 +2477,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_White"></a>Color White</h5>
+<h6 class="title">
+<a name="Color_White"></a>Color White</h6>
</div>
</div>
</div>
@@ -2452,8 +2488,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Color_Gray"></a>Color Gray</h5>
+<h6 class="title">
+<a name="Color_Gray"></a>Color Gray</h6>
</div>
</div>
</div>
@@ -2463,8 +2499,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Graphic_Outline"></a>Graphic Outline</h5>
+<h6 class="title">
+<a name="Graphic_Outline"></a>Graphic Outline</h6>
</div>
</div>
</div>
@@ -2474,8 +2510,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Graphic_Fill"></a>Graphic Fill</h5>
+<h6 class="title">
+<a name="Graphic_Fill"></a>Graphic Fill</h6>
</div>
</div>
</div>
@@ -2486,8 +2522,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Time"></a>Time</h4>
+<h5 class="title">
+<a name="Time"></a>Time</h5>
</div>
</div>
</div>
@@ -2495,8 +2531,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Now"></a>Now</h5>
+<h6 class="title">
+<a name="Now"></a>Now</h6>
</div>
</div>
</div>
@@ -2513,8 +2549,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Math"></a>Math</h4>
+<h5 class="title">
+<a name="Math"></a>Math</h5>
</div>
</div>
</div>
@@ -2522,420 +2558,420 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Sine"></a>Sine</h5>
+<h6 class="title">
+<a name="Sine"></a>Sine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sin(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sin(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sin(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sin(double)</a>
+
</p>
</div>
<div class="section" title="Cosine">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Cosine"></a>Cosine</h5>
+<h6 class="title">
+<a name="Cosine"></a>Cosine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cos(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cos(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cos(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cos(double)</a>
+
</p>
</div>
<div class="section" title="Tangent">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Tangent"></a>Tangent</h5>
+<h6 class="title">
+<a name="Tangent"></a>Tangent</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tan(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tan(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tan(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tan(double)</a>
+
</p>
</div>
<div class="section" title="Arc Sine">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Arc_Sine"></a>Arc Sine</h5>
+<h6 class="title">
+<a name="Arc_Sine"></a>Arc Sine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#asin(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#asin(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#asin(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#asin(double)</a>
+
</p>
</div>
<div class="section" title="Arc Cosine">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Arc_Cosine"></a>Arc Cosine</h5>
+<h6 class="title">
+<a name="Arc_Cosine"></a>Arc Cosine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#acos(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#acos(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#acos(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#acos(double)</a>
+
</p>
</div>
<div class="section" title="Arc Tangent">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Arc_Tangent"></a>Arc Tangent</h5>
+<h6 class="title">
+<a name="Arc_Tangent"></a>Arc Tangent</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan(double)</a>
+
</p>
</div>
<div class="section" title="Convert Degree to Radians">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Convert_Degree_to_Radians"></a>Convert Degree to Radians</h5>
+<h6 class="title">
+<a name="Convert_Degree_to_Radians"></a>Convert Degree to Radians</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toRadians(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toRadians(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toRadians(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toRadians(double)</a>
+
</p>
</div>
<div class="section" title="Convert Radians to Degrees">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Convert_Radians_to_Degrees"></a>Convert Radians to Degrees</h5>
+<h6 class="title">
+<a name="Convert_Radians_to_Degrees"></a>Convert Radians to Degrees</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toDegrees(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toDegrees(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toDegrees(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#toDegrees(double)</a>
+
</p>
</div>
<div class="section" title="Exp">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Exp"></a>Exp</h5>
+<h6 class="title">
+<a name="Exp"></a>Exp</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#exp(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#exp(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#exp(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#exp(double)</a>
+
</p>
</div>
<div class="section" title="Log">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Log"></a>Log</h5>
+<h6 class="title">
+<a name="Log"></a>Log</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log(double)</a>
+
</p>
</div>
<div class="section" title="Log b10">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Log_b10"></a>Log b10</h5>
+<h6 class="title">
+<a name="Log_b10"></a>Log b10</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log10(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log10(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log10(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log10(double)</a>
+
</p>
</div>
<div class="section" title="Square Root">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Square_Root"></a>Square Root</h5>
+<h6 class="title">
+<a name="Square_Root"></a>Square Root</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#squareRoot(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#squareRoot(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#squareRoot(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#squareRoot(double)</a>
+
</p>
</div>
<div class="section" title="Cube Root">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Cube_Root"></a>Cube Root</h5>
+<h6 class="title">
+<a name="Cube_Root"></a>Cube Root</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cbrt(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cbrt(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cbrt(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cbrt(double)</a>
+
</p>
</div>
<div class="section" title="Remainder">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Remainder"></a>Remainder</h5>
+<h6 class="title">
+<a name="Remainder"></a>Remainder</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#iEEEremainder(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#iEEEremainder(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#iEEEremainder(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#iEEEremainder(double,%20double)</a>
+
</p>
</div>
<div class="section" title="Ceiling">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Ceiling"></a>Ceiling</h5>
+<h6 class="title">
+<a name="Ceiling"></a>Ceiling</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ceil(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ceil(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ceil(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ceil(double)</a>
+
</p>
</div>
<div class="section" title="Floor">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Floor"></a>Floor</h5>
+<h6 class="title">
+<a name="Floor"></a>Floor</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#floor(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#floor(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#floor(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#floor(double)</a>
+
</p>
</div>
<div class="section" title="Rount">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Rount"></a>Rount</h5>
+<h6 class="title">
+<a name="Rount"></a>Rount</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#rint(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#rint(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#rint(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#rint(double)</a>
+
</p>
</div>
<div class="section" title="Arc Tangent Rectangular">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Arc_Tangent_Rectangular"></a>Arc Tangent Rectangular</h5>
+<h6 class="title">
+<a name="Arc_Tangent_Rectangular"></a>Arc Tangent Rectangular</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan2(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan2(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan2(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#atan2(double,%20double)</a>
+
</p>
</div>
<div class="section" title="Power">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Power_2"></a>Power</h5>
+<h6 class="title">
+<a name="Power_2"></a>Power</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#pow(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#pow(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#pow(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#pow(double,%20double)</a>
+
</p>
</div>
<div class="section" title="Absolute Value">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Absolute_Value"></a>Absolute Value</h5>
+<h6 class="title">
+<a name="Absolute_Value"></a>Absolute Value</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#abs(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#abs(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#abs(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#abs(double)</a>
+
</p>
</div>
<div class="section" title="Maximum">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Maximum"></a>Maximum</h5>
+<h6 class="title">
+<a name="Maximum"></a>Maximum</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#max(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#max(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#max(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#max(double,%20double)</a>
+
</p>
</div>
<div class="section" title="Minimum">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Minimum"></a>Minimum</h5>
+<h6 class="title">
+<a name="Minimum"></a>Minimum</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#min(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#min(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#min(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#min(double,%20double)</a>
+
</p>
</div>
<div class="section" title="ULP">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="ULP"></a>ULP</h5>
+<h6 class="title">
+<a name="ULP"></a>ULP</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ulp(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ulp(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ulp(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#ulp(double)</a>
+
</p>
</div>
<div class="section" title="Sign">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Sign"></a>Sign</h5>
+<h6 class="title">
+<a name="Sign"></a>Sign</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#signum(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#signum(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#signum(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#signum(double)</a>
+
</p>
</div>
<div class="section" title="Hyperbolic Sine">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Hyperbolic_Sine"></a>Hyperbolic Sine</h5>
+<h6 class="title">
+<a name="Hyperbolic_Sine"></a>Hyperbolic Sine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sinh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sinh(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sinh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#sinh(double)</a>
+
</p>
</div>
<div class="section" title="Hyperbolic Cosine">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Hyperbolic_Cosine"></a>Hyperbolic Cosine</h5>
+<h6 class="title">
+<a name="Hyperbolic_Cosine"></a>Hyperbolic Cosine</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cosh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cosh(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cosh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#cosh(double)</a>
+
</p>
</div>
<div class="section" title="Hyperbolic Tan">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Hyperbolic_Tan"></a>Hyperbolic Tan</h5>
+<h6 class="title">
+<a name="Hyperbolic_Tan"></a>Hyperbolic Tan</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tanh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tanh(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tanh(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#tanh(double)</a>
+
</p>
</div>
<div class="section" title="Hypotuneuse">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Hypotuneuse"></a>Hypotuneuse</h5>
+<h6 class="title">
+<a name="Hypotuneuse"></a>Hypotuneuse</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#hypotuneuse(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#hypotuneuse(double,%20double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#hypotuneuse(double,%20double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#hypotuneuse(double,%20double)</a>
+
</p>
</div>
<div class="section" title="Expm1">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Expm1"></a>Expm1</h5>
+<h6 class="title">
+<a name="Expm1"></a>Expm1</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#expm1(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#expm1(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#expm1(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#expm1(double)</a>
+
</p>
</div>
<div class="section" title="Log1p">
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Log1p"></a>Log1p</h5>
+<h6 class="title">
+<a name="Log1p"></a>Log1p</h6>
</div>
</div>
</div>
<p>See JavaDoc:
- <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log1p(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log1p(double)</a>
-
+ <a class="ulink" href="http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log1p(double)" target="_new">http://java.sun.com/javase/6/docs/api/java/lang/Math.html#log1p(double)</a>
+
</p>
</div>
</div>
@@ -2943,8 +2979,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="List"></a>List</h4>
+<h5 class="title">
+<a name="List"></a>List</h5>
</div>
</div>
</div>
@@ -2952,8 +2988,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Item"></a>Item</h5>
+<h6 class="title">
+<a name="Item"></a>Item</h6>
</div>
</div>
</div>
@@ -2972,8 +3008,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Length"></a>Length</h5>
+<h6 class="title">
+<a name="Length"></a>Length</h6>
</div>
</div>
</div>
@@ -2992,8 +3028,8 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Distribution"></a>Distribution</h4>
+<h5 class="title">
+<a name="Distribution"></a>Distribution</h5>
</div>
</div>
</div>
@@ -3001,8 +3037,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Uniform_Cross_Distribution"></a>Uniform Cross Distribution</h5>
+<h6 class="title">
+<a name="Uniform_Cross_Distribution"></a>Uniform Cross Distribution</h6>
</div>
</div>
</div>
@@ -3022,8 +3058,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Uniform_Additive_Distribution"></a>Uniform Additive Distribution</h5>
+<h6 class="title">
+<a name="Uniform_Additive_Distribution"></a>Uniform Additive Distribution</h6>
</div>
</div>
</div>
@@ -3043,8 +3079,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Cross_Distribution"></a>Cross Distribution</h5>
+<h6 class="title">
+<a name="Cross_Distribution"></a>Cross Distribution</h6>
</div>
</div>
</div>
@@ -3063,8 +3099,8 @@
<div class="titlepage">
<div>
<div>
-<h5 class="title">
-<a name="Additive_Distribution"></a>Additive Distribution</h5>
+<h6 class="title">
+<a name="Additive_Distribution"></a>Additive Distribution</h6>
</div>
</div>
</div>
@@ -3085,8 +3121,8 @@
<div class="titlepage">
<div>
<div>
-<h3 class="title">
-<a name="Diagrams_3"></a>Diagrams</h3>
+<h4 class="title">
+<a name="Diagrams_3"></a>Diagrams</h4>
</div>
</div>
</div>
@@ -3095,19 +3131,556 @@
<div class="titlepage">
<div>
<div>
-<h4 class="title">
-<a name="Meta-Classes_3"></a>Meta-Classes</h4>
+<h5 class="title">
+<a name="Meta-Classes_3"></a>Meta-Classes</h5>
</div>
</div>
</div>
<p>
-
+
</p>
<div class="mediaobject">
<img src="images/FunctionsDiagram.png"></div>
<p>
+
+</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="chapter" title="Chapter 2. Creating Agent Models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title">
+<a name="Creating_Agent_Models"></a>Chapter 2. Creating Agent Models</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Getting Started">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Getting_Started"></a>Getting Started</h2>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="chapter" title="Chapter 3. Exploring Agent Models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title">
+<a name="Exploring_Agent_Models"></a>Chapter 3. Exploring Agent Models</h2>
+</div>
+</div>
+</div>
+</div>
+<div class="chapter" title="Chapter 4. Programer's Guide">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title">
+<a name="Programer.27s_Guide"></a>Chapter 4. Programer's Guide</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Overview">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Overview"></a>Overview</h2>
+</div>
+</div>
+</div>
+<p>Escape is a full-featured Agent-Based Modeling (ABM) integrated development environment (IDE) with a Java based API and end user modeling tools. It's based on Ascape, which has been in use for more than 10 years. The core API is very stable, and that should give users a way to explore the features of AMP without concerns about keeping in synch with the rapidly evolving AXF /AGF API. It allows modelers to code in Java and/or generate models with AMF and then execute those models within the same development environment.</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EscapeExecutionScreenshot.png" target="_new">image:EscapeExecutionScreenshot.png</a>
+
+</p>
+<p>A primary purpose of the Escape project -- apart from the obvious goal of providing a nice Eclipse hosted ABM toolkit -- is to provide an exemplar to demonstrate how any arbitrary agent modeling framework can be integrated within the AMP environment. A cool aspect of this is that AMP has no dependencies on Escape, but also that the underlying ABM modeling framework for Escape has no dependencies on AMP -- instead Escape simply provides the runtime glue between AMP and the ABM framework. The underlying ABM framework uses the Ascape API, an API that first began development more than ten years ago and that has not been modified at all in order for it to work within the AMP environment.</p>
+<p>(Well, not quite.. Ascape was refactored into separate non-UI core and a Swing UI projects. This involved a bit of repackaging, but was really straightforward as Ascape follows a strict MVC architecture. Note that currently Escape is bulkier than it will eventually be -- over time we will be generalizing more aspects of Escape into the AMP AXF and AGF components.)</p>
+</div>
+<div class="section" title="Getting Started">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Getting_Started_2"></a>Getting Started</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Documentation and other Resources">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title">
+<a name="Documentation_and_other_Resources"></a>Documentation and other Resources</h3>
+</div>
+</div>
+</div>
+<p>Because it's API is based on Ascape, Escape is one component of AMP that already has extensive documentation. There is complete Javadoc as well as a manual and other web resources. See the
+ <a class="ulink" href="http://ascape.sourceforge.net" target="_new">Ascape Website</a> to locate these resources. The documentation on the main page is a good place to start. It's written for Ascape so ignore all of the bits about project setup, and a lot of the UI is different, but the basics apply to Escape just as well. The
+ <a class="ulink" href="http://ascape.sourceforge.net/docs/TheAscapeManual5.pdf" target="_new">Ascape Manual</a> written by Damon Centola should be very helpful. Take a look at the conversion link below for ideas on how to make the models form the manual work under Ascape. (Converting these models is a great opportunity for a community contribution!)
+ </p>
+</div>
+</div>
+<div class="section" title="Installation">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Installation"></a>Installation</h2>
+</div>
+</div>
+</div>
+<p>Escape is
+ <a class="ulink" href="http://eclipse.org/amp/installing/" target="_new">installed</a> by default with the other model components. If you want to do 3D (really 2 1/2) visualizations, you will want AGF3D and the LWJGL dependency. You can build from source but in that case you'l need to launch a self-hosted runtime, so it's best to simply install from the update site if you're not actually doing AMP development.
+ </p>
+</div>
+<div class="section" title="Exploring Example ABM Models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Exploring_Example_ABM_Models"></a>Exploring Example ABM Models</h2>
+</div>
+</div>
+</div>
+<p>The first thing most people will want to do in AMP is to play with the example models. You don't need to do any programming for this, and the setup is really straightforward. Of course, the first think you'll need to do is
+ <a class="ulink" href="http://eclipse.org/amp/installing" target="_new">Install AMP</a>. (You don't need any of the optional components unless you want to play with the 3D visualizations, Ascape, or Repast.) You can explore AMF models as well as some really interesting classic ABM models.
+ </p>
+<div class="section" title="AMF Models">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title">
+<a name="AMF_Models"></a>AMF Models</h3>
+</div>
+</div>
+</div>
+<p>There are a number of models developed with AMF that can automatically generate example models to run in Escape. There are two ways to run the example models:</p>
+<div class="section" title="Setup Escape Projects">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="Setup_Escape_Projects"></a>Setup Escape Projects</h4>
+</div>
+</div>
+</div>
+<div class="section" title="Creating a New Escape Project">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Creating_a_New_Escape_Project"></a>Creating a New Escape Project</h5>
+</div>
+</div>
+</div>
+<p>The best option is to simply create a new Escape project and drag the models into it! We're working on a simple cheat sheet for this, but until then, just follow these simple steps:</p>
+<div class="orderedlist">
+<ol class="orderedlist" type="1">
+<li class="listitem">
+<p>If you're not already there, open the Agent Modeling Perspective. Select Window > Open Perspective > Other.. and then Agent Modeling. (Or you can choose Window > Reset Perspective and the Agent Modeling perspective should appear in the Open Perspective list itself.)</p>
+</li>
+<li class="listitem">
+<p>Next, let's create the project where we'll place our model. Select File > New > Escape AMF Project. Give it a name like "escape.tutorial", then click Finish.</p>
+</li>
+<li class="listitem">
+<p>Finally grab the Epidemic.metaabm model at
+ <a class="ulink" href="http://download.eclipse.org/amp/models/Epidemic.metaabm" target="_new">http://download.eclipse.org/amp/models/Epidemic.metaabm</a> and drag it into the project. (Depending on your browser the file may load as text directly into your browser, in which case just right-click on the link and save it to a file.)
+ </p>
+</li>
+</ol>
+</div>
+</div>
+<div class="section" title="Using an Pre-Built Example Project">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Using_an_Pre-Built_Example_Project"></a>Using an Pre-Built Example Project</h5>
+</div>
+</div>
+</div>
+<p>If you get really stuck somewhere, you can also get ready made projects from CVS. See
+ <a class="ulink" href="http://eclipse.org/amp/developers/repositoryDetails.php" target="_new">this page</a> for information on CVS setup. The project for Escape example models are located at:
+ </p>
+<div class="literallayout">
+<p>org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.escape<br>
+
+</p>
+</div>
+</div>
+</div>
+<div class="section" title="Run the Model">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="Run_the_Model"></a>Run the Model</h4>
+</div>
+</div>
+</div>
+<p>Right-click on the model, and select "Execute"! You should see something like this:</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EpidemicModelRunning.png" target="_new">image:EpidemicModelRunning.png</a>
</p>
+<p>We're working on more end-user documentaiton, but hopefully you'll find model control pretty self-explanatory. The toolbar buttons allow you to control model execution.</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EpidemicModelControls.png" target="_new">image:EpidemicModelControls.png</a>
+
+</p>
+<p>From right to left, you can start, restart, pause, step, stop and close a model. You can even run multiple models and control them independently. You can also move views around, close them and so on as with any other Eclipse views. Here we're running two separate models for comparison.</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EpidemicModelComparison.png" target="_new">image:EpidemicModelComparison.png</a>
+
+</p>
+<p>If you want to find out more about an agent, show the properties view, and click on agent.</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EpidemicModelAgentProperties.png" target="_new">image:EpidemicModelAgentProperties.png</a>
+
+</p>
+<p>You can experiment with different parameters (settings) for models by then clicking in the gray area away within the view.</p>
+<p>
+
+<a class="ulink" href="/wiki/image:EpidemicModelProperties.png" target="_new">image:EpidemicModelProperties.png</a>
+
+</p>
+<p>There are a number of other things to play around with, such as zooming the agent view or selecting other chart series to display using the Chart Customizer, so just explore. You can always close an active model by clicking on the close toolbar button. Or if you can't access the models controls for some reason, you can open the progress view and close projects form there.</p>
+</div>
+<div class="section" title="Next Steps">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="Next_Steps"></a>Next Steps</h4>
+</div>
+</div>
+</div>
+<p>Other models are located at: (to do)</p>
+<p>To understand the capabilities of AMF, you might also want to try out running the same models automatically generated for Ascape or Repast.</p>
+<div class="literallayout">
+<p>org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.ascape<br>
+org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.repast<br>
+
+</p>
+</div>
+</div>
+</div>
+<div class="section" title="Classic Java ABM Models">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title">
+<a name="Classic_Java_ABM_Models"></a>Classic Java ABM Models</h3>
+</div>
+</div>
+</div>
+<p>Many models have been created using Ascape over the years, including all of the classic models created at Brookings and some other cool models such as Craig Reynold's Boids and a pretty cool little traffic model, and they've all been converted to run in Escape. They're in Java but you can execute and explore them in exactly the same way as the Epidemic model above. All of the Ascape example models have been converted (a straightforward process) from their intial Ascape incarnations. For licensing reasons (they're BSD, not EPL) we can't host them directly on the Eclipse site. You can get the projects in two ways:</p>
+<div class="section" title="From Project Archive">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="From_Project_Archive"></a>From Project Archive</h4>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>Download the Escape examples zip from the Ascape sourceforge site:
+ <a class="ulink" href="http://sourceforge.net/projects/ascape/files/Escape/5.2.0/EscapeExamples.zip/download" target="_new">http://sourceforge.net/projects/ascape/files/Escape/5.2.0/EscapeExamples.zip/download</a>
+
+</p>
+</li>
+<li class="listitem">
+<p>Unzip the file.</p>
+</li>
+<li class="listitem">
+<p>Import them into your workspace. For help, see
+ <a class="ulink" href="http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html" target="_new">this page</a>.
+ </p>
+</li>
+</ul>
+</div>
+</div>
+<div class="section" title="From SVN">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="From_SVN"></a>From SVN</h4>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>Import the SVN projects from the sourceforge SVN. For help, see
+ <a class="ulink" href="/wiki/http://www.eclipse.org/subversive/documentation/teamSupport/find_check_wiz.php_this_page" target="_new">http://www.eclipse.org/subversive/documentation/teamSupport/find_check_wiz.php this page</a>.
+ </p>
+</li>
+</ul>
+</div>
+<div class="literallayout">
+<p>http://ascape.svn.sourceforge.net/svnroot/ascape/org.ascape.escape.models.brook<br>
+http://ascape.svn.sourceforge.net/svnroot/ascape/org.ascape.escape.models.examples<br>
+
+</p>
+</div>
+<p>Once you've downloaded the projects, open up the src folder and navigate to the Java files for the actual models. For example, to run Conway's Life, you'll want src/edu.brook.life.ConwayLife. Right-click on the Java file and select "Execute". There are many models to explore! (It's not always obvious which Java files are for models, so you may have to poke around a bit. We need to put together a catalog here. Another nice opportunity for user contributions.)</p>
+</div>
+</div>
+</div>
+<div class="section" title="Developing Models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Developing_Models"></a>Developing Models</h2>
+</div>
+</div>
+</div>
+<p>The easiest way for Java developers to get started doing agent-based modeling in Eclipse is to begin to write programs using it.To develop new models, you can:</p>
+<div class="orderedlist">
+<ol class="orderedlist" type="1">
+<li class="listitem">
+<p>Create a new Escape project. The Escape projects are actually configured for AMF code generation so there are dependencies and builders in there that you don't need; you can remove all of the escape builders and any of the kitchen sink items. We'll try to get a POJO Escape project wizard out there at some point.</p>
+</li>
+<li class="listitem">
+<p> But it might be simpler to just create a new Plugin Project and add the necessary dependencies there. Have a look at the example escape project to see what you need. Note that you will likely need more dependencies then you need to simply build -- this is because the class loader uses the classes from the project path and so runtime classes have to be there as well. We may simply package an Eclipse runtime convenience plugin to gather these dependencies up a bit.</p>
+</li>
+</ol>
+</div>
+<p>Then just create new Java classes for your root model scape and agents just as you would for an Ascape project.</p>
+</div>
+</div>
+<div class="chapter" title="Chapter 5. Reference">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title">
+<a name="Reference_4"></a>Chapter 5. Reference</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Converting Existing Ascape models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Converting_Existing_Ascape_models"></a>Converting Existing Ascape models</h2>
+</div>
+</div>
+</div>
+<p>There are only a few changes should have to make to existing Ascape models or to use existing Ascape documentation to develop Escape models.</p>
+<div class="section">
+<div class="titlepage"></div>
+<div class="section" title="Model">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="N108CF"></a>Model</h4>
+</div>
+</div>
+</div>
+<p>The core model is completely API compatible. No changes!</p>
+</div>
+<div class="section" title="View">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="View"></a>View</h4>
+</div>
+</div>
+</div>
+<p>Because Escape uses SWT and Ascape uses Swing, there are a few unavoidable incompatibilities. Most of these we avoid by using higher level APIs but here are the key changes that you're likely to have to make:</p>
+<div class="section" title="Convert the low-level imports from AWT and Swing to SWT">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Convert_the_low-level_imports_from_AWT_and_Swing_to_SWT"></a>Convert the low-level imports from AWT and Swing to SWT</h5>
+</div>
+</div>
+</div>
+<p>The simplest way to accomplish this is to remove all of the imports and then organize imports. For example:</p>
+<div class="literallayout">
+<p>java.awt.Color => org.eclipse.swt.graphics.Color<br>
+java.awt.Graphics => org.eclipse.draw2d.Graphics<br>
+
+</p>
+</div>
+<p>Then just do a global find for all of the imports and replace them with nothing. This is a great place for a regexp. Try:</p>
+<div class="literallayout">
+<p>find: import java\.awt\.(.*);<br>
+replace: [nothing]<br>
+
+</p>
+</div>
+<p>You don't have to replace these with the SWT equivalents, just click on the project, right-click and choose "Source:Organize Imports.."
+ By the way, a great way to avoid having to select the right entries in optimize imports and to alert you when you have missed anything is to prevent the awt and swing classes from being used at all. Right-click on project, choose "Build Path:Configure Build Path", go to Libraries tab, open JRE System Library, choose "Access Rules", edit, and then add entries for java/awt/** and javax/swing/**. The code will regenerate and you'll have error markers for all of the stuff that won't work with Escape and Eclipse.</p>
+</div>
+<div class="section" title="Convert color features">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Convert_color_features"></a>Convert color features</h5>
+</div>
+</div>
+</div>
+<p>You can't use AWT colors either so you'll need to replace any colors. AMP provides a convenience classes for Colors called ColorFeature and ColorFeatureConcrete. You can use these or any of the other ways to define SWT colors. For example:</p>
+<div class="literallayout">
+<p>Color.lightGray => ColorFeature.LIGHT_GRAY<br>
+new Color(Math.min(1.0f, (float) (redEnergy + orangeEnergy)), (float) orangeEnergy * .8f, (float) blueEnergy) => <br>
+ ColorFeatureConcrete.create(Math.min(1.0f, (float) (redEnergy + orangeEnergy)), (float) orangeEnergy * .8f, (float) blueEnergy)<br>
+
+</p>
+</div>
+</div>
+<div class="section" title="Change agent color getters">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Change_agent_color_getters"></a>Change agent color getters</h5>
+</div>
+</div>
+</div>
+<p>If you've defined colors through overriding Agents as in most models, you'll need to change the method signature. You could just do a global replace for this one.</p>
+<div class="literallayout">
+<p>public Color getColor( => public Object getPlatformColor(<br>
+
+</p>
+</div>
+</div>
+<div class="section" title="Get rid of image features">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Get_rid_of_image_features"></a>Get rid of image features</h5>
+</div>
+</div>
+</div>
+<p>Escape doesn't support them. In practice they haven't been used a lot. At some point perhaps we'll have nice sprite support instead. :)</p>
+<div class="literallayout">
+<p>public Image getImage() {**} => ""<br>
+
+</p>
+</div>
+</div>
+<div class="section" title="Modify usages of DrawFeatures">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title">
+<a name="Modify_usages_of_DrawFeatures"></a>Modify usages of DrawFeatures</h5>
+</div>
+</div>
+</div>
+<p>If you've created any of your own draw features, you'll need to change them slightly to accommodate the differences between the AWT and SWT / Draw2D APIs. This should be pretty straightforwrd. For example:</p>
+<div class="literallayout">
+<p>g.setColor(...<br>
+g.fillOval(..<br>
+becomes:<br>
+g.setBackgroundColor(<br>
+g.fillOval(..<br>
+
+</p>
+</div>
+<p>That's about it, though it's probable that we've missed something. Please post a message on the amp newsgroup if you run into any other conversion issues.</p>
+</div>
+</div>
+<div class="section" title="Configuration">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="Configuration"></a>Configuration</h4>
+</div>
+</div>
+</div>
+<p>Instead of using Ant, Escape has really nice support for parameterizing and testing models. See
+ <a class="ulink" href="/wiki/Experimenting_and_Testing" target="_new">Experimenting and Testing</a> (todo). If you do want to work with ant you will need to install the plugins from the Sourceforge download site. (These have dependencies that I didn't want to bother with going through the Eclipse IP process to get in. If for some reason you think these should be part of core Escape let Miles know and I'll take care of it.) Ant has not been tested for Escape so it's not even clear it will work.
+ </p>
+</div>
+</div>
+</div>
+</div>
+<div class="chapter" title="Chapter 6. More Information">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title">
+<a name="More_Information"></a>Chapter 6. More Information</h2>
+</div>
+</div>
+</div>
+<div class="section" title="Obtaining Example Models">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both">
+<a name="Obtaining_Example_Models"></a>Obtaining Example Models</h2>
+</div>
+</div>
+</div>
+<p>There is a cheat-sheet available for obtaining the example models. If you would rather obtain them yourself, here is the CVS information:</p>
+<div class="section">
+<div class="titlepage"></div>
+<div class="section" title="Import from CVS">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title">
+<a name="N1092C"></a>Import from CVS</h4>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>Import the CVS projects from the AMP project repository. For help, see
+ <a class="ulink" href="http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/reference/ref-40a.htm" target="_new">this page</a>. For repository details, see
+ <a class="ulink" href="http://eclipse.org/amp/developers/repositoryDetails.php" target="_new">http://eclipse.org/amp/developers/repositoryDetails.php</a>. These are the example projects:
+ </p>
+</li>
+</ul>
+</div>
+<div class="literallayout">
+<p>org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.ascape <br>
+org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.escape <br>
+org.eclipse.amp/org.eclipse.amp.amf/examples/org.eclipse.amp.amf.examples.repast <br>
+
+</p>
+</div>
+<div class="itemizedlist">
+<ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>Right-click on the models to execute them.</p>
+</li>
+<li class="listitem">
+<p>Play around with the model attribute settings and behavior (Acts).</p>
+</li>
+</ul>
+</div>
</div>
</div>
</div>
diff --git a/documentation/amp.pdf b/documentation/amp.pdf
index 08407dd..9efac75 100644
--- a/documentation/amp.pdf
+++ b/documentation/amp.pdf
Binary files differ
diff --git a/documentation/images/EscapeExecutionScreenshot.png b/documentation/images/EscapeExecutionScreenshot.png
new file mode 100644
index 0000000..f03a242
--- /dev/null
+++ b/documentation/images/EscapeExecutionScreenshot.png
Binary files differ
