Info |
---|
|
This page gives information on the set up of a training. Other pages describe the technicalities like |
Section |
---|
Scenario and Script database: set up the training |
Section |
---|
Column |
---|
|
|
Set-up environment
To set-up a
traning training environment for the Delft-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
(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
and ConfigCourse_WC.jpif
file to start the ConfigCourse_WC system. - Add a
jre
folder (copy of the jre folder in the operational FEWS system)
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
and ConfigCourse_WC.jpif
file to start the WaterCoach
Create the folder ScenarioScriptDatabase
- Create the folder
WaterCoach
for the ScenarioScriptDatabase- Add a folder
Demo
_scenario
for the (first) scenario- Add a folder
Demo_script
for the (first) script for this specific scenario- Add the
script_config.xml
file and all the necessary files that are referenced in the script
- Add a folder
localDataStore
containing the local data store for this scenario (this may be a
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
Section |
---|
Anchor |
---|
| application_config |
---|
| application_config |
---|
|
Application Configuration: WaterCoachDisplay.xmlCreate the WaterCoachDisplay.xml (see documentation or example - both navigate away from current wiki page) Anchor |
---|
| script_config |
---|
| script_config |
---|
|
Script configuration: script_config.xml Column |
---|
Image Removed |
|
Section |
---|
Column |
---|
|
|
applicationCreate the script_config.xml file from scratch, or check out this example - navigates to another wiki page.
Note: The script file should always be named script_config.xml.
Create With the
application example script_config
xml file, you can use this example
You can rename this file to match the name of your forecasting systemInspect 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.
Column |
---|
Image Removed |
Section |
---|
.xml in place you can run the Water Coach by double clicking the WaterCoach.exe. Try it! Inspect the elements of the example and make modifications: dataStart , dataStop , displayStart What is the difference between dataStart and displayStart ? How can you use this? How long does the example script run? Extend the length of the game by changing the value of the dataStop keyword. stories are what the script revolves around-
forecastTable and the foreastNote are the objective of the Water Coach -
dictionaryFiles can be used in many different ways
Below, we will take a closer look at stories , forecastTable and dictionaryFiles You can run the Water Coach by double clicking the WaterCoach.exe. Select the scenario and script you have created. Test your modifications! StoriesThere are two types of stories. Inspect the Stories of the example FramesInspect the Frames of the example and make modifications: -
title is how the frame is presented to the trainee Change the title to reflect the content of the frame -
start , stop and popup define how a frame is executed Add a story to the script that contains at least three frames. Make the first frame active for the first 30 seconds of the script, the second for the next 30 seconds and so on. Experiment with the start, stop, and popup keywords in a story. -
requiredExperienceLevel Experiment with the experience levels. Do you want to make changes to your script_config.xml? -
once With the once option you can simulate a phone call. How can you fit that into your script? -
condition is a method to make the script more interactive We take a closer look at the condition below -
file Add a file (e.g. pdf or png) to the ScenarioScriptDatabase. Add a frame to the inbox or a story that displays this file. -
message How does a message appear to the trainee?
Column |
---|
|
|
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.xmlThe 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!
Anchor |
---|
| forecasttable |
---|
| forecasttable |
---|
|
Forecast table
Inspect the Forecast table of the example and make modifications:
-
header, column
Add at least one non-editable and one editable column to the forecast table.
Do you want to export the content of this column? row, cell
Add at least one row to the table
Use your creativity for suitable content
Feel free to change the existing content of the forecast table
Conditions
Add a condition to at least one frame, either in the inbox or a story.
You can also duplicate the frame and use disjunctive conditions for the two frames.
Dictionary Files
Inspect the Dictionary files that is referred to in the example.
Inspect the Dictionary, which is a sperate file. Where can you find this file?
- Add a reference to another dictionary file
- Fill this dictionary file with
word
s and their definition
A dictionary could be used to aid a less experienced trainee
Every time the dictionary is used, this is logged for after action review
Can you find the log file for this training session?
Connecting the dots
So far, alterations to the script have been made without referring to the scenario, i.e. the contents of the Delft-FEWS local data store. Start-up Delft-FEWS and inspect the data that is available.
Construct a simple script with events for a trainee in which he/she has to inspect the data in Delft-FEWS in order to be able to publish a forecast (for a location and parameter of your choice).
Give feedback at the end of the script about the forecast that he/she made.
Column |
Image Removed