Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Desastres
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Desastres
  • Desastres
  • Wiki
  • notes

notes · Changes

Page history
gabriel.paul created page: notes authored Nov 16, 2018 by Gabriel Henrique Paul's avatar Gabriel Henrique Paul
Hide whitespace changes
Inline Side-by-side
notes.md 0 → 100644
View page @ 48c84eb6
**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
Clone repository
  • API
  • QuickStart
  • agents
  • agents
    • actions
    • agent
  • api
    • firstconnection
    • firstmessage
    • how it works
    • stepsmessages
  • Home
  • notes
  • requirements
  • setting enviroment
  • simulation
  • simulation
    • corearchitecture
View All Pages