Accueil Explorer Aide
S'inscrire Connexion
vatger
/
aman-es
2
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki

Aucune description

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

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