The following enhancements to the RiverWare simulation objects are described briefly. The user is encouraged to consult the Simulation Objects Documentation in the RiverWare Help for more detailed descriptions of the enhancements to the objects and their methods.

A new category was added to the reservoir objects named Low Flow Releases. Within this category there is the default no-action method and the Enable Low Flow Releases method. The Enable Low Flow Releases method is used with the MeetLowFlowRequirement predefined RPL function used to meet low flow requirements at a downstream control point by releasing from one or more reservoirs.

A new category called Operating Levels was added to the reservoir objects. In this method, the user can select the Conservation and Flood Pools method if the user wishes to define flood and conservation pools on the reservoir. If not, the default no-action None method can be used.

A new slot, Diversion Capacity, was added as a general slot to the reservoir objects.

The slot Hydrologic Inflow Forecast was added as a dispatch slot. In certain models, the Hydrologic Inflow Forecast was calculated throughout the forecast period but did not force the reservoir to dispatch given the new information. This could change results in models that use the Geometric Recession or Exponential Recession in the Generate Forecast Hydrology category.

Two new methods were added to the Bifurcation Solution Direction category: Solve Outflow1 Only and Solve Outflow2 Only. These two methods limit the available dispatch methods so the bifurcation will only solve in one direction.

Negative outflow warnings were removed from the bifurcation object.

On the control point, a new category called Low Flow Requirement was added to allow the user to determine the required low flow. The user can select the Reservoir Level Lookup method to relate the low flow requirement to the level of a reservoir. Or, in the Low Flow Periodic Lookup method, the user can input a periodic table of low flow requirements.

A new seepage method, Head Based Seepage, was added to the Canal Seepage category. This new method determines the seepage from the canal as the function of water surface elevation, water table elevation, canal bed elevation, and conductance from the canal.

A new method was added to the Diversion Request Calculation called Periodic Diversion Requests. This method allows the user to input a periodic slot containing the diversion requests.

A new method was added to the Diversion Request Calculation called Reservoir Level Lookup. This method allows the user to input a periodic slot that relates the Diversion Request to the level of a specified reservoir.

A new category was added to the Diversion Object called Diversion Object Solution Direction. In this category, there is the default method Solve For Outflows and the new Solve Given Outflows. Solve For Outflows provides the previous functionality. If the user selects, Solve Given Outflow, the available dispatch method become SolveDiversionGivenOutflow.

This new dispatch method is only available when the Solve Given Outflow is selected in the Diversion Object Solution Direction category. This dispatch method requires that the total Multi Outflow is known and the Diversion and Diversion Request are unknown.

Diversion Shortage was added as a general slot to the Diversion Object. Calculated in the dispatch method, the Diversion shortage is the difference between the Diversion and Diversion Request.

A new method category, Evapotranspiration, was created to simulate evapotranspiration directly from the groundwater. It contains the following methods which specify how the user wishes to parameterize the evaporation calculation: None, Input ET Rate, Input ET Volume, and Elevation ET Table. This method is available for either the Single Groundwater or Connected Groundwater objects.

A new method category, Groundwater Solution Type, was added to the groundwater object. The default method is called Single Groundwater Object and represent the previous functionality. A new method, Connected Groundwater Objects, was added to allow the user to model groundwater objects that are connected to other groundwater objects.

This method allows the user to specify the number and location of the connected groundwater objects with respect to the current object. This new method category contains 14 user methods representing all combinations of Upstream, Downstream, Left and Right. For example a groundwater object may be connected to only one other groundwater object which is upstream. Or it may be connected to four other groundwater objects which are upstream, downstream and to the left and right. A method called No Connected Groundwater Objects method category is also available to specify that there is no connection to other groundwater objects.

A new method, Head Based Percolation, was added to the GW Deep Percolation category to allow the user to determine percolation as a function of groundwater elevation. This method is only available if the Connected Groundwater Objects method is selected.

