Configuration (METRo)
From Documentation
This article describe the configuration file of METRo.
Contents |
[edit] Description
This file is optionnal and contains configuration to run METRo. It contains the arguments that are usually written on the command prompt. If there is no argument on the command line for an option, the value used for this option is taken in this file if it is given with the option --config.
A default configuration file can be created by using the command:
python metro.py --generate-config metroconf.xml
[edit] Version and revision date
- Version: 1.0
- Revision date: November 15th 2004
[edit] Default location
No default location. Configuration filepath must be specified on command line.
[edit] Contents
We will find fields that must be configurated at METRo's launching but without link with the configuration station file. As examples: the date of the roadcast start, the modules of pre-process and of post-process that have to be activated.
[edit] Mandatory fields
All fields are optional. They all have a hard-coded default value. This file will be created if it doesn't already exist.
[edit] Example
<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
<key>DATA_ATTRIBUTE_FORECAST_EXTENDED</key>
<array>
</array>
<key>DATA_ATTRIBUTE_OBSERVATION_EXTENDED</key>
<array>
</array>
<key>DEFAULT_FORECAST_HEADER_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_FORECAST_PREDICTION_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_OBSERVATION_HEADER_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_OBSERVATION_MEASURE_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_ROADCAST_HEADER_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_ROADCAST_PREDICTION_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_STATION_HEADER_TIMEZONE</key>
<string>UTC</string>
<key>DEFAULT_STATION_ROADLAYER_TYPE</key>
<string>ASPHALT</string>
<key>FILE_FORECAST_IN_FILENAME</key>
<string>../../data/forecast/forecast.xml</string>
<key>FILE_FORECAST_OUT_FILENAME</key>
<string>forecast_out.xml</string>
<key>FILE_LOGGER_FILENAME</key>
<string>log_metro</string>
<key>FILE_OBSERVATION_FILENAME</key>
<string>../../data/observation/observation.xml</string>
<key>FILE_ROADCAST_FILENAME</key>
<string>roadcast.xml</string>
<key>FILE_STATION_FILENAME</key>
<string>../../data/station/station.xml</string>
<key>INIT_LOGGER_SHELL_DISPLAY</key>
<true/>
<key>INIT_LOGGER_VERBOSE_LEVEL</key>
<integer>5</integer>
<key>INIT_MODULE_EXECUTION_SEQUENCE</key>
<array>
<string>metro_read_forecast</string>
<string>metro_string2dom_forecast</string>
<string>metro_read_observation</string>
<string>metro_string2dom_observation</string>
<string>metro_read_station</string>
<string>metro_string2dom_station</string>
<string>metro_dom2metro</string>
<string>metro_preprocess_interpol_forecast</string>
<string>metro_preprocess_fsint2</string>
<string>metro_preprocess_qa_qc_observation</string>
<string>metro_preprocess_interpol_observation</string>
<string>metro_preprocess_combine</string>
<string>metro_model</string>
<string>metro_metro2dom</string>
<string>metro_write_roadcast</string>
<string>metro_write_forecast</string>
</array>
<key>INIT_XML_LIB</key>
<string>metro_xml_libxml2</string>
<key>XML_DATATYPE_EXTENDED</key>
<dict>
</dict>
<key>XML_FORECAST_HEADER_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_FORECAST_PREDICTION_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_OBSERVATION_HEADER_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_OBSERVATION_MEASURE_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_ROADCAST_HEADER_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_ROADCAST_PREDICTION_EXTENDED_ITEMS</key>
<array>
</array>
<key>XML_STATION_HEADER_EXTENDED_ITEMS</key>
<array>
</array>
</dict>
</plist>
| METRo I/O files |
| Station | Observation | Forecast | Roadcast | Configuration |
| METRo I/O specification |
| Schema | | Flowchart | Format | Date | Observation QA/QC | Road condition | Station type | Time zone | Layer type | Latitude and longitude |
| METRo I/O examples |
| Station | Observation | Forecast | Roadcast | Graphical display |
| This page is part of the documentation of the METRo software. Back to the table of content. |
