Home Explore Help
Register Sign In
vatger
/
aman-es
2
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki

No Description

Tree: 272fb3aab0
Branches Tags
aman-es
ZIP TAR.GZ
Sven Czarnian 272fb3aab0 add the communication file format 3 years ago
cmake 557c781fa6 add GSL as a development dependency 3 years ago
external 557c781fa6 add GSL as a development dependency 3 years ago
include 272fb3aab0 add the communication file format 3 years ago
res 0035c97c20 introduce resource files 3 years ago
src 272fb3aab0 add the communication file format 3 years ago
CMakeLists.txt 2a0dad3c7b update comments 3 years ago
LICENSE 5f702016ad add the license of the project 3 years ago
README.md 539987868c update the documentation 3 years ago
version.h.in 52870429a6 add missing templates for the automated file generation 3 years ago

README.md

Arrival MANanager (AMAN)

System description

AMAN is splitted up into four different components.

  • aman-com defines the diffent message types
  • aman-es implements an EuroScope plugin to communicate with aman-sys
  • aman-sys implements the backend system to plan an optimal arrival sequence for the different airports
  • aman-web implements a web-interface to configure aman-sys and visualize sequences

Component description

AMAN uses Protocol Buffers for the message serialization and message definition between the EuroScope instance and the AMAN backend.

Additionally is ZeroMQ used for the communication abstraction layer.

This component extracts all relevant information out of the VATSIM network and sends the information to the server. Additionally is a unique identifier used to verify connections to the backend. According to data protection is the ZeroMQ-based network encryption used. Every controller needs his own unique identifier.

Additional libraries

License

AMAN is released under the GNU General Public License v3