/Dragonfly

Tool for Simulating Self-adaptiveDrone Behaviours

Primary LanguageJavaBSD 2-Clause "Simplified" LicenseBSD-2-Clause

Dragonfly

SEAMS 2019 artifact

Dragonfly simulates the self-adaptive drone's behaviour with and without a wrapper solution during its flight from a source to a target hospital.

Summary

This repository contains all resources from Dragonfly, submitted to Artifacts track at SEAMS 2019. It consists of an executable simulator for self-adaptive drones, its source code and a demonstration video. This text provides instructions on how to use the simulator.

As described in the camera ready paper in more details, the purpose of this artifact is to simulate a drone flight between two hospitals to delivery an organ payload. By using this simulation, it is possible to observe the differences between the behaviours of the original implementation of the drone and the drone with a wrapper solution developed using aspect-oriented programming.

The simulator is implemented in Java, uses the JavaFX technology for the Graphical User Interface, and AspectJ for aspect implementation and weaving.

Artifact structure

This repository contains the following items:

  • README.md - This text as Markdown.
  • LICENSE.md - BSD 2-Clause License.
  • index.html - This text as HTML.
  • DragonFly-Project/src/ - Source directory containing the SEAMS demo application code.
  • ExecuteApplication/ - Directory including Docker image and .JAR files for executing in Ubuntu and Windows, each one having its proper instructions to run.

Development requirements

To run the code you need a version of Java 8 in which JavaFX is packaged (or add this dependency manually). It is also necessary to add AspectJ as a dependency. To facilitate configuration, the following link contains the version of the dependencies used, and a video example of how to run DragonFly from the code in the Intellij IDE.

Link: https://drive.google.com/drive/folders/1Zs2ftZSutymb8AwVx3AYNbWYDZWmdn8o?usp=sharing

Requirements to run

The executable artifact is available in both a single JAR format and Docker images to run on Windows 10 or Ubuntu machines. Note that the artifact may run on other Windows and Linux versions, but it was not extensively tested in all operating systems.

Getting started

The easiest way to run the artifact is by running the .JAR file, since it only needs a Java Runtime Environment (JRE) installed to work. To run using Docker images, there are files named "Steps.txt" inside the "Docker" directory, which is located in "ExecuteApplication/Ubuntu" and also in "ExecuteApplication/Windows" directories. In this file, a step-by-step for configuring Docker to run the application using its container image is described.

Running the Simulator - Step-by-step

This section presents a step-by-step tutorial to use the artifact.

1) Setting up Environment

The first step of using the simulator is the environment construction. The available elements are:

  • River, which the drone should not land on;
  • Hospital, which can be set by the user as the Source and Target hospitals of the flight;
  • Antenna, which emits waves that cause a bad connection in the drones located in its adjacent blocks;
  • Drone, the main element that has its own properties, as described in the next steps.
  • Boat, a boat that can save drones that are about to execute a safety landing and carry them to their destination.
  • House, a graphic representation of a House.
  • Tree, a graphic representation of a Tree.

This simulator provides two options for setting the environment:

  • to create an environment from scratch, inserting each element one by one. For inserting an element, the user needs to select the button of the respective element, and click at the desired position on the grid.
  • to load the example environment used in the paper, the user can access "Menu -> SEAMS paper example".

2) Setting Drone Configuration

The next step consists of configuring the following drone properties:

  • Battery consumption per block: it sets the percentage of battery consumed when the selected drone moves from a block to an adjacent block.
  • Battery consumption per second: it sets the percentage of battery consumed per second while the selected drone is flying.
  • Initial battery: the initial percentage value for the selected drone.
  • Wrapper dropdown: The user selects the desired wrapper implementation, or selects the "None" option for executing with its original behavior.
  • Automatic checkbox: by checking this box, the user turns the automatic pilot feature of the drone on, so it will move independently following a minimal path algorithm. On the other hand, leaving the box unchecked implies that the user will pilot the drone manually.
  • Drone's Destination: by clicking the gear icon, the user can select on the environment the destination's position.

Controls for piloting drones manually:

  • R key: turn on/off the drone.
  • SPACEBAR key: drone takes off/lands.
  • W, A, S and D keys: drone moves up, left, down and right, respectively.

3) Starting the application

The final step consists of starting the execution of the application, by clicking the "Ready" button, which triggers the execution of each drone inserted in the environment simultaneously. The traces of each drone are printed in a text area, from which it is possible to verify the scenarios that the drones perform and the current status of their battery.

By clicking on the "Restart" button, the user restarts the execution, i.e., the initial position and initial battery of the drones are restored and the user can start a new simulation.

4) Wrappers

  • Wrapper1: address safe landing procedure by invoking actions like Move Aside and Keep Flying to prevent drone from landing on water.
  • Wrapper2: address bad connection situation by forcing the drone to glide for a while instead of automatically returning to home.
  • Wrapper3: implements the above two exceptional conditions at the same time.

License

This artifact is licensed under the BSD 2-Clause License; the artifact may not be used except in compliance with the License. Conditions to redistribute and use this artifact in source and binary forms, with or without modification, are detailed in LICENSE.md file.

Contact

If you have any problem to use the artifact, please do not hesitate to contact us by sending an email to dragonfly.seams2019@gmail.com, pauloh.maia@uece.br, lucas.vieira@aluno.uece.br or maths.c28@gmail.com.