Simulation Results

A simulation creates several output files where the results are stored. A new folder is created for the results within the data/output directory or the custom directory specified within config.yaml(folder name is the name of the scenario) in which all results will be stored. The following output files will be created during the process of the simulation:

File	Description	References
scenario.json	scenario file containing all simulation settings for reference
scenario.sp3	file containing satellite orbits (Standard Product 3)	SP3 File Format (opens new window)
scenario_N.YYn	RINEX 2.11/3.02 navigation file for each receiver and each GNSS system – N denotes receiver index	RINEX 3.02 (opens new window)
scenario_N.YYo	RINEX 2.11/3.02 observation file (mixed) for each receiver – N denotes receiver index	RINEX 3.02 (opens new window)
scenario_N.binx	GNSS metadata file for each receiver – N denotes receiver index	GNSS Metadata Standard (opens new window)
scenario_N.kml	KML (Google Earth® compatible output) file for each receiver – N denotes receiver index	see KML
scenario_N.pos	file containing simulated receiver positions for each receiver – N denotes receiver index	see Position File
scenario_N.sky	file containing skyplot data for each receiver – N denotes receiver index	see Skyplot File
scenario_N_X.bin	binary signal file containing simulated IF signal – N denotes receiver index and X denotes carrier frequency	see Signal File
scenario_N_X.lvl	level file containing information on signal level – N denotes receiver index and X denotes carrier frequency Note: a .lvl file is only generated if the Hardware Profile is set accordingly	see Level File
scenario_N_X.facq	fake acquisition file containing acquisition information for each receiver – N denotes receiver index and X denotes carrier frequency	see Fake Acquisition File
scenario_XX.yuma	almanac file containing almanac information for each GNSS type – XX denotes the GNSS type	Yuma File Definition (opens new window)
scenario.spf	file containing information on simulated spoofing signals	see Spoofer File
scenario_fictional-M.spfp	spoofer power file containing received spoofing power for each receiver – M denotes the spoofer index	see Spoofer Power File