...
Grouping to accommodate parallel execution of multiple activities when multiple CPU available. Parallel Since FEWS 2017.01 it is optionally possible to run the parallel activities on multiple forecasting shells. Parallel activities should only be configured when the underlying activities have no data dependency. If data dependency exists, activities should be executed in sequence. This may be forced by embedding them as part of a sequence group. Since FEWS 2017.01 it is optionally possible to run the parallel activities on multiple forecasting shells. This can be done with the multipleForecastingShells=true or forecastingShellCount=n for ensembles and location loopsTo run on multiple FSS specify multipleForecastingShells=true
workflow:parallel - split ensemble loops and locations loops over multiple forecasting shells
To split loops over multiple forecasting shells specify forecastingShellCount = n. Every underlying loop is split into n parts. Every FSS is running the same specified activity but skipping the part of the ensemble loop / location loop that is meant for an other FSS. It is not allowed to start a nested parallel when you are in a ensemble/location loop parallel.
workflow:sequence
Grouping to enforce sequential execution of multiple activities as they generally have data dependencies. Typically used in workflows where parallel activities are defined to clarify which activities have be to executed in sequence.
Figure 143 Elements of an Parallel Activity in the workflow.
...