Following are special attention notes, indicating that functionality has changed that requires you to update models or that results may differ. If you have any questions, contact: riverware-support@colorado.edu

Certain objects like the Reach, Confluence, and Control Point determine the first allowable timestep at which they can dispatch by searching upstream to find the earliest input value. Previously, if the search encountered a Stream Gage, it would stop the search. Now the search continues upstream through the gage. As a result, some downstream objects may be able to dispatch earlier if there is a gage upstream and there are inputs on or upstream of the gage. In some models this can lead to errors if the user has input values on the gage or other objects to solve at these pre-simulation timesteps. Often clearing the inputs is all that is required. The values will propagate from upstream.

The license manager was upgraded to a newer version. For floating licenses, you must restart the license server with the newer version. See License Manager Upgrade for instructions.

The Flow Tables and Flow vs. Power Table method was modified to use the Min Turbine Release at Max Generation as its constraining value. This is obtained from the Flow vs Power Table by finding the max power and then using the corresponding flow. More information is available Inline Power Plant - Flow Tables and Flow vs Power Tables method.

The semantics for the slot Min Value and Max Value were changed to Lower Bound and Upper Bound as described Min/Max Changed to Bounds. In addition, warning messages that values are outside of these bounds are no longer posted by default. If you wish to see these warning messages, check the Warn when Values are out of Bounds toggle in the Run Parameters as described Warn when Values are out of Bounds in User Interface.

Time Aggregation Series Slots were enhanced to better calculate averages for monthly flows that are aggregated to an annual timestep. Results for these calculations will change. In addition, slots with FLOW or VELOCITY unit types (per time and/or rate types) can not use the Sum function as this aggregation does not make sense. See Modifications to Aggregation Computations.