OperaappConfigurationFile

To start, OPERA GUI needs to read a specific properties file named operaapp-configuration.properties. The logic to search for this file is the following one :

• first, OPERA will see if the file exists locally (i.e. at the same location where OPERA was launched)
• in case of no local file exists, OPERA will use the one included Inside the jar file.

Here is the content of this file :

OUTPUT_FILENAME operaAppRun-<Date>
OUTPUT_DATEFORMAT yyyy-MM-dd_HH-mm-ss

WORK_DIR OPERA_DATA/work
CONTEXT_PATH OPERA_DATA/context
RESULT_PATH OPERA_DATA/results
OUTPUT_PATH OPERA_DATA/outputrun
#BD_TLE_TREE FLAT
BD_TLE_TREE HIERARCHICAL
BD_TLE_PATH OPERA_DATA/tles
BD_TLE_BY_DAY_PATH OPERA_DATA/tlesbyday
ADDITIONAL_PATRIUS_DATA OPERA_DATA/AdditionalPatriusData
BD_TLE_SAT_CAT_PATH /satcat.csv
COUNTRIES_FILE_PATH /countries.csv
REAL_SOLAR_ACTIVITY_FILEPATH /solar/ACSOL_REAL.act
PREDICTED_SOLAR_ACTIVITY_FILEPATH /solar/ACSOL_PREDICTED.act

OPERA_CONFIGURATION /opera-configuration.properties
OPERA_CONFIGURATION_EDITORS /opera-configuration-editors.properties
OPERA_CONFIGURATION_EDITORS_ADVANCED /opera-configuration-editors-advanced.properties
OPERA_CONFIGURATION_EDITORS_REENTRY /opera-configuration-editors-reentry.properties
OPERA_CONFIGURATION_EDITORS_SM_ESTIMATION /opera-configuration-editors-estimationsm.properties
OPERA_CONFIGURATION_EDITORS_MANOEUVERS /opera-configuration-editors-manoeuvers.properties
OPERA_CONFIGURATION_EDITORS_REPORT /opera-configuration-editors-report.properties

Note: when a path starts by "/", it may mean that the file will be taken from the jar file.

Note: this properties file is automatically created, the first time the GUI is launched (to avoid to extract it later)