Versions Compared

Old Version 38

changes.mady.by.user Maarten Smoorenburg

Saved on

compared with

New Version Current

changes.mady.by.user Maarten Smoorenburg

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section


Column
width45%

Generate a scenario (available since Delft-FEWS 2023.01)

In the 'Generate scenario' section the user can make a simple scenario with data from the Open Archive. It requires that the Stand Alone system has a direct connection to the Open Archive, and that this section is enabled in the configuration (se see how-to here). With this functionality, a user can make a very simple script that works with the data that can be downloaded automatically from the Open Archive for a specified time window. This makes it very easy for users to play back some event or have a starting point for a more complex scenario.
To generate a scenario, the user should specify:

  1. the name of the scenario;
  2. the start time of the scenario;
  3. the end time of the scenario;
  4. (if configured): whether grids should be fully downloaded and imported in the scenario's localDataStore, or should use the 'import grids as reference' functionality whereby the actual data is only downloaded from the archive when a user is viewing them in a display;
  5. (if configured): specify whether archived model states should be available in the scenario;
  6. (if configured): specify whether archived modifiers should be available in the scenario.

Note: the period for which data is downloaded depends on the timeseriesType, consistent with the tagging functionality of the Open Archive;

  • for observed time series (i.e. timeSeriesType is external historical), all observations within between the start and end time are downloaded and imported.
  • for external forecasts (i.e. timeSeriesType is  external forecast), all external forecast for which the forecast window falls between the start and end time are downloaded and imported. This means that also external forecasts with an analysis time older than the specified start time are used.
  • for simulations (i.e. timeSeriesType is simulated historical or simulated forecast), the simulations for which the T0 falls between the start and end time are downloaded and imported.

Upon pressing the 'Generate' button, the user is asked 3 questions in pop-up windows that appear after one another:

  1. pop-up 1 shows indications of size of the data that is to be downloaded, specified for scalar and grid data separately (download size of grids is not indicated if the "import grids as reference" options was selected). Press "Yes" if you want to continue, and "No" if not.
  2. pop-up 2 details the selection of FEWS configurations that the user can choose from; current configuration (always available), or some configurations found in the archive for the specified period; the last configuration until the start time, and all other configurations archived in the period between the start and end  time. The panel is empty if no configurations are found in the archive. 
  3. pop-up 3 ask the user to provide the scenario database folder that the new scenario should be added to. One can choose any folder here, but a folder on a local drive is preferred as the new to start WaterCoach will run directly in the created scenario folder. One could also choose to use the configured ScenarioScriptDatabase folder so that the scenario is immediately available for all WaterCoach instances that are connected to that folder. The recommended procedure, however, is to first test the scenario locally, and only copy it to the ScenarioScriptDatabase if one is satisfied with it.

After this folder is specified, the current Stand Alone FEWS instance will try to download copy the latest configuration that is available in the Open Archive until the given start time. If now configuration is found, the current configuration will be used. In both cases the configuration that is to be used for the scenario is copied to the scenario folder.configuration with a simple script.xml to the new scenario folder. 

After the configuration is ready in the scenario folder, a new FEWS instance is started with that configuration (details of which settings are used is are specified <<here>>. A pop-up window will appear, asking the user  if the download of data as specified for the scenario should be started. This window also specifies how much data is to be downloaded.), and the downloading and importing of the data from the archive begins. 

When all data is downloaded, the user can start to play the scenario from the 'Select scenario' section.


Column
width45%

 

 

Image Modified

Image Modified




Section


Column
width45%

Get to know the Water Coach Display ("clock")

After a scenario/script has been started, a new window will appear for the chosen scenario/script.

In-training time

The scenario/script window contains a panel with the scenario/script date and time (i.e. the in-training time). The time can be paused and resumed by the user. It is also possible to configure a "next activity"-button or a "fast forward"-button, with which the player can jump through time to the next message or speed-up the time, respectively. Furthermore, the presence of a button for manually setting the in-training time can be configured.

Note: since the presence of these buttons is optional, what you see may differ from the example on the right.

Communication

Depending on the script configuration, information (e.g. messages, phone calls, etc.) or exercises will be displayed either in FEWS or on the screen as a pop-up window for the user to process. Information can also become available behind the (optional) communication buttons. This information is dynamic, i.e. the contents can vary over time. As a third option, information can be retrieved by the user from the "inbox"-drop-down menu. The amount of information/help depends on the experience level that is chosen.

Note: since the presence (and labels) of the communication buttons is optional, what you see may differ from the example on the right.

Dictionary

Depending on the script configuration, words can be looked up in a dictionary.

Note: since the presence of the dictionay buttons is optional, what you see may differ from the example on the right.


Column


...