• In the Water Right category, the Priority Right must be selected. This is the same as selecting the Has Priority Date toggle on the General tab of the Open Account (configuration) dialog. Specify a unique priority date.

• In the Initial Request category, select the Specify Initial Request, the Fill Conservation Pool, or the Fill Conservation Pool with Diversions method to specify how the initial water right is determined. In the Specify Initial Request method, the user can specify (via input, dmi, or rules) the Initial Request slot. If the Fill Conservation Pool method is selected, initial allocations to Storage Accounts are limited to that amount which will fill up the conservation pool on the reservoir. If the Fill Conservation Pool with Diversions method is selected, initial allocations to Storage Accounts are limited to that amount which will fill up the conservation pool on the reservoir and meet diversions totaling the sum of the Initial Requests of all direct diverters from the storage account. The total volume in all Storage Accounts on a reservoir contributes to the conservation pool volume, regardless of the ownership of the water in these accounts. For this reason, in order to prevent a single storage account from holding all the water in the conservation pool, the Conservation Pool Fill Factor category may be used. This category contains methods that allow a fraction of the conservation pool (and diversions) to be allocated, thereby reserving some for other accounts. See Initial Request for additional information.

• If lagged return flows entering the Storage Account are to be credited to the appropriation from allocatable flow, select the method Return Flow Credit in the Appropriation Request Adjustment category.

• Max Legal Request. This method allows the user to enter a value for the Initial Request that is larger than the legal right. This is useful if you are computing the Initial Request from aggregated or historical data. See Max Legal Request for details.

• Min Bypass. If there is a minimum bypass, select a method in the Min Bypass category. Currently available is the method Fraction of Flow Above Min. See Min Bypass for details on this method.

• There is no way for water to leave the allocatable flow supply chain from which this the water rights solver allocates other than through:

– The allocations made by the solver

– Gain Loss slot values which are output. This is accomplished by selecting the appropriate Gain Loss Coefficient method (see Gain Loss Coefficient) on passthrough accounts in the chain and then specifying the coefficient (either scalar, series or periodic) if desired. If Gain Loss slot values are not determined by a gain loss coefficient (that is, they are user input), the solver cannot solve upstream for cutbacks to upstream appropriations.

– In addition, inflows, outflows, non-appropriation transfers, and return flows are assumed to be non-negative throughout the supply chain and there are no existing diversions or (appropriation) transfers to accounts that will not be re-allocated by this method. Slot inflow values may be negative only to the extent that they do not produce negative outflows anywhere in the supply chain at any time during the solution. See the note below for the only exception to this.

• At Instream Flow Accounts, no sibling accounts have negative inflows. If they do, this method cannot solve upstream for cutbacks to upstream appropriations. See the note below for the only exception to this.

• Because the solver relies on the account-solving infrastructure, certain required input values must be known on the accounts so that the supply chain can solve before this method is called. The required knows for account solution are documented in the Accounting reference documentation. See About Accounts for details. Following is a summary of the slot requirements for this solver to work.

– On Passthrough and Instream Flow Accounts: Inflow slot values will be propagated from above, except for those at the heads of the tributaries of the allocatable flow supply chain, which do not require Inflow slot values.

– Passthrough accounts not on a reservoir: Slot Inflow must be defined. Gain Loss slot values may not be user input (they may be Output). But a gain loss coefficient (either scalar, series, or periodic value based on selected method) may be defined in which case, if Gain Loss is NaN, the passthrough accounts will compute the Gain Loss slot values.

– Passthrough accounts on a reservoir with storage allowed: Inflow and Slot Inflow must be defined.

– Passthrough accounts on a reservoir with storage not allowed: Slot Inflow must be defined.

– Diversion accounts: Nothing required a priori.

– Storage accounts: Slot Inflow and Gain Loss must be defined.

– Instream flow accounts: Nothing else required.

– If passthrough accounts at the tops of the tributaries’ allocatable flow supply chain can solve (by virtue of having Slot Inflows, these accounts will produce the flow slot values required for the rest of the supply chain to solve before this method is called.

• Adding an object to the model and forgetting to put it into the subbasin.

• The subbasin is disabled. Use Workspace, then Open Computational Subbasin, followed by Subbasin, then Enable Subbasin.

• Model uses the wrong controller. Set your controller to Inline Rulebased Simulation and Accounting.

• Unintended convergence criteria on account slots. Check your convergence criteria.

• Wrong units on account slots. Make sure all the units are what you expect.

• Lags on reaches do not match lags on their accounts.

• Forgetting to set the water type on the supplying account of a water right (at the point of appropriation from the stream). The water type must be set at each point of appropriation from the stream. If you see an Appropriation Request slot value being calculated for a right, but no allocation made to that right (not even an allocation of zero), this is likely to be the reason. Use the visualization tools on the accounting workspace (that is, Account Groups) to display accounts with a given water type, as in Figure 6.1. Then change any incorrect accounts to the right water type.

• Having more than one account on an object with the allocatable flow supply type. The results are undefined when this is the case. There is one exception, for offstream diversions (see Linking Accounts for descriptions), the Diversion object can have multiple passthrough accounts with the allocatable flow supply type.

• Having supplies that enter or leave the allocation subbasin but contain allocatable water. Use the diagnostics described in Using Diagnostics with the Solvers to print messages about these supplies when the subbasin is cloned.

• User-input data for allocation requests was put into the wrong slot; it should go into Initial Request; not Appropriation Request. The Appropriation Request slot is for outputs of the solution method; this is where the method writes the request as constrained by the state of the system at priority time; that is,, after senior accounts have been satisfied.

• Attempting to use Fill Conservation Pool or Fill Conservation Pool with Diversions method on a Storage Account without setting up the necessary methods and data on the underlying Reservoir object.

• Too many hops from the allocatable flow (stream) to the water right account.

• Supplying a reservoir with project water before the solver is called, thus reducing the appropriation to storage.

• Failing to clear supply chains from non-allocatable water before calling the solver. These allocations may reduce allocations to storage from allocatable water, and they may reduce diversions where diversion capacity is limiting.

• Not providing enough information for all accounts in the subbasin to solve once before the solver rule executes. See the required data in the previous section. This data can be specified by Inputs, Rules, or object-level accounting methods. See Object-level Accounting Methods (OLAMs) for details. In most models, you probably want to use the following methods:

– Zero Slot Inflows method for most objects. This should be configured to execute at “Beg of the Run”. See Zero Slot Inflows for details.

– Copy Slot to Slot Inflows method for local inflow reaches, control points and reservoirs. This should be configured to execute at “Beg of the Run” or beginning of timestep depending on when the local inflows are known. See Copy Slot to Slot Inflows for details.

• Show All Water Account Subordination Relationships. Show only those accounts involved in a subordination relationship

• Show All Water Accounts and their Subordinate Accounts. Show all accounts on the left side and their subordinate accounts on the right. Accounts may be repeated.

• Show All Water Accounts and their Dominant Accounts. Show all accounts on the right side and their dominant accounts on the left side. Accounts may be repeated.