geopro:pedro:platforms
Diferenças
Aqui você vê as diferenças entre duas revisões dessa página.
Ambos lados da revisão anteriorRevisão anteriorPróxima revisão | Revisão anterior | ||
geopro:pedro:platforms [2007/07/12 18:53] – pedro | geopro:pedro:platforms [2008/06/12 18:35] (atual) – pedro | ||
---|---|---|---|
Linha 1: | Linha 1: | ||
+ | ====== ABM Discussions and Requirements====== | ||
+ | |||
+ | ====Anatomy of a Toolkit: A comprehensive compendium of various agent-based modelling toolkits, on the market today==== | ||
+ | |C. Nikolay, G. Madey, 2007| Proceedings of Agent2007: Complex interaction and social emergence, 87-97| [[http:// | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Abstract: | ||
+ | can be overwhelming. Moreover, different communities of users prefer different aspects | ||
+ | of a toolkit. This paper is a survey of the toolkits that are available today and how they | ||
+ | compare to each other from a multi-stakeholder perspective. Our goal is to provide users | ||
+ | the ability to better choose a suitable toolkit based on the features abstracted from various | ||
+ | documentation and the first hand experiences of a broad range of communities of users | ||
+ | and compiled into an easy to use compendium. In addition, we expand the Agent Based | ||
+ | Modeling body of knowledge to include information about a breadth of characteristically | ||
+ | and historically diverse platforms. | ||
+ | |||
+ | \\ | ||
+ | |||
====Evaluation of free Java-libraries for social-scientific agent based simulation==== | ====Evaluation of free Java-libraries for social-scientific agent based simulation==== | ||
Linha 4: | Linha 23: | ||
\\ | \\ | ||
- | // This paper compares four freely available programming libraries for support of social scientific agent based computer simulation: RePast, Swarm, Quicksilver, | + | **Abstract: |
+ | |||
+ | \\ | ||
Very subjective choices of the criteria used, without references in the literature. For example, one of the topics is "easy to use," that in terms of Human-Machine | Very subjective choices of the criteria used, without references in the literature. For example, one of the topics is "easy to use," that in terms of Human-Machine | ||
Linha 51: | Linha 72: | ||
At the end of the paper, there is a long list of other tools, and the reasons why they were excluded from the analysis. | At the end of the paper, there is a long list of other tools, and the reasons why they were excluded from the analysis. | ||
- | |||
- | |||
====Requirements Analysis of Agent-Based Simulation Platforms: State of the Art and New Prospects==== | ====Requirements Analysis of Agent-Based Simulation Platforms: State of the Art and New Prospects==== | ||
- | |M. B. Marietto, N. David, J. S. Sichman, H. Coelho, 2003|[[http:// | + | |M. B. Marietto, N. David, |
|M. B. Marietto, N. David, J. S. Sichman, H. Coelho, 2002|Multi-Agent Based Simulation Workshop| [[http:// | |M. B. Marietto, N. David, J. S. Sichman, H. Coelho, 2002|Multi-Agent Based Simulation Workshop| [[http:// | ||
\\ | \\ | ||
- | //In this paper we propose a preliminary reference model for the requirements specification of agent-based simulation platforms. We give the following contributions: | + | **Abstract: |
In effect, when evaluating the importance of requirements analysis in this field it is quite odd to find very few references in the literature about this topic. | In effect, when evaluating the importance of requirements analysis in this field it is quite odd to find very few references in the literature about this topic. | ||
- | This observation becomes even more surprising since one can find a considerable number of platforms (though very heterogeneous) available to the research community.// | + | This observation becomes even more surprising since one can find a considerable number of platforms (though very heterogeneous) available to the research community. |
+ | |||
+ | \\ | ||
- | //a requirement is a feature of a system or a description of something the system is capable of doing in order to reach its objectives. | + | a requirement is a feature of a system or a description of something the system is capable of doing in order to reach its objectives. |
- | [...] it aims to detail the structure of a system, establishing its principles of behaviour.// | + | [...] it aims to detail the structure of a system, establishing its principles of behaviour. |
* **Manage Scheduling Techniques**: | * **Manage Scheduling Techniques**: | ||
Linha 92: | Linha 113: | ||
* **Manage Social Opacity**: conditions under which the control of cognitive information transfer between agents in different societies is possible (organisational borders). instantiate different topologies of opaque social spaces in a dynamic way. while the observed agents and societies must be visible to the observer agent, the observer agent and societies must be opaque to the observed agents. | * **Manage Social Opacity**: conditions under which the control of cognitive information transfer between agents in different societies is possible (organisational borders). instantiate different topologies of opaque social spaces in a dynamic way. while the observed agents and societies must be visible to the observer agent, the observer agent and societies must be opaque to the observed agents. | ||
* **Provide Models of Cognitive Reflectivity**: | * **Provide Models of Cognitive Reflectivity**: | ||
- | |||
- | |||
- | |||
- | |||
====MAS infrastructure definitions, | ====MAS infrastructure definitions, | ||
Linha 101: | Linha 118: | ||
\\ | \\ | ||
- | //This paper attempts to articulate the general role of infrastructure for multi-agent systems (MAS), and why | + | **Abstract: |
infrastructure is a particularly critical issue if we are to increase the visibility and impact of multi-agent | infrastructure is a particularly critical issue if we are to increase the visibility and impact of multi-agent | ||
systems as a universal technology and solution. Second, it presents my current thinking on the socio-technical | systems as a universal technology and solution. Second, it presents my current thinking on the socio-technical | ||
content of the needed infrastructure in four different comers of the multi-agent systems world: science, | content of the needed infrastructure in four different comers of the multi-agent systems world: science, | ||
- | education, application, | + | education, application, |
+ | \\ | ||
+ | The public incentives for widespread attention to and use of analogous technologies such as Web | ||
+ | browsers and cell phones appeared only with the development of | ||
+ | - a stable, reliable, accessible infrastructures, | ||
+ | - a critical mass of " | ||
- | ====The RETSINA MAS Infrastructure==== | + | How will the MAS communities create pedagogical environments |
- | |K. Sycara, M. Paolucci, M. V. Velsen and J. Giampapa, 2003| Autonomous Agents and Multi-Agent Systems|[[http:// | + | and tools that will help develop, transfer, and extend the MAS knowledge and skills |
+ | to impact widening groups of people? Simply put, there are few if any sharable tools | ||
+ | with serious pedagogical aims. | ||
+ | |||
+ | I've divided spheres of MAS activity into four categories, each of which has different infrastructure needs | ||
+ | - the communities in each sphere have different views of their own " | ||
+ | different notions of what are the most " | ||
+ | These four categories are MAS science, MAS education, MAS application, | ||
+ | use. The most critical infrastructure needs are not the same across these focus areas. There is a table which compares | ||
+ | the requisites for each category. | ||
+ | |||
+ | System Elements | ||
+ | * Communication Languages: [[http:// | ||
+ | * Components (content and processes): libraries | ||
+ | * Design Methodologies: | ||
+ | * Experimental Platforms: for developing and testing | ||
+ | * IDEs: for construction, | ||
+ | * Implementation Frameworks: templates that can be filled in with MAS codes and data | ||
+ | Capabilities | ||
+ | * Data Collection: messages, execution, behaviour, tasks | ||
+ | * Experiment Construction: | ||
+ | * Information Exchange: reports, source code | ||
+ | * Intentional Failure: the same as Sichmann | ||
+ | * Representation of MAS Concepts/ | ||
+ | * Simulaton: repeatable, realtime control/ | ||
+ | * Transfer: unplug atents and attach them to other systems or environments | ||
+ | Attributes (of Elements/ | ||
+ | * Illustrativeness: | ||
+ | * Openness: heterogeneous agents (architecture, | ||
+ | * Packaging: self-contained package | ||
+ | * Progressive Complexity: illustrate important principiles | ||
+ | * Robustness: failure tolerance | ||
+ | * Scalability: | ||
+ | * Support: party responsible for modifications, | ||
+ | * Usability: correspondence between skills, knowlegde, context of users and the tool | ||
+ | * Visibility: visualize process, interactions and architectures | ||
+ | Other | ||
+ | * Community | ||
+ | * Open Source Projects | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ====Principles and Concepts of Agent-Based Modelling for Developing Geospatial Simulations==== | ||
+ | |C. J. E. Castle, A. T. Crooks, 2006| [[http:// | ||
\\ | \\ | ||
- | // | + | **Abstract: |
+ | Modelling (ABM) paradigm, with particular reference | ||
+ | simulations. | ||
+ | classification of model types, | ||
+ | towards modelling systems at the individual-level. In particular, automata approaches (e.g. | ||
+ | Cellular Automata, CA, and ABM) have been particularly popular, with ABM moving to the | ||
+ | fore. A definition of agents and agent-based models | ||
+ | and disadvantages, | ||
+ | models is discussed, | ||
+ | provided. Types of simulation / modelling systems available for ABM are defined, | ||
+ | supplemented with criteria | ||
+ | endeavour. Information pertaining to a selection of simulation / modelling systems (Swarm, | ||
+ | MASON, Repast, StarLogo, NetLogo, OBEUS, AgentSheets | ||
+ | categorised by their licensing policy (open source, shareware / freeware | ||
+ | systems). The evaluation (i.e. verification, calibration, validation | ||
+ | models | ||
+ | GIS are a particularly useful medium for representing | ||
+ | model input and output | ||
+ | modelling (e.g. ABM). In particular, problems | ||
+ | are highlighted. | ||
+ | coupling or integration / embedding) a GIS with a simulation / modelling system purposely | ||
+ | built, | ||
+ | concludes with a synthesis of the discussion that has proceeded. | ||
+ | \\ | ||
- | ====Environments for Multiagent Systems, State-of-the-Art and Research Challenges==== | + | [...] GIS are not well suited to dynamic modelling (Goodchild, 2005; Maguire, 2005). |
- | |D. Weyns, H. V. D. Parunak, F. Michel, T. Holvoet and J. Ferber, 2005| [[http:// | + | |
- | (some interesting papers cite this one): " | + | Advantages over traditional techniques: |
+ | - captures emergent phenomena; | ||
+ | - provides a natural environment for the study of certain | ||
+ | - is flexible, particularly | ||
- | //It is generally accepted that the environment | + | There is a description of MAS, its advantages and disadvantages with details. |
- | Opportunities that environments offer, have mostly been researched | + | |
- | In this paper, we first give an overview | + | the agent-based approach to modelling |
+ | geospatial modelling. [...] Agent mobility makes ABM very flexible in terms of potential | ||
+ | variables and parameters that can be specified. Neighbourhoods can also be specified using a | ||
+ | variety of mechanisms. The implementation of agent interactions can easily be governed by | ||
+ | space, networks, or a combination of structures. | ||
+ | |||
+ | [ABM] remains an art more than a science | ||
+ | |||
+ | By their very definition, agent-based models consider systems at a disaggregated level. This | ||
+ | level of detail involves | ||
+ | and their interaction with an environment. The only way to treat this type of problem in | ||
+ | agent computing | ||
+ | parameters in order to assess the robustness of results (Axtell, 2000). | ||
+ | |||
+ | General requisites for MAS applications are the same as proposed by [[http:// | ||
+ | |||
+ | Open source is particularly useful for verifying | ||
+ | unexpected outcomes are a reflection of a mistake in the computer programme (a ‘bug’), | ||
+ | logical errors | ||
+ | |||
+ | |||
+ | ====Agent-based Simulation Platforms: Review and Development Recommendations==== | ||
+ | |S. F. Railsback, S. L. Lytinen, S. K. Jackson, 2006| Simulation| [[http:// | ||
+ | \\ | ||
+ | |||
+ | **Abstract: | ||
+ | each. NetLogo is the highest-level platform, | ||
+ | interfaces, and comprehensive documentation. It is designed primarily for ABMs of mobile | ||
+ | interactions in a grid space, but not necessarily clumsy for others. NetLogo is highly recommended, even for prototyping | ||
+ | complex | ||
+ | organizing and designing ABMs and corresponding software libraries. MASON is least mature and designed with execution | ||
+ | speed a high priority. The Objective-C version | ||
+ | organized. Objective-C seems more natural than Java for ABMs but weak error-handling and the lack of developer tools are | ||
+ | drawbacks. Java Swarm allows | ||
+ | of the two languages well. Repast provides Swarm-like | ||
+ | of its organization and design could be improved. A rough comparison of execution speed found MASON and Repast usually | ||
+ | fastest (MASON 1-35% faster than Repast), Swarm (including Objective-C) fastest for simple models but slowest for complex | ||
+ | ones, and NetLogo intermediate. Recommendations include completing the documentation (for all platforms except NetLogo), | ||
+ | strengthening conceptual frameworks, providing better tools for statistical output and automating simulation experiments, | ||
+ | simplifying common tasks, and researching technologies for understanding how simulation results arise. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | Our focus is primarily | ||
+ | There is a table comparing the terminology | ||
+ | |||
+ | ^ Version | ||
+ | | 1 |100 agents randomly in a | ||
+ | | 2 |A second bug action: growing | ||
+ | | 3 |Habitat cells that grow food; bug growth is equal to the food they consume from their cell. | Yes - Local automata| | ||
+ | | 4 |“Probes” letting the user see the instance variables of selected cells and bugs. | No graphics | | ||
+ | | 5 |Parameter displays letting | ||
+ | | 6 |A histogram of bug sizes. | ||
+ | | 7 |A stopping rule that causes execution to end when any bug reaches a size of 1000. | No | | ||
+ | | 8 |File output of the minimum, mean, and maximum | ||
+ | | 9 |Randomization | ||
+ | |10 |Size-ordering of execution order: bugs move in | ||
+ | |11 |Optimal movement: bugs move to the cell within | ||
+ | |12 |Mortality and reproduction: | ||
+ | |13 |A graph of the number of bugs. | No graphics | | ||
+ | |14 |Initial bug sizes drawn from a random normal distribution. | ||
+ | |15 |Cell food production rates read from an input file; | ||
+ | |16 |A second “species”: | ||
+ | |17 | Support for simulation experiments | ||
+ | |||
+ | Simulation experiments such as sensitivity and uncertainty analyses require multiple model runs, | ||
+ | including (i) “scenarios” varying inputs such as parameter values and (ii) “replicates”, | ||
+ | number generator seed. | ||
+ | |||
+ | __TerraME: | ||
+ | |||
+ | __TerraME: | ||
+ | |||
+ | __TerraME: | ||
+ | argument to another function, because it is just candy for agent.function(agent), | ||
+ | function call... | ||
+ | |||
+ | Key issues | ||
+ | * **The framework and library paradigm is good - but the framework is important**: Compared to Swarm, Repast and MASON seem more like libraries and less like frameworks, which makes the transition from ideas to working simulator more difficult. They allow models to be organized in a Swarm-like framework, but their documentation and teaching materials do not emphasize the conceptual aspects of model design. | ||
+ | * **Platform complexity is a major concern**: this complexity is intimidating | ||
+ | * Lack of a clear philosophy and decision process | ||
+ | * Software not in well-organized packages or libraries. | ||
+ | * Lack of complete documentation. Users should not have to read source code to get a basic idea of how a platform’s methods work. | ||
+ | * Failure to use common design patterns widely. For example, only Swarm’s classes for collections of objects (lists, arrays, maps) are designed so that any class operating | ||
+ | * **IDEs such as Eclipse are very useful** | ||
+ | * **Scientific modelers need scientific tools**: models need scientific analysis (statistics) | ||
+ | * **Understanding causality is an unfulfilled need**: tools for help understanding what is happening in the model | ||
+ | |||
+ | Some recommendations: | ||
+ | * **documentation of classes and methods** | ||
+ | * continual development of how-to and template models | ||
+ | * revive the “framework” part of the platform: establish the software library as one part of an overall process leading modelers through the model design, | ||
+ | * powerful tools for setting up and executing simulation experiments | ||
+ | * **ways to improve the trade-off between ease of use and generality of platforms** | ||
+ | * **research technologies for testing, analyzing, and understanding ABMs** | ||
Linha 131: | Linha 316: | ||
\\ | \\ | ||
- | //The range of tools designed to help build agent-based models is briefly reviewed. It is suggested that although progress has been made, | + | **Abstract: |
there is much further design and development work to be done. Modelers have an important part to play, because the creation of tools | there is much further design and development work to be done. Modelers have an important part to play, because the creation of tools | ||
- | and models using those tools proceed in a dialectical relationship.// | + | and models using those tools proceed in a dialectical relationship. |
+ | |||
+ | \\ | ||
The authors compare the standardization that occurred in statistical packages to the development of ABM, | The authors compare the standardization that occurred in statistical packages to the development of ABM, | ||
Linha 146: | Linha 333: | ||
- | ====Agent-based modeling: A revolution?==== | + | |
- | |S. C. Bankes, 2002|PNAS|[[http:// | + | |
+ | ====The RETSINA MAS Infrastructure==== | ||
+ | |K. Sycara, M. Paolucci, M. V. Velsen and J. Giampapa, 2003| Autonomous Agents and Multi-Agent Systems|[[http:// | ||
\\ | \\ | ||
- | //A clear consensus among the papers | + | **Abstract: |
- | However, the reasons to expect | + | |
- | anticipated revolution | + | \\ |
- | session.// | + | |
+ | One element that we articulate is the relation between infrastructure for a single agent and the infrastructure for the MAS | ||
+ | in which the agent participates. We consider MAS infrastructure to be the domain independent and reusable substratum on which MAS systems, services, components, live, | ||
+ | communicate, | ||
+ | |||
+ | [The infrastructure is clearly for modelling agents in different machines, but we can use the same concepts for simulating.] | ||
+ | Some of the layers presented are (the complete list is [[http://leg.ufpr.br/ | ||
+ | - ACL (Agents Communication Language): it enables agents to be implemented | ||
+ | - Mapping names to agent locations | ||
+ | - Performance measurement | ||
+ | - Locating agents by capability | ||
+ | |||
+ | When an agent first comes up in an open environment, | ||
+ | Instead of having hardwired IP addresses for such services, the MAS infrastructure | ||
+ | and the corresponding single agent infrastructure can facilitate the discovery of existing registered agents. | ||
+ | |||
+ | __TerraME: | ||
+ | to a tag, that can store the " | ||
+ | this tag. | ||
+ | |||
+ | This information | ||
+ | When an agent needs another | ||
+ | request specifying the desired capability. The middle agent matches requests and | ||
+ | advertisements. In general, there could be a variety of middle agents that exhibit different | ||
+ | matching behaviors. we have identified 28 middle agent types and have experimented with different performance | ||
+ | characteristics. | ||
+ | |||
+ | __Discussion: | ||
+ | |||
+ | **Open systems** allow agents to enter, and exit, the system dynamically and unpredictably, | ||
+ | employ a fixed set of agents that are known a priori. In closed MAS each agent knows the name, location and capability | ||
+ | of the others. Thus agent interactions can be statically predefined. This makes agent design and construction | ||
+ | simple, but makes the MAS brittle and not extensible. | ||
+ | |||
+ | |||
+ | |||
+ | ====Modelling social action for AI agents==== | ||
+ | |C. Castelfranchi, | ||
+ | |||
+ | |||
+ | |||
+ | =====TODO===== | ||
+ | |||
+ | ====Computational Laboratories for Spatial Agent-Based Models==== | ||
+ | |C. Dibble, 2006| [[http:// | ||
+ | \\ | ||
+ | |||
+ | **Abstract: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
+ | ====Environments for Multiagent Systems, State-of-the-Art and Research Challenges==== | ||
+ | |D. Weyns, H. V. D. Parunak, F. Michel, T. Holvoet and J. Ferber, 2005| [[http:// | ||
+ | |||
+ | (some interesting papers cite this one): " | ||
+ | |||
+ | **Abstract: | ||
+ | Opportunities that environments offer, have mostly been researched | ||
+ | In this paper, we first give an overview of the state-of-the-art on environments in MASs. The survey discusses relevant research tracks on environments that have been explored so far. Each track is illustrated with a number of representative contributions by the research community. Based on this study and the results of our own research, we identify a set of core concerns | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | ====Exception Handling in Agent Systems==== | ||
+ | |M Klein, 1999| Third International Conference on Autonomous Agents| | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ====Semantic Interoperability in Global Information Systems==== | ||
+ | |A. Ouksel, A. Sheth (Eds.), 1999| Special Issue of ACM SIGMOD Record| | ||
+ | |||
+ | | ||
+ | |||
+ | |||
+ | ====Software engineering considerations for individual-based models==== | ||
+ | |Ropella, G. E. P., S. F. Railsback, and S. K. Jackson. 2002| Natural Resource Modeling| | ||
+ | |||
+ | \\ | ||
- | //to evaluate this proposed revolution, what matters is not the computer science advances that make ABM possible, but rather the social | + | understanding causality? |
- | science challenges that make it necessary.// | + | |
- | //Three generic reasons that make ABM important to social sciences:// | ||
- | - //**the unsuitability of competing modeling formalisms**: | ||
- | - //**agents as a natural ontology for many social problem**: provides a place to express the enormous amount of data and knowledge about the behavior, motivations, | ||
- | relationships of social agents, be they human individuals or institutions.// | ||
- | - // | ||
geopro/pedro/platforms.1184266420.txt.gz · Última modificação: 2007/07/12 18:53 por pedro