Laserfiche WebLink
<br />~0202i <br /> <br />Basic Concepts <br /> <br />Demands <br /> <br />3.2.3 Diversions: A diversion demand takes water from the stream and, at least <br />potentially, denies the water to other users with a later priority date. This is where the priority <br />scheme, based on water right dates, comes in. <br />A diversion may have a natural water right, or a project water right, or a natural water right <br />with a supplemental project water right. If it has both water rights, the date of the supplemental right <br />need not be the same as the date for the natural water right. Four-digit numbers are used to represent <br />the water right date (0001 through 9999). <br />A diversion with a natural water right may take only natural water which will not be used by <br />a higher priority (earlier date) natural demand, diversion, or IFR downstream. <br />A diversion with a project water right may take project water which will not be used by a <br />higher priority project demand (diversion or IFR) downstream; or it may take natural water which <br />will not be used downstream by any natural demand (of any date) or by a higher priority project <br />demand; or it may call for the release of stored (project) water. <br />A diversion with both natural and project dates first attempts to satisfy its requirement as a <br />natural right, then tries to make up the shortage (if any) as a project right. <br /> <br />3.2.4 Storal!e Demand: A storage demand is similar to a project diversion demand in <br />that water is withdrawn from the stream. <br />This demand is hard-wired into the program, and needs no user specification. The water <br />right date assigned here is 9999, the lowest possible priority. .:. , <br />A reservoir will only store water which would otherwise be wasted, and it will all of that <br />water it can hold. <br /> <br />3.3 Station Diagrams <br />You will need to be thoroughly familiar with the station diagrams in Appendix C [Page 66] to <br />understand the concepts of HYDROSS. <br />HYDROSS does not use linear programming or other simultaneous solution techniques. It <br />operates on the data in a strict sequential order in time (results for one month depend on the system <br />state at the end of the previous month), space (results at one station depend on what is happening <br />upstream and/or downstream), and priority (early water right dates are allowed water before later <br />dates). <br />There is also a mini-scheme at each station which fixes the order in which we will consider <br />what happens at the station. The mini-scheme is illustrated in the station diagrams. <br />The three components of each diagram (further discussed below) are: <br />Inflow <br />Station Activity <br />Outflow <br /> <br />Page 16 <br /> <br />HYDROSS 4.1 <br /> <br />March 25, 1991 <br />