Versions Compared

Key

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

What

A workflow.xml

Required

no

Description

Definition of sequence of modulesinstances moduleInstances (or workflows) in logical order

schema location

http://fews.wldelft.nl/schemas/version1.0/workflow.xsd

...

All workflows are defined in the Workflows section of the configuration; when working from a filesystem this is the WorkflowFiles directory.. Each workflow will have the same structure and must adhere to the same XML schema definition. Workflows are indentified by their name, which are registered to the system through the workflowDescripots workflowDescriptors configuration in the Regional Configuration section.

Workflows

All workflows defined in DELFT-FEWS must adhere to a common schema. Worlkfows defined Workfows defined may either be available from the Workflows table -- when the configuration is loaded into the database , -- or available in the WorkflowFiles directory when the configuration is available on the file system.

...

ImportExternal               Fixed file Choosen  name for the ImportExternal this workflow.

1.00                                            00                               Version number

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

...

  • Simple activities
  • Activities with a fallback activity;
  • Activities to be run as an ensemble.

Each activity can either be a single moduleInstance of another workflow.


Figure 142 Elements of the Workflow configuration.

...

Root element for the definition of a workflow activity. Multiple entries must can be defined.

runIndependent

...

Info

When running activities as an ensemble that request time series sets from the database that are not a part of that ensemble, the default ensembleId should be added to the TimeSeriesSets definition. The default ensemble Id is "main".

All time series sets written when running in ensemble mode will have the ensembleId as specified in the workflow ensembleId element, unless overruled by a local ensembleId defined in the timeSeriesSet on writing.

Example

No Format

<?xml version="1.0" encoding="UTF-8"?>
<workflow version="1.1" xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews
E:\schemas\workflow.xsd">
	<activity>
		<runIndependent>false</runIndependent>
		<moduleInstanceId>Astronomical</moduleInstanceId>
	</activity>
	<activity>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>BackupPrecipitation_Forecast</moduleInstanceId>
	</activity>

		<runIndependent>true</runIndependent>
		<moduleInstanceId>PrecipitationGaugeToGrid_Forecast</moduleInstanceId>
	</activity>
	<activity>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>Spatial_Interpolation_Precipitation_Forecast</moduleInstanceId>
	</activity>
	<activity>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>MergePrecipitation_Forecast</moduleInstanceId>
	</activity>
	<activity>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>GridToCatchments_Forecast</moduleInstanceId>
	</activity>
	<activity>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>Singapore_Sobek_Forecast</moduleInstanceId>
	</activity>
</workflow>