Ingen beskrivning

Sven Czarnian 1bb9813a7a allow to add flights as forced for AMAN to include them, if the neighboring controller is not using AMAN 3 år sedan
cmake a23de5ee67 add required libraries 3 år sedan
external a23de5ee67 add required libraries 3 år sedan
include 689c2326c2 use only one backend and adapt to the new communication structure 3 år sedan
res 0035c97c20 introduce resource files 3 år sedan
src 1bb9813a7a allow to add flights as forced for AMAN to include them, if the neighboring controller is not using AMAN 3 år sedan
.gitmodules 57a4aae223 add aman-com as a submodule 3 år sedan
CMakeLists.txt 2a0dad3c7b update comments 3 år sedan
LICENSE 5f702016ad add the license of the project 3 år sedan
README.md 539987868c update the documentation 3 år sedan
version.h.in 52870429a6 add missing templates for the automated file generation 3 år sedan

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