Platform configuration file
The provided configuration file is written in YAML (YAML Ain't Markup Language). It is important to note that YAML files are sensitive to correct indentation. Incorrect indentation can lead to an invalid file, which may cause issues when the launcher attempts to process the configuration.
To ensure that the configuration file remains valid and the launcher can start successfully, it is crucial to follow these guidelines:
# Platforms
platforms:
# First platform
- name: UAV1
description: First platform
channels:
- name: EO-IR
description: First channel
input:
name: EO/IR
description: EO/IR-1 camera
url: udp://227.1.1.1:30120?localaddr=127.0.0.1
outputs:
- name: EO/IR-1-OUT
description: EO/IR-1 output
url: udp://224.1.1.1:30120?localaddr=127.0.0.1
- name: Screen1
description: Screen 1
url: udp://224.1.1.2:30120
# Second platform
- name: UAV2
description: Second platform
channels:
- name: EO-IR
description: First channel
input:
name: EO/IR
description: EO/IR-1 camera
url: udp://227.1.1.2:30120?localaddr=127.0.0.1
outputs:
- name: EO/IR-2-OUT
description: EO/IR-2 output
url: udp://225.1.1.1:30120?localaddr=127.0.0.1
- name: Screen2
description: Screen 2
url: udp://225.1.1.2:30120
In the provided configuration file:
The file starts with the "platforms:" key, indicating that a list of platforms will follow. The platform (for example, a UAV) may have a number of sensors (like video channels, etc)
Each platform is represented as a dictionary denoted by a hyphen (-) followed by indentation. In this sample we have two independent platforms:
The first platform is named "UAV1". It has one sensor: "EO-IR".
Note that this is a sample YAML configuration file, and the actual behavior of the platform or the meaning of the configurations will depend on the system that processes this file.