A new method was added to the Pumping Calc category called Input Pumped Flow. It models groundwater pumping by removing a given amount of water from storage. This method is dependent on the selection of the Connected Groundwater Objects in the GW Solution Type category

This dispatch method is used exclusively when the Connected Groundwater Objects method is selected. The solveGWMB_givenPreviousElevations dispatch method will compute the current Storage and Elevation values based on the previous elevations and any other selected mass balance variables.

The Stage Table Lookup user method was modified on the Reach object. Previously, the Stage slot in this method was set equal to whichever value was known, Inflow Stage or Outflow Stage (as calculated using inflow and outflow stage tables). If both values were known, it is set as the average of the two.

In the revision, the stage slot is set equal to an average value whenever possible. If inflow and outflow stage values are known for the current time step, the stage is set as the average of these two values. If one of the values is not known for the current time step, a value is sought at the previous time step. The stage is then set as the average of a current time step stage value (either inflow or outflow) and the previous time step stage value (either inflow or outflow, corresponding to whichever is not available at the current time step). If a value from the previous time step is still not available, at the first time step of a model run, for example, no averaging is done. The stage slot value is set equal to whichever value is known at the current time step.

A new seepage method, Head Based Seepage, was added to the Seepage Calc category. This new method, only available if the Stage Table Look Up method is selected, determines the seepage from the reach as a function of stage, water table elevation, streambed elevation, and conductance from the reach.

A new method called Periodic Minimum Bypass was added to the Minimum Diversion Bypass category. It allows the user to input a periodic slot that contains the Minimum Bypass.

A new slot, Diversion Capacity was added to the Reach. It is dependent on having either the Available for Diversion or Head Based Diversion method selected.

A new category called Irrigation Acreage and Evapotranspiration Rates Category was added to the Water User. This category, available only when the Irrigation Requests method is selected in the Diversion and Depletion Request user category, allows the user to specify how they wish to parameterize the Irrigated Area and Evapotranspiration Rate slots. The Input Acreage and Rates method, the default, mirrors the previous functionality in the Irrigation Requests method where the user inputs a time series of Irrigated Area and Evapotranspiration Rates. The Aggregate Acreage and Rates method allows the user to input Crop-specific Irrigated Area and Crop-specific Evapotranspiration Rates. The method then sums the Crop-specific Irrigated Area to get the total Irrigated Area and averages (weighted by area) the Crop-specific Evapotranspiration Rate to get the Evapotranspiration Rate.

The Irrigated Area GW Return Rate method was added to the returnFlowSplitCalculation category on the water user. This method allows the user to split return flows between the surface water and groundwater as a function of diversion, diversion request, groundwater return rate, and irrigated area. The method is dependent on having the Irrigation Requests method selected in the Diversion and Depletion Request category.

A new method category was added to the water user called Multiple Supply Sources. Aside from the default “None” method, it has a single selectable method called Multiple Supply Reservoirs. This method instantiates the Supply From Reservoirs slot and Maximum Delivery Rates slots.The Supply From Reservoirs slot should be linked to the Multi Outflow slot of each supplying diversion object. It will be used to specify the diversion objects that act as supplies, and it will hold the data returned by the ComputeReservoirDiversions RPL function that computes the diversions from each reservoir to meet a demand requirement.

Two new methods were added to the Diversion and Depletion Request Calculation category, Periodic Diversion Request and Reservoir Level Lookup. The Periodic Diversion Request calculates Diversion Requested using a periodic slot. The Reservoir Level Lookup method calculates the Diversion Requested as a function a specified reservoir’s Operating Level.

A new method category called Limit Diversion was added to the water user. Aside from the default “None” method, the category has a user selectable method called Limit By Reservoir Level. This method performs no calculations directly but will add the Demand Reservoir slot. If this method is selected, the RPL function, ComputeReservoirDiversions which computes the Supply From Reservoirs slot, will not compute a diversion if the Demand Reservoir is in the flood pool or if its level is higher than the supply reservoir.