skip to main content
Objects and Methods : Computational Subbasin : User Methods : Key Control Point Max Release
Key Control Point Max Release
This category appears only if the Operating Level Balancing method is selected in the Flood Control category.
Note:  This method category and its methods are for convenience of algorithm development, and they may not be available in the future.
Each reservoir that is subject to a key control point may be assigned a Max Flood Control Release value by the key control point balancing method. This method determines whether the flood control uses that value in its computations. (If the value is not a valid, it is ignored, in any case.)
The Max Flood Control Release is a value determined by the Key Control Point Balancing method. It is applied on all but the final pass of the algorithm. See the discussion and example in the subsection Constraints of the Full Reservoir.
* Max Release Applies
This is the default method.
The Max Flood Control Release is applied as an upper bound on each timestep of the forecast period, on all passes but the last.
The effect of applying this maximum is mixed. On one hand, it tends to allow each subject reservoir to release something, even if at the expense of a higher-priority reservoir. This may help to smooth the release schedules for reservoirs, to avoid oscillating behavior, in which on one day, RA releases but RB does not, and on the following day RB releases, while RA does not, then RA releases, then RB releases, and so on. On the other hand, it may subvert the principle of giving priority to the fuller reservoirs.
When a reservoir’s maximum is zero, the flood control algorithm bypasses most of the work associated with projecting a release schedule during all but the last pass.
There are no slots specific to this method.
* Max Release Ignored
The value is ignored. See Max Release Applies for details.
There are no slots specific to this method.
Revised: 01/11/2023