...
Time | Input value | input flag | Output value | output flag | custom flagsource | |||||
|---|---|---|---|---|---|---|---|---|---|---|
1-1-2012 00:15 |
|
|
|
|
| |||||
1-1-2012 00:30 | 1 |
|
|
|
| |||||
1-1-2012 00:45 | 1 |
|
|
|
| |||||
1-1-2012 01:00 | 1 | 3 | doubtful | - | ||||||
1-1-2012 01:15 |
|
|
|
|
| |||||
1-1-2012 01:30 | 1 |
|
|
|
| |||||
1-1-2012 01:45 |
|
|
|
|
| |||||
1-1-2012 02:00 | 1 |
| NaN | - | - | |||||
1-1-2012 02:15 | 1 |
|
|
|
| |||||
1-1-2012 02:30 | 1 | doubtful |
|
|
| |||||
1-1-2012 02:45 | 1 |
|
|
|
| |||||
1-1-2012 03:00 | 1 | 4 | doubtful | D1 | ||||||
1-1-2012 03:15 | 1 |
|
|
|
| |||||
1-1-2012 03:30 | 1 |
|
|
|
| |||||
1-1-2012 03:45 | 1 |
|
|
|
| |||||
1-1-2012 04:00 | 1 | 4 | reliable |
The first output value is set to doubtful. Because in this case the total percentage of missing values is 25%. Which means that the following rule is applied.
| Code Block |
|---|
<validationRule> <inputMissingPercentage>40</inputMissingPercentage> <outputValueFlag>doubtful</outputValueFlag> </validationRule> |
...
The second output value is a missing value because in this case the percentage of missing values is equal to 50%. This means that in this case the following rule will be appplied.
| Code Block |
|---|
<validationRule> <inputMissingPercentage>100</inputMissingPercentage> <outputValueFlag>missing</outputValueFlag> </validationRule> |
...
The third output value is set to doubtful. The input doesn't contain missing values but has a single doubtful input value. The percentage of doubtful values in the input is therefore 25% which means that the following rule will be applied.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<workflowDescriptor id="FillRelations" forecast="false" visible="true"autoApprove="false"> <description>Met deze taak worden de gaten groter dan 2 uur gevuld dmv. relaties.</description> <allowSelection>true</allowSelection> <schedulingAllowed>true</schedulingAllowed> </workflowDescriptor> |
When a node in the IFD is selected with a workflow which has the allowSelection option set true, the GUI will look like this:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<explorerTask name="Forecasts"> <taskClass>nl.wldelft.fews.gui.plugin.selection.SegmentSelectionDialog</taskClass> <toolbarTask>false</toolbarTask> <menubarTask>false</menubarTask> <toolWindow>true</toolWindow> <loadAtStartup>true</loadAtStartup> </explorerTask> |
Trim Output
A boolean option <trimOutput> is available within transformations. When true, missing values at the start and end of the output will be removed before writing the data to the database. This can prevent existing values to be overwritten with missings.
Forecast Loop
For some transformations it is possible to define a forecast loop by configuring a <forecastLoopSearchPeriod>. This means that the transformation will be run for each forecast found within that period.
...