output_README.md

Explaining output of example/stanford.py

Output Directory Structure

├── stanford
│   ├── mission.json
│   ├── mission_routes.png
│   ├── routes
│   ├── routes.png
│   └── wadl.log

mission.json

This file contains several parameters, broadly in the categories of version, payloadProfiles, vehicleProfiles, mission, and vehicles.

In this documentation, I will focus on vehicleProfiles, and mission.

The vechilesProfiles dictionary object stores information about the drone make, model, payload, and other miscellanious parameters concerning physical characteristics and limitations of the drone.

The mission dictionary object stores information the mission name, and information about each route produced by the solver. Each route has metadata, trajectory types, altitude information, fail safes, and segment information for the UAVs to follow.

mission_routes.png and routes.png

Visualizes the mission_routes from Mission() and routes generated from Survey()

routes/

Each .csv file in the routes/ folder is named as {name_of_starting_location}_{index}_{altBand}.csv

Each row corresponds to a keypoint (lat, long), altitude, speed, and other information about altitude and speed (although not sure in what order).

wadl.log

Logs information used for debugging the solver.