...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Figure 76 Elements of the ImportActivities configuration
...
Root element for importing modules states resulting from the run of the external modules. Multiple elements may be defined. If no state is to be imported (for example in forecast run as opposed to state run), then the element should not be defined.
- stateConfigFile
...
- - Fully qualifying name of the
...
- XML file
...
- containing the state import configuration
- expiryTime - When the state is an intermediate result in a forecast run you can let the state expire. By default the expiry time is the same as the module instance run.
- synchLevel - Optional synch level for state. Defaults to 0 is not specified (i.e. same as data generated by the forecast run)
stateConfigFile
Name (and location) of the PI-XML file describing the states to be imported. If the directory location is not explicitly specified the file will be expected to be read from the importDir defined in the general section. This file contains all necessary information to define state type and location. The moduleInstanceId of the state imported is per definition the current module instance.
importTimeSeriesActivity
Root element for importing scalar and polygon
importTimeSeriesActivity
Root element for importing scalar and polygon time series resulting from the run of the external modules. Multiple elements may be defined.
importMapStacksActivity
Root element for importing grid time series resulting from the run of the external modules. Multiple elements may be defined.
importProfilesActivity
Root element for importing longitudinal profile time series resulting from the run of the external modules. Multiple elements may importFile and timeSeriesSet should be defined.
- importFile
...
- - PI-XML file describing the time series to be imported. The file contains all information on type of data to be imported (scalar, longitudinal, grid, polygon). For all data types except the grid the file also contains the time series data If the directory location is not explicitly specified the file will be expected to be read from the importDir defined in the general section.
...
importMapStacksActivity
Root element for importing grid time series resulting from the run of the external modules. Multiple elements may be defined. importFile and timeSeriesSet should be defined.
importPiNetcdfActivity
Root element for importing grid time series in Pi-Netcdf format. importFile and timeSeriesSet should be defined.
importProfilesActivity
...
Root element for importing longitudinal profile time series resulting from the run of the external modules. Multiple elements may be defined. importFile and timeSeriesSet should be defined.
Shutdown Activities
Figure 77 Elements of the Shutdown Activities configuration
This activity is the identical to the startUpActivities. The only difference is that these are carried out after the module run and import of data. See definition of StartUp activities for configuration.