Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
In the Water Coach, making a forecast with FEWS can be trained. Stand-Alone mode
|
Table of Contents | ||
---|---|---|
|
In the Water Coach, making a forecast with FEWS can be trained.
Stand-Alone mode
Section |
---|
Start Delft-FEWS and the WaterCoach pluginStart the executable of the required Delft-FEWS application can be started directly:
Start the WaterCoach plugin via the menu, if this is not started automatically. A docked window will appear. The window may show two sections; a 'Select scenario' section, and a 'Generate scenario' section. The latter is only available since FEWS 2023.01, and if explicitly configured. It's usage is explained below, and the configuration is explained in the WaterCoach-on-the-Fly configuration. First the 'Select scenario' option is explained. |
...
Column | ||
---|---|---|
| ||
Select a scenario/scriptIn the 'Select scenario' section the user can specify the user name, the scenario and script to be played, and the experience level (optional). By default, the first available scenario and script are selected. The user name is only used in the log-file. The log-file is created for each scenario/script that is played and is added (with a time stamp) to the appropriate directory in the scenario/script database. This default location of the log file can be overruled by specifying the location in the WaterCoach Display configuration. The chosen scenario and script can be started with the " Note: since the selection of the experience level is optional, this field might not be visible. If you have started WaterCoach previously, you will first get a question if you want to continue with this previous session. If you choose yes, you will continue with the data generated in the previous session (i.e. the LocalDataStore). (You only get this question if you have shut down the WaterCoach completely, i.e. both the window with the clock and the menu to select a Scenario and Script.)
|
Column |
---|
|
...
width | 45% |
---|
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 (see how-to WaterCoach-on-the-Fly configuration). 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:
- the name of the scenario;
- the start time of the scenario;
- the end time of the scenario;
- (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;
- (if configured): specify whether archived model states should be available in the scenario;
- (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:
- 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.
- 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.
- 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 copy the configuration with a simple script.xml to the new scenario folder.
...
width | 45% |
---|
...
Column | ||
---|---|---|
| ||
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 timeThe 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 " Note: since the presence of these buttons is optional, what you see may differ from the example on the right. CommunicationDepending 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 " Note: since the presence (and labels) of the communication buttons is optional, what you see may differ from the example on the right. DictionaryDepending 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 |
---|
Section |
---|
Publish a ForecastForecasts can be made in the forecast window, which will appear by pushing the " Note: the content of the forecast window is completely configurable, what you see may differ from the example. |
Section |
---|
Stopping the WaterCoachWhen you close WaterCoach control panel (i.e. "clock"), you will be able to select and start another scenario and/or script in the WaterCoach plugin. The last selected scenario and script will be written in user_settings.ini. When you close the WaterCoach plugin, the WaterCoach mode is switched off. Participant modeStart master Delft-FEWS applicationNote: It is important to always first completely start the master Delft-FEWS application and its WaterCoach session, before any of the participant clients are started, since they make use of the LocalDataStore of the master application.
Start participant Delft-FEWS applicationNote: It is important to always first completely start the master Delft-FEWS application and its WaterCoach session (see previous steps), before any of the participant clients are started, since they make use of the LocalDataStore of the master application.
Expected behavior during the training
Stopping the training
|
...
Column | ||
---|---|---|
| ||
Multiple Delft-FEWS applications for a combined training with WaterCoachWhen two or more Delft-FEWS application are connected for a combined training with WaterCoach, you will see a section on "Multiple Systems" in the WaterCoach display. Start leader Delft-FEWS applicationThe leader Delft-FEWS application will be the application that will determine the time (i.e. write the time file with which the followers synchronize).
Start follower Delft-FEWS application(s)Note: it is recommended to start the leader before the follower(s), but it is not mandatory for the functionalities. It is possible to connect more than one follower to the leader.
Start participant Delft-FEWS application(s) (optional)Start the participant Delft-FEWS application as described above (optional). Expected behavior during the combined training
Stopping the combined trainingThere are several ways to stop a combined training, each with it's own behavior as described below.
|
...
Column |
---|