Versions Compared

Old Version 33

changes.mady.by.user Simone De Kleermaeker

Saved on

compared with

New Version 34

changes.mady.by.user Simone De Kleermaeker

Saved on

Key

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

...

Section


Column
width45%

SSD folder structure for different (older) versions of a Delft-FEWS application (aka WaterCoach meta-application)

If different (older) WaterCoach scenarios are associated with different (older) configuration and/or modules, the corresponding Config folder and/or Modules folder can be placed in the WaterCoach scenario folders as well.

The user experience is the same as before, but under the hood more things happen. After selecting a scenario and script, Delft-FEWS will restart as always, but will now not only copy the LDS, but also unzip and replace the Config (and Modules) folder in the $REGION_HOME$

To let WaterCoach Meta-application work correctly, please follow these rules:

  • use only the names Config.zip, and Modules.zip,
  • if any scenario contains a Config.zip, all scenarios need to contain a Config.zip,
  • if any scenario contains a Modules.zip, all scenarios need to contain a Modules.zip,
  • WaterCoachDisplay.xml: set copyLocalDataStore=true for all Config.zip versions
  • when the global.properties are not the same for all, place them in the RootConfigFiles folder, and use the same name for all global properties files (including your stand alone application which is started by the user).


Column


Code Block
titleSSD including different (older) versions of the Config and Modules folder
ScenarioScriptDatabase
|-- scenario1
|   |-- localDataStore
|   |   `-- local.fdb
|   |-- script1
|   |   |-- script_config.xml
|   | -- Config.zip
|   | -- Modules.zip
`-- scenario2
    |-- localDataStore
    |   `-- local.fdb
    |-- script1
        |-- script_config.xml

|   | -- Config.zip
|   | -- Modules.zip




Section


Column
width45%

SSD folder structure for multiple Delft-FEWS applications

It is also possible to group several scenarios/scripts (that belong to different Delft-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.

Minimize size of LDS through changes to Delft-FEWS config

To minimize the size of the localDataStore, one could separate the import of maps and timeseries into separate modules. This allows for a lower frequency for the import of maps. However, when this is applied, an additional change should be made to the Delft-FEWS configuration (see also application configuration). Also make sure to incorporate the changes to the moduleInstanceId's for the separate import of timeseries and maps in the Delft-FEWS configuration of the filters, spatial display, etc.


Column


Code Block
titleSSD for multiple Delft-FEWS applications
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



...