Page History

...

<periodCoefficientSet>
  <!-- periodCoefficientSet A -->
  <period>
    <startDateTime date="2002-01-01" time="00:00:00"/>
    <endDateTime date="2003-01-01" time="00:00:00"/>
  </period>
  ...
</periodCoefficientSet>
<periodCoefficientSet>
  <!-- periodCoefficientSet B -->
  <period>
    <startDateTime date="2003-01-01" time="00:00:00"/>
    <endDateTime date="2004-01-01" time="00:00:00"/>
  </period>
  ...
</periodCoefficientSet>
<periodCoefficientSet>
  <!-- periodCoefficientSet C -->
  <period>
    <startDateTime date="2010-01-01" time="00:00:00"/>
    <endDateTime date="2011-01-01" time="00:00:00"/>
  </period>
  ...
</periodCoefficientSet>

Run transformations for a set of selected locations

In some cases it is usefull to run a transformation only for a specific set of locations. For example when the entire workflow has already ran and there is only a change at a specific location. This situation can occur, for example, when a water level has been editted or when the configuration is changed.

In this case the workflow can skip the calculations for the unchanged locations. The main benefit of this approach is that it saves a lot of processing time.

This functionality is now available in FEWS.However it is important to understand that this functionality cannot be used in all workflows. The functionality can be applied for transformations only. It cannot be used for running models or secondary validations. When a transformation is started for a location selection than the transformation will only start when all the locations of the input timeseries and the output timeseries are part of the location selection. If this is not the case the transformation will not start.

It is also important to note that this functionality is limited to transformations where the locations of the input time series and the output location are the same. This is typicaly the case for interpolations, aggregations etc.

This functionality cannot be used for spatial transformations. This will be explained with a simple example.

In this example we have a workflow with 2 transformations. The first transformation consists of a interpolation. In the second transformation a closest distance transformation is done. The user wants to calculate the output for a certain output location of the closest distance transformation. When the workflow is started, the interpolation transformation will be started first. However at this point FEWS should know which locations will used as input when the time series for the selected locations will be calculated, because these are the locations for which a interpolation needs to be done. The other calculations can be skipped. Although it is possible to derive such information by analyzing the flow of the transformation it is decided at this point not to implement this. This means that this functionality cannot be applied for this type of tranformations.

This is reason why it is only possible to run a set of transformations for a location selection for tranformations in which the input locations are the same as the output locations. There is one expection for this rule. For the statisticRelatedLocation-transformations the functionality is also supported. When such a transformation is started and the outputlocation has a relation with 1 or more inputlocations and the either the outputlocation is selected or one the inputlocations than the selected locations will be extended with the inputlocations and the outputlocations.

In addition to the above, this functionality can only be used for non-forecast workflows. Typically this functionality should be used for pre-processing of post-processing.

Therefore it is by default not possible to run a workflow for a specific location selection. This is only possible when in the workflowdescriptors the option allowSelection is to true. This option should only be set to true when the configurator has checked that the workflow is suitable for running for a specific location.

Implementation plan

The following steps should be followed when this functionality is implemented.
1) Decide in which situations this functionality is needed
2) Make a list of the workflows which need to run in this type of situations
3) Ensure that the workflow only consists of transformations for which this functionality can be used
4) Move transformations or other parts of the workflow which are suitable for this type of operations to another workflow
5) Set the option allowSelection to true in the workflow descriptor for the workflow which can be used for selection specific calculations