Table of Contents |
---|
Configuration guide for an IDMA display
An IDMA display shows the difference between accumulated values of an observed time series and average accumulation of a number of time series from a base group of locations. If the observed time series has missing values, values from an estimated time series can be used.
To create an IDMA display, a DoubleMassDisplay.xml should be configured. As the example below Example 1 shows, the content of this display include includes three time series sets, namely: baseGroupTimeSeriesSet, observedTimeSeriesSet, and estimatedTimeSeriesSet. These time series sets refer to a locationSetId, as shown on lines 10, 21, and 32, in the example.DoubleMassDisplay configuration example, from which, a number of locations are filtered to be shown on the IDMA display. These specific locations are referred to in the configured nodes in Topology.xml. Example 2 shows a configured node with four location IDs.
In addition, in the DoubleMassDisplay.xml, a modifier ID should be configured, which refers to the id of a time series modifier, defined in ModifierTypes.xml. This time series modifier also refers to the same location set referred to in DoubleMassDisplay.xml. Example 3 shows a configured time series modifier.
Example 1: a DoubleMassDisplay.xml configuration:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<doubleMassDisplay xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/doubleMassDisplay.xsd"> <modifierId>IDMATest</modifierId> <baseGroupTimeSeriesSet> <moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId> <valueType>scalar</valueType> <parameterId>PP_Month</parameterId> <qualifierId>merged</qualifierId> <qualifierId>pxpp_pp24</qualifierId> <locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="month"/> <readWriteMode>read complete forecast</readWriteMode> </baseGroupTimeSeriesSet> <observedTimeSeriesSet> <moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId> <valueType>scalar</valueType> <parameterId>PP_Month</parameterId> <qualifierId>merged</qualifierId> <qualifierId>pxpp_pp24</qualifierId> <locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="month"/> <readWriteMode>read complete forecast</readWriteMode> </observedTimeSeriesSet> <estimatedTimeSeriesSet> <moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId> <valueType>scalar</valueType> <parameterId>PP_Month</parameterId> <qualifierId>merged</qualifierId> <qualifierId>pxpp_pp24</qualifierId> <locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="month"/> <readWriteMode>read complete forecast</readWriteMode> </estimatedTimeSeriesSet> </doubleMassDisplay> |
Example 2: a configured node with three location ids in Topology.xml:
Code Block | ||
---|---|---|
| ||
<node id="PRISM" name="PRISM">
<locationId>NY0254</locationId>
<locationId>NY0641</locationId>
<locationId>NY0542</locationId>
<locationId>NY0658</locationId>
<workflowId>ImportPRISM</workflowId>
<mapExtentId>CONUS</mapExtentId>
<filterId>ImportPRISM</filterId>
<showRunApprovedForecastButton>true</showRunApprovedForecastButton>
</node>
|
Example 3: a configured time series modifier in ModifierTypes.xml:
Code Block | ||
---|---|---|
| ||
<timeSeriesModifier id="IDMATest" name="IDMATest">
<timeSeries>
<moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>PP_Month</parameterId>
<qualifierId>merged</qualifierId>
<qualifierId>pxpp_pp24</qualifierId>
<locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep unit="month"/>
</timeSeries>
<defaultStartTime>start run</defaultStartTime>
<defaultEndTime>end run</defaultEndTime>
<defaultValidTime/>
<resolveInWorkflow>true</resolveInWorkflow>
<resolveInPlots>false</resolveInPlots>
</timeSeriesModifier> |
IDMA display example
Example 4 shows an IDMA display. The blue, green, and red lines each correspond to accumulation differences for three different time series from three different locations, namely: DORSET 2 SET, PERU, and DALTON. The blue line is thicker than the rest because it corresponds to the location (DORSET 2 SET) which is selected in the location drop down. The gray lines show calculations with estimated values, wherever observation values were not available.
Example 4: an IDMA display
Applying modifiers
As the display in Example 4 shows, the slope of the accumulated differences changes at different places. Therefore it is possible to apply a modifier wherever a slope change is observed to make corrections. To apply a modifier, a start time, end time, and a correction factor need to be specified. On the IDMA plot, two orange markers correspond to the specified start and end times. Once a modifier is applied, it is possible to choose to see the raw values to be able to compare them with the modified values. The raw values will be shown with the same color, but different line style and line width, to indicate the possible differences.
Example 5 shows the display after a modifier was applied. In this case, the specified factor is 2. The dashed blue line shows the raw estimates before the modifier was applied.
Example 5: an IDMA display, before a modifier is applied