Set-up environment
To set-up a traning environment for the FEWS application ConfigCourse_WC
, you have to take the following steps:
- Create a FEWS_WaterCoach folder
- Add a stand alone copy of the operational
ConfigCourse_WC
system (a few changes are necessary) - Add a FEWS
bin
folder (this can be a copy of the operational FEWS version, but also a newer version with new functionality you want to train)- Add the
ConfigCourse_WC.exe
andConfigCourse_WC.jpif
file to start the ConfigCourse_WC system (copy these files from the bin folder of the operational system and modify the region dir in the .jpif file)
- Add the
- Add a
jre
folder (copy of the jre folder in the operational FEWS system)
- Add a stand alone copy of the operational
- Create a
WaterCoach
folder- Add the application_config.xml. You can rename this file to (e.g.)
ConfigCourse_WC.xml
- Add an
ConfigCourse_WC.exe
andConfigCourse_WC.jpif
file to start the WaterCoach
- Add the application_config.xml. You can rename this file to (e.g.)
- Create the folder
ScenarioScriptDatabase
- Add a folder
ConfigCourse_WC
for the system- Add a folder
Demo
for the (first) scenario- Add the
localDataStore
for this scenario (copy of the localDataStore folder from the operational system) - Add a folder
Demo_script
for the (first) script for this specific scenario- Add the script configuration
script_config.xml
- Add the script configuration
- Add the
- Add a folder
- Add a folder
application_config.xml
Create the application config xml file, you can use this example
You can rename this file to match the name of your forecasting system
Inspect the application configuration for ConfigCourse (ConfigCourse_WC.xml) and set the preferred language (e.g. to "NL" or "EN").
Run the Water Coach (ConfigCourse_WC.exe) and choose the scenario named "demo". Follow the on-screen instructions.
script_config.xml
Create the script_config.xml file from scratch, or check out this example
Note: The script file should always be named script_config.xml
The tools provided can be used in any way you like, get creative!
The current script runs for 10 seconds.
Extend the length of the script by changing the value of the <ScriptStop> keyword (in the file "script_config.xml" in the appropriate directory of the scenario database).
Test it!