Accounting
The following changes have been made to RiverWare accounting functionality.
Rio Grande-specific Object-level Accounting Methods (OLAMs)
Elephant Butte Gain Loss Method Changes
In the Reservoir Account Gain Loss category, the Elephant Butte Gain Loss method has been modified as follows.
• Evaporation and precipitation are now charged to all accounts with positive previous storage. Seepage is charged to the account named “RioGrande”.
• The Gain Loss is computed to reconcile the reservoir based on the following:
– The RioGrande account storage, whether positive or negative
– Any other account of water type RioGrande that has positive storage
This change modifies the accounting results when the Elephant Butte Gain Loss method is used.
See Elephant Butte and El Vado Gain Loss in Accounting for details.
Elephant Butte with RG Compact Method Removal
The Elephant Butte Loss with RG Compact method is no longer supported because it should not be used and could cause confusion if selected inadvertently. This method has been removed from the user interface and can no longer be selected. Models using this method are automatically switched to the Elephant Butte Gain Loss method, and a warning message is posted to diagnostics.
Water Rights Solver: Diagnostic
A water rights subbasin warning has been changed to a diagnostic message. The message indicates supplies were not cloned because one end is out of the subbasin.
Following is the old message:
“Cloning for rule: One end of supply is not in subbasin: River^River.Return Flow.River_Excess River to River River Div__dot__Supply”
The new diagnostic message is as follows:
“During cloning, one end of a supply was found to not be in the subbasin and will not be cloned. The supply is: River_Excess River to River River Div__dot__Supply”
You can now see these messages by selecting the Run Management, then Sim Obj diagnostic category with the computational subbasin object context selected.
Revised: 12/01/2020