Data sample for Mercury simulator

Sample data to run Mercury Mercury is available at: https://github.com/UoW-ATM/Mercury This file contains a sample of input data for the open-source air mobility simulator Mercury. Please use use version 3 of the dataset for Mercury 3.0 and version X.Y.Z for Mercury X.Y. The dataset is structured as follows: input: Input folder for Mercury input/scenario=-1: Folder containing scenario -1 with about 1000 flights anonymised. input/scenario=-1/scenario_config.toml: Configuration file for the scenario input/scenario=-1/data: data provided is organised as follows: ac_performance: aircraft performance dataset. Requires BADA files (not provided, BADA files need to be structured inside provided folders (see Mercury Readme) airlines: static information on airlines used in the scenario airports: static information on airports, including capacity declarations and minimum turnaround time. Two subfolders included: taxi (with taxi-in and taxi-out times) and curfew (with curfew times) costs: data required to define cost functions delay: delay parameters (non-ATFM) eaman: definition of EAMAN in scenario (scope) flight_plans: information on the flight plans, contains: crco: not provided as not needed to run Mercury (used for FP generation) en_route_wind: not provided as not needed to run Mercury (used for FP generation) flight_plans_pool: pool of flight plans for o-d ac type triplets flight_uncertainty: distributions to model uncertainty on the realisation of the flight plans routes: routes available between o-d pairs (used only for HMI and for FP generation (not needed to run Mercury)) trajectories: trajectories available from o-d ac type triplets (used only for HMI and for FP generation (not needed to run Mercury)) network_manager: ATFM probabilities, distributions and definition pax: passenger itineraries for flights provided scenario: static information on scenario (to be deprecated in subsequent updates) schedules: flight schedules provided (note these will determine which airports, flight plans, etc. are provided in the dataset) input/scenario=-1/case_sdudies: folder to contain the definition of case studies case_study=0: default case study with the configuration file (case_study_config.toml)