raw.html - gerrit/www.eclipse.org/amp - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Insert title here</title>
 </head>
 <body>
 <div id="midcolumn"><img style="float: right" src="/amp/images/AMPLogo.png" alt="" />
 <h1>Agent Modeling Platform</h1>
 <h3>Components</h3>
 <p>The AMP project provides extensible frameworks and exemplary tools for representing, editing, generating,
 executing and visualizing agent models. AMP is made up of the following components:</p>
 <div id="amf" class="homeitem">
 <h4>Agent Modeling Framework (AMF)</h4>
 <p>AMF is an Agent-Based Model Meta-Model representation, editor, generator and development environment. The AMF
 Acore meta-model is similar to EMF Ecore (and is itself an Ecore model) but provides high-level support for agents,
 including spatial, behavioral and functional features -- it's focused on ABM but could be useful in many other domains.
 AMF provides code-generation for complete executable models in a pluggable way and can support arbitrary target
 platforms. Targets for Java Skeletons and Intefaces, JUnit test cases, Escape models and documentation are included.
 Targets for other platforms will be provided separately.</p>
 </div>
 <div id="axf" class="homeitem">
 <h4>Agent Execution Framework (AXF)</h4>
 <p>The execution framework provides core interfaces, services and UI for model life-cycle execution, agent
 aggregation, view and control management, and integration with the Eclipse workbench. AXF is not itself intended to
 provide extensive support for runtime execution, but instead acts as an abstraction layer between the Eclipse
 environment and client toolkits. For example, implementations would provide model internal scheduling engines and data
 collection facilities which are wired up at runtime through adapters. While there are no dependencies between AMF and
 AXF, AXF does provide corresponding features where appropriate. As with AMF, AXF is not limited to ABM. Anyone who has a
 need for executing, managing and visualizing Workbench hosted processes containing collections of interacting objects
 may find it useful.</p>
 </div>
 <div id="agf" class="homeitem">
 <h4>Agent Graphics and Visualization Framework (AGF)</h4>
 <p>The graphics framework extends GEF, Draw2D, Zest and other technologies to support real-time visualization of and
 interaction with agent models. Initially, AGF provides support for agents within 2D space and graph structures, but will
 extend that to 3-D, GIS and others. Like the other AMP components, AGF design focus is to provide an extensible
 infrastructure, allowing platform adopters to easily create their own view and editor parts.</p>
 <p>AGF will include two sub-components:
 <ul>
 				<li>AGF-Chart: A dynamic (live) charting facility with end-user oriented interactive tools, including live data support.</li>
 				<li>AGF-Viz: Support for graph and -- eventually -- other dense information dynamic visualization such as nD.</li>
 </ul>
 <h4>Escape</h4>
 <p>Escape is an exemplar ABM toolset. 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.
 <h3>Architecture</h3>
 <p>The overall AMP architecture and Eclipse project dependencies are summarized below:</p>
 <img src="images/AMPArchitectureDiagram.jpg"
 </div>
 </div>

 <div id="rightcolumn">
 <div class="sideitem">
 <h6>Incubation</h6>
 <p>AMP is in the <a href="http://www.eclipse.org/projects/dev_process/validation-phase.php">Incubation Phase</a>.</p>
 <div align="center"><a href="http://www.eclipse.org/projects/what-is-incubation.php"><img align="center"
 				src="http://www.eclipse.org/images/egg-incubation.png" border="0" /></a></div>
 </div>
 <div class="sideitem">
 <h6>Current Status</h6>
 <p>There isn't anything useful here yet! We've just been provisioned, and are in the process of setting up project
 resources and preparing code to move over for the initial drop. Please see our <a
 				href="http://www.eclipse.org/projects/project-plan.php?projectid=modeling.amp">Project Plan</a> for more details.</p>
 </div>

 <div class="sideitem" style="background-color: #C3C4FF; font-size=smaller">
 <h6>What's an Agent-Based Model?</h6>
 <div>The primary focus of AMP is "Agent-Based Modeling". ABMs share characteristics with object models, but are:
 <ul>
 				<li>Spatial: Models have explicit environment(s) in which agents interact. (An environment need not be a
 				physical landscape; other examples of spatial relationships include social networks or positions within a logic
 				system.)</li>
 				<li>Temporal: Models change over discrete units of time.</li>
 				<li>Autonomous: Agent behaviors are activated independently from other object requests.</li>
 				<li>Heterogenous: Agents may share behavior definitions but have apparent and distinct states and behaviors.</li>
 				<li>Collective: Models contain large communities of agents which exhibit collaborative and competitive
 				behaviors.</li>
 				<li>Emergent: Agents have collective macro-behaviors that are non-obvious from agent micro-specifications.</li>
 </ul>
 </div>
 </div>
 <div class="sideitem">
 <h6>Resources</h6>
 <div>As we don't have any AMF specific documentation up yet, here is a bit of background context for the overall project. Please note that these are not Eclipse hosted and Eclipse is not responsible for their content.
 <b>Websites</b>
 <a href="http://metaabm.org">MetaABM</a>
 <p /><a href="http://ascape.sourceforge.net">Ascape</a>
 <p />MetaABM SVN: http://svn.metascapeabm.com/metaabm/
 <p />Ascape SVN: https://ascape.svn.sourceforge.net/svnroot/ascape/
 <b>Papers</b>
 <a href="http://www.pnas.org/content/99/suppl.3/7280.full">Agent-Based Modeling</a>
 <p /><a href="http://jasss.soc.surrey.ac.uk/11/4/12.html">"Why Model?"</a>
 <p /><a href="http://www.agent2006.anl.gov/2006procpdf/Parker_Agent_2006.pdf">Agent-Based
 Meta-Models</a>(An earlier implementation.)
 <p /><a href="http://metascapeabm.com/images/news/tr1-metaabminpictures.pdf">MetaABM in Pictures</a>
 <p /><a href="http://www.pnas.org/content/99/suppl.3/7304.full">Ascape</a>
 <b>Blog Articles</b>
 <a href="http://milesparker.blogspot.com/2009/04/meta-models-for-arbitrary-targets-iii.html">Targeting Multiple APIs</a>
 </div>
 </div>
 <div>
 </div>
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
	<html>
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
	<title>Insert title here</title>
	</head>
	<body>
	<div id="midcolumn"><img style="float: right" src="/amp/images/AMPLogo.png" alt="" />
	<h1>Agent Modeling Platform</h1>
	<h3>Components</h3>
	<p>The AMP project provides extensible frameworks and exemplary tools for representing, editing, generating,
	executing and visualizing agent models. AMP is made up of the following components:</p>
	<div id="amf" class="homeitem">
	<h4>Agent Modeling Framework (AMF)</h4>
	<p>AMF is an Agent-Based Model Meta-Model representation, editor, generator and development environment. The AMF
	Acore meta-model is similar to EMF Ecore (and is itself an Ecore model) but provides high-level support for agents,
	including spatial, behavioral and functional features -- it's focused on ABM but could be useful in many other domains.
	AMF provides code-generation for complete executable models in a pluggable way and can support arbitrary target
	platforms. Targets for Java Skeletons and Intefaces, JUnit test cases, Escape models and documentation are included.
	Targets for other platforms will be provided separately.</p>
	</div>
	<div id="axf" class="homeitem">
	<h4>Agent Execution Framework (AXF)</h4>
	<p>The execution framework provides core interfaces, services and UI for model life-cycle execution, agent
	aggregation, view and control management, and integration with the Eclipse workbench. AXF is not itself intended to
	provide extensive support for runtime execution, but instead acts as an abstraction layer between the Eclipse
	environment and client toolkits. For example, implementations would provide model internal scheduling engines and data
	collection facilities which are wired up at runtime through adapters. While there are no dependencies between AMF and
	AXF, AXF does provide corresponding features where appropriate. As with AMF, AXF is not limited to ABM. Anyone who has a
	need for executing, managing and visualizing Workbench hosted processes containing collections of interacting objects
	may find it useful.</p>
	</div>
	<div id="agf" class="homeitem">
	<h4>Agent Graphics and Visualization Framework (AGF)</h4>
	<p>The graphics framework extends GEF, Draw2D, Zest and other technologies to support real-time visualization of and
	interaction with agent models. Initially, AGF provides support for agents within 2D space and graph structures, but will
	extend that to 3-D, GIS and others. Like the other AMP components, AGF design focus is to provide an extensible
	infrastructure, allowing platform adopters to easily create their own view and editor parts.</p>
	<p>AGF will include two sub-components:
	<ul>
	<li>AGF-Chart: A dynamic (live) charting facility with end-user oriented interactive tools, including live data support.</li>
	<li>AGF-Viz: Support for graph and -- eventually -- other dense information dynamic visualization such as nD.</li>
	</ul>
	<h4>Escape</h4>
	<p>Escape is an exemplar ABM toolset. 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.
	<h3>Architecture</h3>
	<p>The overall AMP architecture and Eclipse project dependencies are summarized below:</p>
	<img src="images/AMPArchitectureDiagram.jpg"
	</div>
	</div>

	<div id="rightcolumn">
	<div class="sideitem">
	<h6>Incubation</h6>
	<p>AMP is in the <a href="http://www.eclipse.org/projects/dev_process/validation-phase.php">Incubation Phase</a>.</p>
	<div align="center"><a href="http://www.eclipse.org/projects/what-is-incubation.php"><img align="center"
	src="http://www.eclipse.org/images/egg-incubation.png" border="0" /></a></div>
	</div>
	<div class="sideitem">
	<h6>Current Status</h6>
	<p>There isn't anything useful here yet! We've just been provisioned, and are in the process of setting up project
	resources and preparing code to move over for the initial drop. Please see our <a
	href="http://www.eclipse.org/projects/project-plan.php?projectid=modeling.amp">Project Plan</a> for more details.</p>
	</div>

	<div class="sideitem" style="background-color: #C3C4FF; font-size=smaller">
	<h6>What's an Agent-Based Model?</h6>
	<div>The primary focus of AMP is "Agent-Based Modeling". ABMs share characteristics with object models, but are:
	<ul>
	<li>Spatial: Models have explicit environment(s) in which agents interact. (An environment need not be a
	physical landscape; other examples of spatial relationships include social networks or positions within a logic
	system.)</li>
	<li>Temporal: Models change over discrete units of time.</li>
	<li>Autonomous: Agent behaviors are activated independently from other object requests.</li>
	<li>Heterogenous: Agents may share behavior definitions but have apparent and distinct states and behaviors.</li>
	<li>Collective: Models contain large communities of agents which exhibit collaborative and competitive
	behaviors.</li>
	<li>Emergent: Agents have collective macro-behaviors that are non-obvious from agent micro-specifications.</li>
	</ul>
	</div>
	</div>
	<div class="sideitem">
	<h6>Resources</h6>
	<div>As we don't have any AMF specific documentation up yet, here is a bit of background context for the overall project. Please note that these are not Eclipse hosted and Eclipse is not responsible for their content.
	<b>Websites</b>
	<a href="http://metaabm.org">MetaABM</a>
	<p /><a href="http://ascape.sourceforge.net">Ascape</a>
	<p />MetaABM SVN: http://svn.metascapeabm.com/metaabm/
	<p />Ascape SVN: https://ascape.svn.sourceforge.net/svnroot/ascape/
	<b>Papers</b>
	<a href="http://www.pnas.org/content/99/suppl.3/7280.full">Agent-Based Modeling</a>
	<p /><a href="http://jasss.soc.surrey.ac.uk/11/4/12.html">"Why Model?"</a>
	<p /><a href="http://www.agent2006.anl.gov/2006procpdf/Parker_Agent_2006.pdf">Agent-Based
	Meta-Models</a>(An earlier implementation.)
	<p /><a href="http://metascapeabm.com/images/news/tr1-metaabminpictures.pdf">MetaABM in Pictures</a>
	<p /><a href="http://www.pnas.org/content/99/suppl.3/7304.full">Ascape</a>
	<b>Blog Articles</b>
	<a href="http://milesparker.blogspot.com/2009/04/meta-models-for-arbitrary-targets-iii.html">Targeting Multiple APIs</a>
	</div>
	</div>
	<div>
	</div>
	</body>
	</html>