Initialization Rules are a set of RPL rules associated with the model which can be executed as part of run initialization to set up data for the run. Initialization Rules provide a complement to user inputs and execution of DMIs.

Unlike other rules which can only set series slots, initialization rules can be used to set Table Slots and Scalar Slots.

This section describes the applicability and use of Initialization Rules. See RPL User Interface for details on the user interface for Initialization Rules and other RPL sets.

Each method for providing data to a simulation is suited to different modeling scenarios. For situations in which there are a small number of inputs that don’t change frequently, interactive setting of input values is often the simplest approach. However, when this process would be time-consuming or error-prone, it is preferable to automate the setting of user inputs. Input DMIs provide a flexible way of accomplishing this by providing mechanisms for communication between RiverWare and external programs (usually databases). If there is computational logic involved in this process, e.g., if the data need to be massaged to remove outliers, then this logic must somehow be embedded in the external DMI program. On the other hand, using initialization rules to accomplish the same task allows this logic to be viewed and edited from within RiverWare, often improving the clarity and ease of maintenance of the model.

Initialization Rules also differ from DMIs in that in the context of a RBS simulation, they can be used to provide default values which the policy can then override. To illustrate a scenario in which this might be useful, consider a run in which some quantity is generally assumed to be zero, but which can take on non-zero values under some conditions. One strategy for modeling this situation is to set the relevant values to zero using low priority rules with execution constraints that cause them to execute only on the first timestep. Alternatively, Initialization Rules accomplish this same behavior with less user effort (no execution constraints are necessary) and with the additional advantage that these rules are organized separately from the policy (if there is one). In fact, most RBS rules which are constrained to execute only on the first timestep are likely to be more appropriately included with the Initialization Rules.

Another important distinction between Initialization Rules and policy (rules) is that the former are executed before data checking at the beginning of the run. Thus, Initialization Rules can be used to set values such as initial Storage or Pool Elevation on a reservoir, whereas RBS rules execute only after data checking and so could not be used to give these slots reasonable values. Further, unlike other rules which can only set series slots, initialization rules can be used to set table and scalar slots.

This topic describes how to use initialization rules.

From the workspace, use the Policy, then Initialization Rules RPL Set menu.

The set is saved in the model file. The Initialization Rules Set Editor dialog does have a File, then Save Initialization Rules Set As menu item to save the initialization rules to a file. A File, then Replace Initialization Rules Set from File menu item allows the initialization rules set to be replaced by the contents of a specified file. These menu items allow an initialization rules set to be moved between models via a file. However there is only a single instance of initialization rules in a model and this set is still saved and loaded with the model file. You can also use the File, then Clear Set to remove all items in the initialization set.

The rules are executed during the initialization phase of Simulation and Rulebased simulation runs (including accounting) and Optimization runs. For Simulation/Rulebased, they are executed after values are cleared and inputs are registered but before beginning of run checks on all objects.

See Simulation Controller in Solution Approaches for details on the ordering for simulation.

See Simulation/Rules Interaction in Solution Approaches for rulebased simulation.

See How the Accounting System Solves in Accounting for accounting.

See Initialization Rules in Optimization for information on Initialization Rules in Optimization.

The Initialization Rules are executed in Index order based on the specified Agenda Order. To see the order, select View, then Show Advanced Properties.

Initialization rules can set series slots, table slots, scalar slots, and periodic slots.

No, initialization rules execute once and do not re-execute even if dependencies change.

No, the Initialization rules are organized by Index as shown on the RPL set editor.

Series values set by Initialization Rules are given one of the following flags/priorities as configured through the Set Value Flag menu on each Initialization Rule:

When the Initialization Rules set contains at least one rule, then the Run Control Dialog displays a check box labeled Execute Initialization Rules, which controls whether or not to execute the Initialization runs during the initialization phase of runs. Clear this check box to disable the Initialization Rules.

For an Optimization run, the toggle/flag is labeled Execute Initialization rules before Optimization Run.

Note, the toggles are separate for each controller. They can be on for one controller but off for another controller. See Set Init. Rules Exec. Flag in Automation Tools for a script action that sets these flags.

Tooltips on the series slot values display which Initialization Rule (or RBS rule or DMI) set that value. See the following figure. See Series Slots in User Interface for details on these tooltips.To open that rule, right-click and choose Open Init Rule #.

The RPL debugger can be used with Initialization Rules. Also, the following diagnostic categories in the Rulebased Simulation and Simulation settings dialog control diagnostics for the Initialization Rules:

See Types of RPL Debugging and Analysis in Debugging and Analysis for details on debugging and analysis of RPL sets.