| ... | ... | @@ -41,81 +41,3 @@ Cassio Trindade <br> |
|
|
|
|
|
|
|
|
|
|
|
<p align="left"><img src="http://www.ages.pucrs.br/wp-content/uploads/2018/07/20180817_215540-1024x498.jpg?raw=true" alt="Nutritech" width="80%"/></p> |
|
|
|
|
|
|
|
|
|
|
|
**Notes:**
|
|
|
|
* Disaster Simulation System
|
|
|
|
* Interaction between the Agents and the Simulator.
|
|
|
|
* Agent it's a being that recognizes its location and can decide upon that information.
|
|
|
|
* The development of Agents isn't part of the scope.
|
|
|
|
* Our mission is to develop the Simulator so than the agents can use it
|
|
|
|
* There is no worry about which language the agents are made of.
|
|
|
|
* Multi-Agent Programing Contest - MAPC (simulator example)
|
|
|
|
* The Agents would be autonomous robots and humans.
|
|
|
|
* The simulation takes place in pre-defined steps.
|
|
|
|
* The Agents interact with the Simulator through a protocol.
|
|
|
|
* Stochastic simulation - chances of an event to happen.
|
|
|
|
* Graphic interface (part of a city)
|
|
|
|
* Generation of data - logs of data generated in the graphical interface (decoupling * of the graphical interface).
|
|
|
|
* Definitions: Perceptions, Actions, Events.
|
|
|
|
* Important:
|
|
|
|
* The simulation should be replicable;
|
|
|
|
* Simulation Report - output log;
|
|
|
|
* Documentation and code must be in English.
|
|
|
|
|
|
|
|
* AGENTS types (documentate characteristics):
|
|
|
|
- Fixed Agents:
|
|
|
|
* battery;
|
|
|
|
* velocity;
|
|
|
|
* physical storage;
|
|
|
|
* virtual storage (memory (photos));
|
|
|
|
* locomotion (water, road, air);
|
|
|
|
* dextery;
|
|
|
|
* resources (water catcher, camera).
|
|
|
|
|
|
|
|
|
|
|
|
- Variable agents (social assets) ⇒ do not start the simulation (they are called as volunteers):
|
|
|
|
* velocity;
|
|
|
|
* dextery (cooking);
|
|
|
|
* resources;
|
|
|
|
* energy (fatigue) -> can only help for a while.
|
|
|
|
|
|
|
|
|
|
|
|
- Actions of AGENTS (documentate)*:
|
|
|
|
* Locomotion (in which it must respect the environment, latitude and longitude - command center);
|
|
|
|
* Photographing (space check);
|
|
|
|
* Analyze photo (task: find victims - chance of finding a victim on a spot for photo analysis);
|
|
|
|
* Collect water samples (task: to collect - occupies physical space);
|
|
|
|
* Recharge battery;
|
|
|
|
* Deliver physical item;
|
|
|
|
* Deliver virtual item;
|
|
|
|
* Rescue Victim (if the agent can rescue after analyzing the photo - verify agent conditions);
|
|
|
|
* Search for social assets (search for volunteers within a specific radius - server will open a new connection and look for a new agent .. simulator expects another connection from another agent);
|
|
|
|
* Requesting Social Asset.
|
|
|
|
|
|
|
|
- Events - Floods (documentate features)*:
|
|
|
|
* Duration range
|
|
|
|
* Flood form (rectangle, circle)
|
|
|
|
- Related Events
|
|
|
|
- Photography
|
|
|
|
* Number of flood photography events
|
|
|
|
* Photo size (virtual space)
|
|
|
|
* Find a victim
|
|
|
|
* Chance of a photograph to have related victims
|
|
|
|
- Wather Sample
|
|
|
|
* Number of water collection events by flood
|
|
|
|
* Sample size (physical space)
|
|
|
|
|
|
|
|
- Victims (generate, but still hidden) (within the flood area)
|
|
|
|
* Chance of a victim arising with location revealed during flood
|
|
|
|
* Number of victims per event
|
|
|
|
* Weight of the victim
|
|
|
|
* Lifetime
|
|
|
|
|
|
|
|
Technologies:
|
|
|
|
|
|
|
|
- python 3.6
|
|
|
|
- pyroute
|
|
|
|
- flask-IO
|
|
|
|
|
|
|
|
|
