Water Right
Methods in this category specify whether the account has a water right.
NoneNo water right is defined for this account
Priority RightWhen 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 is the allocatable flow that is the solver tries to allocate to this account.
I/O: Set by Rule
Links: No
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.3 lists the possible reasons. Some of these values may be OR-ed together. This encoding is subject to change at any time. Thus a value in the slot of 401 means the allocation was limited by the water in the supply chain (400) and the Initial Request was specified (1).
I/O: Output only
Links: No
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,003 | Initial Request, which was disaggregated by a subbasin. | The Initial Request was computed by a Computational Subbasin that disaggregated the request from Annual requests. |
0,000,000,005 | Max Permitted method was selected. | No allocation is made. The Appropriation Request reflects the allocation that might have been made had this method not been selected. |
0,000,000,010 | Min Bypass criteria | Min Bypass criteria are reflected in the Appropriation Request. |
0,000,000,040 | Max Accrual | Not yet implemented. |
0,000,000,050 | Max Legal Request | The initial request was larger than the Maximum Legal Request, so it was cutback to the Maximum Legal Request |
0,000,000,200 | Diversion Capacity at source. | |
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,000xxx,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 | Shortage ignored due to subordinate. | Because of subordinate relationship, shortage was ignored. |
Temp Available For Shared Priority
Type: Series slot
Units: Flow
Alternate Units: Volume
Description: A result of the water rights allocation solver. When the Share Proportionally with Limits method is selected in the Account Equal Priority Allocation method category on the computational subbasin, this slot is instantiated. If this account has a priority date equal to other accounts this slot is populated with the amount of water available to this account independently of the other shared priority accounts at the time water is allocated. This value is used in the calculations that ultimately allocate water to the shared accounts; see Water Rights Allocation for details.
I/O: Rule
Links: NO
Method Details
The value in the Appropriation Request slot does not reflect reductions in the allocation to prevent shorting downstream senior rights. It does reflect reductions based on legal constraints (such as minimum bypass) and physical constraints (such as the capacity of the physical diversion structure). See Diversion from Reach in Objects and Methods for additional information about the diversion capacity for the reach.
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.3 describes the reasons the solver allocates what it does.
Revised: 07/09/2023