Versions Compared

Key

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

Image Added

*

...

  • 1
  • Anchor
    _Toc140564173
    _Toc140564173
    Anchor
    _Ref55639357
    _Ref55639357
    Anchor
    _Toc172823846
    _Toc172823846
    Manual Forecast Display
    The Manual Forecast display (see below) in the Operator Client allows for the

...

  • running of single or a manually scheduled forecast.

Image Added

The Manual Forecast display (see below) in a Standalone system is slightly different from the one in the Operator Client and allows for running of a single forecast or a batch of forecasts.

Image Added

manual forecasts. A Stand Alone system only supports a single forecast; in this case no schedule options can be used. In order to use a scheduler a client-Server version of the FEWS including a Master Controller and Forecasting Shell Servers have to be configured.

Wiki Markup
A configured manual forecast single or a series of forecasts can be submitted to the system by pressing \[Run\]. With \[Close\], a user can leave the Manual Forecast display.
Image Removed

Wiki Markup
The various items in the Manual Forecast display are described below.
 Workflow 
A workflow can be selected from a drop-down list with pre-configured workflows. By pressing \[INFO\], a description of the selected workflow can be displayed.
 What-if Scenario 
A What-if Scenario can be selected from a drop-down list with predefined What-if Scenarios. By pressing \[INFO\] a description of the selected What-if Scenario can be displayed. What-if Scenarios are defined via the What-if Scenario display (see section 2.8)
 Forecast description 
A forecast description can be entered in this field. Entering of a description is not obligatory.

Please note that the forecast name is generated automatically by the system and consists of the (i) start time of a forecast, (ii) the selected workflow and (iii) the selected What-if Scenario.
Scheduler options (only in Operator Client)
Two types of manual forecasts can be defined:

...

A single forecast will only run once. A scheduled manual forecast will run for a period of time and with a time interval both defined by the user. The scheduled manual forecast can only be selected when the system is a FEWS Client-Server version. For single forecast only the T~0~ of the forecast has to be entered in the date & time field (yyyy-MM-dd HH:mm).

A scheduled manual forecast will run for a period of time and with a time interval both defined by the user. In case a manual forecast is scheduled, the following information should be entered by the user:

...

In case for example scheduled manual forecasts should always be made at 8:00 AM but the forecast itself should start at 12:00 PM the previous day, the Shift T~0~ should be set at 8 hours while the Start time is set at 08:00.

*_ Approve_*

Ticking the approve box will set the status of the forecast to current. Please note that in an operator client automatic current forecasts can not be set via the manual forecast display. This can only be done by a system manager using the Admin Interface. Reconfiguration or cancelling of both automatic forecasts and scheduled manual forecasts can only be done by the system manager.

*_ Forecast length_*

A default forecast length is configured when setting up the forecasting system. Please note that within an area different forecasts lengths may have been configured depending on for example the hydrological (sub-) system and/or the forecasting models used.

...


Batch Forecast options (only in standalone)
Two types of manual forecasts can be defined:

  • single forecast
  • batch forecast

A single forecast will only run once. For single forecast only the T~0~ of the forecast has to be entered in the date & time field (yyyy-MM-dd HH:mm).

In batch mode, a scheduled manual forecast will run for a period of time and with a time interval both defined by the user. In case a manual forecast is run in batch mode, the following information should be entered by the user:

  • Period of time for which a scheduled manual forecast should run is defined by entering the Start T0 and End T0 (yyyy-MM-dd HH:mm). The first forecast run will be made with the Start T0.
  • Via menu item Interval , the time interval at with which the T0 of consecutive forecasts should be increased when submitted.

All runs will be submitted at the same time but will be run with different T0's as defined by the user.

Automatically approving forecasts

Ticking the approve box will set the status of the forecast automatically to current after it has been completed. In case you want to cancel this action or suspend it, please use the Scheduled Forecast tab in the System Monitor.

State Selection

Leaving Select initial state unchecked, the default state- as has been configured by the system manager- will be used to start the historic run preceding a forecast simulation (see also Running Modules ). For statefull simulation models like PDM or ISIS - like hydrodynamic models- this means that the state selection for a model will follow the state selection rules as configured in the General Adapter Module Instances.

...

In case no Warm state can be found within the defined Search interval , the system will automatically run as if Select initial state was unchecked. This means that in that case the default state will be used for starting the historic run.

Priority

The user can give a forecast run either a High or a Normal priority. The Master Controller will give precedence to high priority tasks above normal priority tasks.

Please note that setting the priority to 'high' does not mean that the task will be directly carried out. In case other high priority tasks are waiting for execution, the new task will be added to the queue. When another task with normal priority is already being executed, it will not be cancelled when a new high priority task is submitted, but will be completed first.

Forecast length

A default forecast length is configured when setting up the forecasting system. Please note that within an area different forecasts lengths may have been configured depending on for example the hydrological (sub-) system and/or the forecasting models used.