The following changes have been made to RiverWare simulation objects.

On the following slots, the convergence criteria was changed within the code to “None” and cannot be changed by the user:

The criteria to reset these slots is now based on the convergence criteria of the Storage slot. If Storage changes such that it will be reset, then the Head/Elevation slots will be reset as well. If Storage is within convergence and not reset, then no attempt is made to reset the Head/Elevation slots

The Head/Elevation results should now track directly with the Storage slot. That is, any change in Storage, results in a change in Head/Elevation. Because of this new approach, groundwater and aquifer objects that redispatch could produce different, corrected, results.

See General Slots in Objects and Methods and Head Based Groundwater Grid in Objects and Methodsfor details.

The Aquifer object now checks that conductance values on adjacent objects have the same value. This ensures that mass is neither lost nor gained as water flows from one object to the next.

See Aquifer in Objects and Methods for details.

Within the Compute Conductance method, the following groundwater slots have been assigned shorter, more consistent names, as follows:

Existing model files, including links and SCTs, are automatically updated with the new names. A warning message is posted to diagnostics alerting you to the change. You must update all RPL expressions and DMIs that reference these slots.

See Compute Conductance in Objects and Methods for details.

The Initialize Flow Slots for Routing computational subbasin method has been improved to work with five additional reach routing methods, as follows:

See Initialize Flow Slots for Routing in Objects and Methods for details.

The Specified Adjusted Capacity slot has been added to the Generator object. You can optionally specify this value as a reduced power request for the generator.

See Generator in Objects and Methods for details.

Previously, warnings were posted for Impulse and Step Response routing methods when the routed flow was not known. For consistency with other RiverWare operations that do not issue a warning message when there is no value, these messages have been modified from Warnings to Diagnostics, using the User Method diagnostic category.