mirror of https://github.com/AdaCore/OpenUxAS.git synced 2026-02-12 13:07:16 -08:00

Files

M. Anthony Aiello 04b71a337d Feature/create run example (#40 )

* Intermediate progress

* Update run-example

Delaying while OpenAMASE opens appears to be important. It takes a while for OpenAMASE to actually open, and the user is supposed to click on the run button before OpenUxAS instances start. The five seconds offered by some examples is insufficient, and may not be guaranteed in any case.

We make the delay configurable, so that the user can remove or adjust it, as needed.

We also make sure that we kill off forked subprocesses and report if we're unable to do so.

* Rename the Ada Waterway Search example

Suggesting this naming convention so that we can create other examples that use the Ada UxAS more easily.

* Add two additional configs

Configs for Examples 03 and 05

* Update config for example 03

This should work out of the box on modern Linux.

* Add config-driven delay after OpenAMASE starts

This is important for the Ada example, although it may be related to the way in which we implemented it.

* Enhance run-example

- Fix error when OpenAMASE does not run
- Handle Ctrl-C gracefully (shut down all subprocesses)
- Allow a relative or absolute path to the example to be specified - this is nice, because then tab-complete works

* Add missing example configs

Also make sure that each ends with a newline (nice for `cat`).

* Use Test_SimulationTime service to sync with AMASE

Removes the need for any timeout to start UxAS instances.

* Fix example 05_AssignTasks

Adding the Test_SimulationTime service + a longer timeout on task assignment allows the example to run correctly.

2020-05-14 13:49:06 -04:00

MessagesToSend

renamed tasks folder to 99_Tasks

2018-10-01 12:38:42 -04:00

cfg_LoiterTask.xml

renamed tasks folder to 99_Tasks

2018-10-01 12:38:42 -04:00

config.yaml

Feature/create run example (#40 )

2020-05-14 13:49:06 -04:00

README.md

renamed tasks folder to 99_Tasks

2018-10-01 12:38:42 -04:00

runAMASE_LoiterTask.py

AMASE scripts point to config files in 99_Tasks folder

2018-10-15 10:29:20 -04:00

runUxAS_LoiterTask.py

renamed tasks folder to 99_Tasks

2018-10-01 12:38:42 -04:00

Scenario_LoiterTask.xml

renamed tasks folder to 99_Tasks

2018-10-01 12:38:42 -04:00

README.md

Loiter Task

An task where a vehicle loiters around a point.

Files:

cfg_LoiterTask.xml - The UxAS configuration file for this example. This configuration file sets up the services and bridges.
runUxAS_LoiterTask.py - This script runs UxAS with the details in the UxAS configuration file
runAMASE_LoiterTask.py - This script runs AMASE with the AMASE configuration file.
Scenario_LoiterTask.xml - The AMASE configuration file for this example.
MessagesToSend/ - Contains the messages sent by UxAS with the send messages service.
MessagesToSend/AirVehicleConfiguration_V101.xml - Details for air vehicle 101.
MessagesToSend/AirVehicleState_V101.xml - Air vehicle 101's initial state.
MessagesToSend/LoiterTask_100.xml - The loiter task that is requested.
MessagesToSend/AutomationRequest_LoiterTask.xml - The automation request for the loiter task.

Running the example:

Open a terminal window in the directory: "examples/tasks/LoiterTask"
enter the command python3 runUxAS_LoiterTask.py or ./runUxAS_LoiterTask.py
open another terminal window in the directory: "examples/tasks/LoiterTask"
enter the command python3 runAMASE_LoiterTask.py or ./runAMASE_LoiterTask.py
start the AMASE simulation (i.e. press the play button)

What happens?

When the AMASE simulation starts, vehicle 101 will be initialized and begin flying east.
After 4 seconds, an automation request for the loiter task is sent.
Once plans have been calculated, vehicle 101 will being performing the loiter task.