Changes between Version 14 and Version 15 of SIMEO
- Timestamp:
- Jan 17, 2010, 7:29:31 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SIMEO
v14 v15 21 21 The goal of SIMEO is to offer a generic framework designed to facilitate the study of interactions between large numbers of agents in a simulated virtual world. 22 22 The environment of this virtual world is composed of many objects that may execute different physical interactions between themselves, with the control of an agent. 23 An agent monitors the environment through sensors and applies impulses in the world through actuators. In order to reach the ability of self-organization, agents should also be able to communicate with each others directly, through messages. 23 An agent monitors the environment through sensors and applies impulses in the world through actuators. Our aim to create a framework with large applicability that can have a major impact in the study of emergent and self-organization systems. In order to reach the ability of self-organization, agents should also be able to communicate with each others directly, through messages. 24 24 25 25 26 == Framework specifications == … … 27 28 1 Define system components: 28 29 29 30 The system's architecture is inspired from the standards provided by FIPA (Foundation for Intelligent Physical Agents) from which are inspired many of the current agents platforms. 30 31 We present below the components proposed for our system and a brief description: 31 32 … … 72 73 Agents provide support for Sensors, Actuators and Communication Channels and can be implemented both in C++ and Java. 73 74 75 The framework is developed on top of Bullet, a professional open source physics engine. It's main task is to perform collision detection, resolve collisions and other constraints and provide the updated world transform for all the objects in the simulation. 76 77 Bullet has been designed to be customizable and modular. The developer can 78 79 * use only the collision detection component 80 81 * use the rigid body dynamics component without soft body dynamics component 82 83 * use only small parts of a the library and extend the library in many ways 84 85 * choose to use a single precision or double precision version of the library 86 87 * use a custom memory allocator, hook up own performance profiler or debug drawer 88 89 The main components are organized as follows: 90 91 92 93 74 94 == Testing == 75 95