Home Esplora Aiuto
Registrati Accedi
vatger
/
aman-es
2
0
Forka 0
File Problemi 0 Pull Requests 0 Wiki

Nessuna descrizione

Ramo (Branch): feature/aircraftExport
Rami (Branch) Tag
aman-es
ZIP TAR.GZ
Sven Czarnian e19e50b027 update to the current interface version 2 anni fa
cmake 27b422d806 add Eigen as a dependency 2 anni fa
external 27b422d806 add Eigen as a dependency 2 anni fa
include d24c1ee1ce add a flag to indicate if the filter needs to be reset 2 anni fa
res 0035c97c20 introduce resource files 3 anni fa
src e19e50b027 update to the current interface version 2 anni fa
.gitmodules 57a4aae223 add aman-com as a submodule 3 anni fa
CMakeLists.txt 2a0dad3c7b update comments 3 anni fa
LICENSE 5f702016ad add the license of the project 3 anni fa
README.md 539987868c update the documentation 3 anni fa
version.h.in 52870429a6 add missing templates for the automated file generation 3 anni fa

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