Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin



scrollbar


45%
Sectioninfo
titleAbout this page
Column
width

This page gives information on the set up of a training. Other pages describe the technicalities

of

like

.


jpif file

The .jpif file for the Water Coach has the following content:

..\jre
-mx512m
-cp
$JARS_PATH$
waterCoach.RunWaterCoach
..\application_config.xml

Optionally, you can pre-fill the form with which you select the scenario and such. In that case, add all of the following lines:
Name (i.e. Name of the participant)
Demo (i.e. Name of the scenario to be selected)
Demo_script (i.e. Name of the script to be selected)
1 (i.e. speed up factor)
1 (i.e. experience level
      • )
Section

Table of Contents
maxLevel3

Scenario and Script database: set up the training

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 (copy these files from the bin folder of the operational system and modify the region dir in the .jpif file)
  • Add a jre folder (copy of the jre folder in the operational FEWS system)
    • Create
    a WaterCoach folder Add
    • the
    application_config.xml fileAdd a bin
  • Add a jre folder (copy of the jre folder in the operational FEWS system) new as of FEWS 2013.02)
  • Add an ConfigCourse_WC.exe and ConfigCourse_WC.jpif file to start the WaterCoach (obsolete as of FEWS 2013.02)
  • Create the folder
    • folder
    containing the WaterCoach binaries (new as of FEWS 2013.02)Add a folder Demo ConfigCourse_WC for the system
      • 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 copy of the localDataStore folder from the operational system
    )
    Anchor
    jpifjpif
    Column

    Image Removed


    width

    Section
    Column
    45%
    Anchor
    application_config
    application_config

    application_config

    Application Configuration: WaterCoachDisplay.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, e.g. ConfigCourse_WC.xml

    Inspect the elements of the example and make modifications:

    • change the preferred language with the locale keyword (e.g. to "NL" or "EN")
    • check the path for the fewsExecutable
    • check the path for the fewsRegionDir
    • does the fewsSystemTimeUpdateInMinutes match your fews configuration? (obsolete as of FEWS 2013.02)
    • check the path for the scenarioScriptDatabasePath
    • check if the fileAssociation is correct for your system
      (optional, WC will search for system defaults if nothing is specified)
    • check the configuration of timeControl, what do all the options imply?
    • do you want to use a different experienceLevel?
    • does the fewsPiPortNumber match your fews configuration?
    Column

    Image Removed

    Section

    WaterCoachDisplay.xml (see documentation or example - both navigate away from current wiki page)

    Column
    width45%

    Anchor
    script_config
    script_config

    Script configuration: script_config.xml

    Create 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:

    scriptStart
    • dataStop,
    scriptStop
    • displayStart
      What is the difference between dataStart and
    scriptStart
    • displayStart?
      How can you use this?
      How long does the example script run?
      Extend the length of the
    script
    • game by changing the value of the
    scriptStop

    Below, we will take a closer look at stories, forecastTable and dictionaryFiles

    You can run the Water Coach by double clicking the

    ConfigCourse_WC

    WaterCoach.exe. Select the scenario and script you have created.
    Test your modifications!

    Column

    Image Removed

    Section Columnwidth45%

    Anchor
    stories
    stories

    Stories

    There are two types of stories. Inspect the Stories of the example

    Visualization of the stories

    By now we have created a nicely filled script. To get a visual overview of the activity in the script, you can use the showVisualizeScriptButton option. Make sure you have this button configured in your application config xml file and visualize your script.

    Do you like what you see?

    By keeping the Water Coach open, you can quickly visualize changes made to the script by reopening the visualization.

    Column

    Image Removed

    Section Column
    width45%

    Anchor
    frames
    frames

    Frames

    Inspect 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!

    Column

    Image Removed

    Section Columnwidth

    45%

    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

    Column

    Image Removed

    Section Column
    width45%

    Anchor
    condition
    condition

    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.

    Column

    Image Removed

    section

    Column

    width45%

    Anchor
    dictionary
    dictionary

    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 words 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?

    Column

    Image Removed

    Section Columnwidth45%

    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