skip to main content
Water Right
Methods in this category specify whether the account has a water right.
* None
No water right is defined for this account.
* Priority Right
When selected, this account will have a water right. Selecting this method is identical to checking the Has Priority Date toggle in the account configuration, General tab.
Slots Specific to This Method
 Appropriation Request
Type: Series slot
Units: Flow
Alternate Units: Volume
Description: A result of the water rights allocation solver. This slot gets the value of the initial request slot, since an instream flow account has no other legal or physical constraints that can reduce the appropriation request.
I/O: Rule
 Available Allocatable Flow
Type: Series Slot
Units: Flow
Alternate Units: Volume
Description: Upper bound on the amount of water an instream flow account can call from a junior account. An instream flow account is not allowed to call more than the allocatable flow in the channel, which quantity is saved in this slot by the water rights solver in SolveWaterRights when the solver’s controlling date is senior to this account, and is used by the water rights solver SolveWaterRights when the solver’s controlling date is junior to this account. The quantity saved in this slot is the outflow from the instream flow account’s sibling passthrough account having the water type given to the solver to identify the allocatable flow supply chain.
I/O: Rule
 Temp Reason
Type: Series slot
Units: None
Alternate Units: NA
Description: This temporary slot encodes diagnostic information about the reason why the account is allocated the amount that it is given by the water rights solver. Table 2.4 lists the possible reasons. Some of these values may be OR-ed together. This encoding is subject to change at any time.
I/O: Output only
 
Table 2.4  SolveWaterRights and SolveWaterRightsWithLags allocation reasons
Temp Reason
Allocation is limited by
Description
0,000,000,001
Initial Request, which was specified.
The Initial Request was specified and limited the allocation.
0,000,000,004
Initial Request, which was computed by Reference Level
The Initial Request was computed by looking at the reference level of the specified reservoir
0,000,000,040
Max Accrual
Not yet implemented.
0,000,000,400
The available water in the supply chain.
This is the flow in the Allocatable Flow supply chain after higher-priority rights have been satisfied.
0,000,xxx,000
 
A downstream senior placed a call.
A downstream senior’s call further restricted the allocation (below the Appropriation Request). The priority number of the senior appears in these digits, except that if the priority is zero, the digits show 999.
 
0,xxx,000,000
A junior placed a call on a senior subordinate.
The priority number of the calling junior appears in these digits. The junior cannot have priority zero.
1,000,000,000
A junior placed a call on a senior subordinate instream flow right.
Because of subordinate relationship, shortage was ignored.
Method Details 
The water rights solver rule function, SolveWaterRights (or SolveWaterRightsWithLags), assigns a flow to a supply for a water right; this flow might be less than is requested in the Appropriation Request slot. Table 2.4 describes the various reasons the solver allocates what it does.
Revised: 07/05/2022