Versions Compared

Key

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



scrollbarSeveral variables are available to be use


What

nameofinstance.xml

Description

Configuration for the general adapter module

schema location

http://fews.wldelft.nl/schemas/version1.0/generalAdapterRun.xsd

Entry in ModuleDescriptors

<moduleDescriptor id="GeneralAdapter">
<description>General Adaptor to launch published interface compliant modules</description>
<className>nl.wldelft

.fews.system.plugin.generaladapter.GeneralAdapter</className>
</moduleDescriptor>

Table of Contents

 

.fews.system.plugin.generaladapter.GeneralAdapter</className>
</moduleDescriptor>

Table of Contents

Info
titleExecute activities requiring openJDK in 2018.02 and later

Since 2018.02, the Forecasting Shell and Operator Client software are shipped with a stripped-down JRE with only those java modules that the OC / FSS / CM client needs. This might cause module components such as adapters, forecast models and simulations that were perfectly running fine on the shipped JRE in 2017.02 or earlier to stop from working since additional modules might be required.

If this is the case, recommended options are to not try and resolve this in the Forecasting Shell launcher service, but to choose one of the following options:

  1. Configure the executeActivity -> command -> customJreDir.
  2. Configure the executeActivity -> environment variables to provide a PATH to the correct JRE version
  3. Supply the component with its own stripped down embedded JRE version and use a wrapper script that is able to find the correct java runtime image.

General Adapter Configuration

...

HBV_Maas_Forecast 1.00 default.xml

HBV_Maas_Forecast

File name for the HBV_Maas_Forecast configuration.

1.00

Version number

default

Flag to indicate the version is the default configuration (otherwise omitted).


Figure 66 Elements of the General Adapter configuration

...

Different module instance id used for finding cold state (when warm state is configured but can't be found, or always when cold state is configured)

backupWarmStateModuleInstanceId

Different module instance id used for finding warm state, when original warm state can't be found

adjustTimeSeriesStartTime

...

Exports rating curves to pi_ratingcurves.xml file. The rating curves with the start time within the GeneralAdapter run period will be exported.

 
Figure 1 Elements of the exportRatingCurveActivity configuration

...

File name of the file to be exported. Always placed into the export dir.

onlyLatestAvailable

If  'onlyLatestAvailable'  is used, then only the latest available rating curve in the run period will be exported. By default all rating curves within the run period are exported

linearTableStageResolution

...

Several variables are available to be used as an argument to an external program or in the exportCustomFormatRunFileActivity. You can use in any filename or directory the properties from the global.properties file or the next internal variables:

  • TEMP_DIR.  The %TEMP_DIR% variable is an internal variable which points to a unique temporary directory which is created in the $REGION_HOME$/Temp and which will be removed afterwards.
  • ROOT_DIR
  • WORK_DIR
  • ENSEMBLE_MEMBER_ID
  • ENSEMBLE_MEMBER_INDEX
  • TIME0
  • START_DATE_TIME (the START_DATE_TIME variable only works in an importStateActivity (since 2014.02) and inside a template file for an exportCustomFormatRunFileActivity (since 2013.02)).
  • END_DATE_TIME (the END_DATE_TIME variable only works in an importStateActivity (since 2014.02) and inside a template file for an exportCustomFormatRunFileActivity (since 2013.02)).
  • CURRENT_TIME (since 2015.01)
  • TASK_ID
  • TASK_RUN_ID
  • TASK_RUN_ID_FOR_PATH
  • TASK_DESCRIPTION
  • TASK_USER_ID
  • WHAT_IF_ID (Since 2016.02 build 65440)
  • WHAT_IF_NAME (Since 2016.02 build 69419)
  • TIME_ZONE_OFFSET_SECONDS

...