Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section


Column
width45%

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

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.


Column


Code Block
ScenarioScriptDatabase
|-- Sea
|   |-- scenario1
|   |   |-- localDataStore
|   |   |   `-- local.fdb
|   |   |-- script1
|   |   |   `-- script_config.xml
|   |   `-- script2
|   |       `-- script_config.xml
|   `-- scenario2
|   |   |-- localDataStore
|   |   |   `-- local.fdb
|       `-- script1
|           `-- script_config.xml
`-- River
    |-- scenario1
|   |   |-- localDataStore
|   |   |   `-- local.fdb
    |   `-- script1
    |       `-- script_config.xml
    `-- scenario2
|   |   |-- localDataStore
|   |   |   `-- local.fdb
        |-- script1
        |   `-- script_config.xml
        `-- script2
            `-- script_config.xml



...