Anchor |
---|
| application_config |
---|
| application_config |
---|
|
Application Configuration: WaterCoachDisplay.xmlCreate the WaterCoachDisplay.xml (you can use this example - navigates to another see documentation or example - both navigate away from current wiki page) Anchor |
---|
| script_config |
---|
| script_config |
---|
|
Script configuration: script_config.xmlCreate 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. With the example script_config.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?
The tools provided can be used in any way you like, get creative! Anchor |
---|
| forecasttable |
---|
| forecasttable |
---|
|
Forecast tableInspect 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 ConditionsAdd 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 FilesInspect 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 dotsSo 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. |