You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

The scenario/script database for the Water Coach is a directory containing an arbitrary number of scenarios/scripts. A scenario consists of a FEWS database (the so-called local data store) that contains measurement data and model data and one or more script directory. Each one of these script directories that uses the same scenario (i.e. the local data store). A script is the story line and consists of all events that happen during the game. Each subdirectory of the scenario directory that contains a file named script_config.xml is considered a script and will automatically appear in the list of scripts that can be selected by the user of the Water Coach. The following files/directories must be part of a scenario/script directory:

  • A scenario directory must contain a directory named localDataStore which holds the pre-loaded FEWS database. When a scenario/script is started in the Water Coach, this directory is copied to the FEWS region directory.
  • A scenario directory must contain one or more script directories.
  • A script directory must contain a script configuration file named script_config.xml.
  • A script directory may contain an arbitrary number of files that are associated with events specified in the script configuration.

The Water Coach adds a log-directory with log-files to the script directory that was chosen by the user. A log-file is created for each scenario/script that is played and is added (with a time stamp) to the appropriate directory in the scenario/script database.

Below is an example of a database containing two scenarios. One scenario contains two scripts, the other scenario contains one script.

ScenarioScriptDatabase
|-- storm surge March 10-13
|   |-- localDataStore
|   |   `-- local.fdb
|   |-- novice
|   |   |-- script_config.xml
|   |   |-- exercise1_EN.txt
|   |   |-- exercise1_NL.txt
|   |   |-- start_session_EN.txt
|   |   |-- start_session_NL.txt
|   |   |-- telephone_call_EN.txt
|   |   |-- telephone_call_NL.txt
|   |   |-- weather_map_March12_00hr.pdf
|   |   |-- weather_map_March12_12hr.pdf
|   |   `-- weather_map_March13_00hr.pdf
|   |-- advanced
|   |   |-- script_config.xml
|   |   |-- telephone_call.txt
|   |   `-- weather_map.pdf
`-- another storm surge
    |-- localDataStore
    |   `-- local.fdb
    |-- script1        |-- script_config.xml
        |-- file1.pdf
        `-- file2.pdf

It is also possible to group several scenarios/scripts (that belong to different FEWS configurations for example) by using an extra directory level, i.e.

ScenarioScriptDatabase
|-- Sea
|   |-- scenario1
|   |   |-- script1
|   |   |   `-- script_config.xml
|   |   `-- script2
|   |       `-- script_config.xml
|   `-- scenario2
|       `-- script1
|           `-- script_config.xml
`-- River
    |-- scenario1
    |   `-- script1
    |       `-- script_config.xml
    `-- scenario2
        |-- script1
        |   `-- script_config.xml

        `-- script2
            `-- script_config.xml

In the application configuration, a reference to the appropriate scenario/script database can be set, for example ScenarioScriptDatabase/River.

FEWS Configuration

To minimize the size of the local datastore used for a game, one could seperate the import of maps and timeseries into seperate modules. This allows for a lower frequency for the import of maps. However, when this is apllied, an additional change should be made to the FEWS configuration (see also application configuration).

  • Incorporate the changes to the moduleInstanceId's for the seperate import of timeseries and maps in the FEWS configuration of the filters, spatial display, etc.
  • No labels

Disclaimer