Page History

...

By default the General Adapter runs are performed in the %TMP% directory. You can force a different directory by defining the %tempDir% variable that overrules the %TMP% environment variable in the global.properties%TEMP_DIR% directory.

Configuration

By default Delft-FEWS will only use one core and all tasks are run one after another. To enable the parallel running of ensemble members the runInLoopParallelProcessorCount entry must be set in the global properties file. Here you either specify the number of cores to use or specify 100 to use all available cores.

...

# to use all available cores/cpu's:
runInLoopParallelProcessorCount=100
tempDir=d:/temp

For all internal Delft-FEWS modules that have been tested no changes are needed to the configuration. For external modules that are run using the General adapter some changes may be needed to the configuration.

...

runInLoopParallelProcessorCount=2
tempDir=d:/temp

This makes that maximum 2 threads are used and the Sobek runs are performed in temporary directories that are created in the tempdir. Per ensemble member a subdirectory is created where the name is defined as %tempdir%\<region><moduleInstance><EnsembleId><EnsembleMemberIndex><threadId>, e.g. d:\temp\TestRegion_Sobek_GA_EPS_1_4438868285134166498regionhome/temp/session. These directories are removed after running. The directories are filled with data that you should export from a moduledataset. Notice that purgeActivities will not work therefore. When running in debug mode the temp is deleted when closing FEWS instead when the run is finished

In a test using 2 CPU the total run of the whole ensemble reduced from exactly 900 seconds to 546 seconds.

Internal variables

You can use in any filename or directory the properties from the global.properties file or the next internal variables:

...