Versions Compared

Old Version 131

changes.mady.by.user Bart Adriaanse

Saved on

compared with

New Version 132

changes.mady.by.user Bart Adriaanse

Saved on

Key

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

...

Code Block
xml
xml
	<variable>
		<variableId>Observation</variableId>
		<timeSeriesSet>
			<moduleInstanceId>Afgeleide_Twentekanalen</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>H.meting</parameterId>
			<locationSetId>Hydro_LMW_TK_H</locationSetId>
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="hour"/>
			<relativeViewPeriod unit="hour" start="-1" end="0"/>
			<readWriteMode>read only</readWriteMode>
		</timeSeriesSet>
	</variable>
	<variable>
		<variableId>Correction</variableId>
		<timeSeriesSet>
			<moduleInstanceId>Afgeleide_Twentekanalen</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>H.meting</parameterId>
			<locationSetId>Hydro_LMW_TK_H</locationSetId>
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="hour"/>
			<relativeViewPeriod unit="hour" start="-1" end="0"/>
			<readWriteMode>read only</readWriteMode>
		</timeSeriesSet>
	</variable>
	<variable>
		<variableId>Observation_minus_correction</variableId>
		<timeSeriesSet>
			<moduleInstanceId>Afgeleide_Twentekanalen</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>H.meting</parameterId>
			<locationSetId>Hydro_LMW_TK_H</locationSetId>
			<timeSeriesType>temporary</timeSeriesType>
			<timeStep unit="hour"/>
			<relativeViewPeriod unit="hour" start="-1" end="0"/>
			<readWriteMode>add originals</readWriteMode>
			<synchLevel>9</synchLevel>
		</timeSeriesSet>
	</variable>
	<transformation id="TransformationObservationMinusCorrection">
		<user>
			<simple>
				<expression>Observation - Correction</expression>
				<outputVariable>
					<variableId>Observation_minus_correction</variableId>
				</outputVariable>
			</simple>
		</user>
	</transformation>
...

Navigation using Topology

To navigate different SSD displays and panels within a SSD display, specific elements can be added to the topology.xml configuration, as in the following example.

Code Block
languagexml
	<nodes id="SSD_NL" name="SSD NL">
		<node id="Overzichtsscherm_WMCN" name="Overzichtsscherm Nederland">
			<mainPanel>schematic status display</mainPanel>
			<scadaDisplayId>ScadaOverzichtsscherm_WMCN</scadaDisplayId>
			<scadaPanelId>Overzichtsscherm_WMCN</scadaPanelId>
		</node>
		<node id="Verwachtingenscherm_WMCN" name="Verwachtingen Nederland">
			<mainPanel>schematic status display</mainPanel>
			<scadaDisplayId>ScadaOverzichtsscherm_WMCN</scadaDisplayId>
			<scadaPanelId>Verwachtingenscherm_WMCN</scadaPanelId>
		</node>
	</nodes>
mainPanel

This element will bring the open SSD display (if any to) the front, this element is optional and works well if only a single SSD display is open. In case you need to be able to open multiple SSD displays at the same time you may want to omit this element, in that case

Known Issues

When using Delft-FEWS the configuration can be present as files on the file system or can be contained in a local data store. The svg files that are used for the schematic status display work in both cases. However, if the svg files refer to separate image files, then the schematic status display can only display these images if the image files are present as files on the file system. If these separate image files are contained in a local data store, then they cannot be displayed in the schematic status display. Therefore, when using separate image files, make sure that the configuration is present as files on the file system. If this is not possible, then it is possible to choose from two different workarounds:

...