Versions Compared

Old Version 55

changes.mady.by.user Arnejan van Loenen

Saved on

compared with

New Version 56

changes.mady.by.user Arnejan van Loenen

Saved on

Key

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

...

Code Block
languagexml
titleExample
		<timeSeriesSet>
	<description>Example time series set</description>
	<moduleInstanceId>ImportTelemetry</moduleInstanceId>
	<valueType>scalar</valueType>
	<parameterId>H.obs</parameterId>
	<locationId>4539.TF</locationId>
	<timeSeriesType>external historical</timeSeriesType>
	<timeStep unit="minute" multiplier="15"/>
	<relativeViewPeriod unit="hour" start="-48" end="24" endOverrulable="true"/>
	<readWriteMode>read only</readWriteMode>
	<synchLevel>1</synchLevel>
	<expiryTime unit="day" multiplier="100"/>
            <moduleInstanceId>Import_NWS_GEFS</moduleInstanceId>
            <valueType>grid</valueType>
            <parameterId>P.forecast</parameterId>
            <locationId>GEFS</locationId>
            <timeSeriesType>external forecasting</timeSeriesType>
            <timeStep unit="hour" multiplier="6"/>
            <readWriteMode>add originals</readWriteMode>
            <ensembleId>GEFS</ensembleId>
        </timeSeriesSet>


Info

When dealing with ensembles, the ensembleId needs only be defined if the workflow activity that is used must retrieve the complete ensemble, or if members are to be written under a new ensembleId. In other cases the ensembleId needs only be defined in the workflow definition (see Workflows chapter). For the TimeSeriesSets defined in modules there is then no difference between running in ensemble mode and running normally.

...