Page History

Each workflow configured in DELFT-FEWS must be registered in the WorkflowDescriptors configuration. This is required to identify the workflow to DELFT-FEWS (the format of the name is free). The configuration also sets some properties of the workflow.

When available on the file system, the The default name of the XML file for configuring the WorkflowDescriptors is for example:

WorkflowDescriptors 1.00 default.xml

WorkflowDescriptors                  Fixed file name for the WorkflowDescriptors configuration

1.00                                            Version number

default                                       Flag to indicate the version is the default configuration (otherwise omitted).

WorkflowDescriptors  is:  WorkflowDescriptors.xml. This file is located in the RegionConfigFiles folder.

Image Added
Figure: Image Removed
Figure 45 Elements of the workflowDescriptor configuration.

workflowDescriptor

Root element of the WorkflowDescriptor. A new element is required for each workflow. Multiple instances may be defined.

...

• Id: Id of the workflow. This Id must be unique. Normally a string is used that gives some understanding of the role of the module (e.g. ImportExternal).
• name: Optional name for the module. Used for reference purposes only.
• visible: Boolean toggle to indicate if workflow is visible for selection in the manual forecast display. Dependent workflows (e.g. sub-workflows) should not be marked visible so that these cannot be run independently. Default is true.
• Forecast: Boolean flag to indicated if workflow is identified as a forecast. This should be the case for workflows with simulated time series as a results. Only Forecast workflows can be approved and made current. Import workflows of external data are not forecasts. Default is true.
• allowApprove. Boolean flag to indicate if workflow may be approved a-priori through manual forecast display (stand-alone only). Default is true.
• autoApprove. Boolean flag to indicate workflow should automatically be approved a-priori (stand-alone only). Default is false.
• autoSetSystemTime. Boolean flag to indicate workflow should automatically adjust the system time. When the workflow is completed and is fully or partly successful, the system time wil be set to the start time of the period written by this workflow.
  If the start time is not a valid time in accordance with the cardinal timestep, the next valid time wil be used.
  Default flag value is false. Applicable only on stand-alone.
• maxEnsembleParts: Positive integer. Determines in how many parts (i.e. forecasting shell instances available) at most the workflow can be split up to run in parallel for ensembles. Ensembles can/will only be split up if this element is specified and the number specified is larger than 1.
• timeOut (since 2012_02): optional timeout that a workflow is allowed to run before the Forecasting Shell terminates it. This setting is independent of the master controller chaser. Therefore it makes only sense to specify a time out smaller than the master-controller chaser grace time.
• showWarningInLogCompletion (since 2014.01): Boolean to report whether warning messages were logged during the execution of the workflow, default false.

Image Removed

waterCoachDelaySpanMillis (available since build 33472)

Example:

<waterCoachDelay unit="hour" multiplier="4"/>

timeout

Example:

• waterCoachDelay: Prevents simulated forecasts becoming available too early in water coach mode. The forecasts are finished in real life at time zero plus delay. The delay includes the run time and the time0 shift. When a forecast is scheduled at 7:00 am with a time0 of 0:00 am and the runs takes approximately an hour you should specify an delay of 8 hours. For external forecasts the delay is configured in the moduleInstanceDescriptors.xml

Node (since 2019.01)

The workflows can be organised in a folder structure in the Manual Forecast Display with the node element. The workflow desctiptor ID's need to be added to the nodes.

<rootNode>
		<node name="Import">
			<workflowId>Import_Hydro_Observations</workflowId>
			<workflowId>Import_Forecasts</workflowId>
			<workflowId>Import_EarthObservation</workflowId>
			<workflowId>Import_Earth2Observe</workflowId>
			<workflowId>Import_HYCOM_All</workflowId>
			<workflowId>Import_WaveWatch3</workflowId>
		</node>
		<node name="Process">
			<workflowId>Create_GFS_Ensembles</workflowId>
			<workflowId>Copy_GFS_Grid</workflowId>
			<workflowId>Modify_GFS_Grid</workflowId>
		</node>
		<node name="Rest">
			<workflowId>Process_Operational_Grids</workflowId>
			<workflowId>WFlow_historic</workflowId>
			<workflowId>WFlow_forecast</workflowId>
			<workflowId>WFlow_E2O_historic</workflowId>
			<workflowId>Fractions_forecast</workflowId>
		</node>
	</rootNode>

<timeout unit="minute" multiplier="5"/>