Laserfiche WebLink
<br />Network Data <br /> <br />DiversiO!l~ " i' J" . <br />tJ~ '.'U <br /> <br />4.5.7 Site efficiency table (% consumed): Required. This is the percentage of the <br />site delivery which will actually be consumed, and thereby lost to the system. The difference between <br />the site delivery and the amount actually consumed is called 'site loss', and is available for return to <br />the system. Any table val~1 of 100.0 or Jll.Q!:e will produce erroneous results. <br /> <br />. <br />4.5.8 % of canal (delivery) loss to return flow: Constant. This percentage of the <br />canal loss will return to the system. The value may range from 0 to 100, depending on whether all, <br />some or none of the loss goes into recharging ground water, servicing weeds, etc. and is lost from the <br />system forever. <br /> <br />4.5.9 % of site loss to return flow: Constant. This percentage of the site loss will <br />return to the system. The value may range from 0 to 100, depending on whether all, some or none <br />of the loss goes into recharging ground water, servicing weeds, etc. and is lost from the system <br />forever. <br /> <br />4.5.10 Diversion reauirement: <br />Requirements may be one of five types: <br />(1) Irrigation requirements are specified by a statement of the area to be irrigated (in acres, <br />hectares, etc.) and a monthly unit requirement table which gives the depth of water required <br />per unit area. The product of these two numbers gives the volume of water consumed per <br />month; HYDROSS divides this by the site efficiency to get the site delivery, and divides the <br />site delivery by the canal efficiency to get the gross diversion requirement. Note that a zero <br />efficiency, site or canal, will cause the computation to blow up. <br />(2) An M&I requirement is given by a monthly table of gross diversion requirements. <br />(3) An offstream storage requirement is specified by the station number of a target reservoir. <br />HYDROSS calculates the site delivery as the amount of water (if any) needed to bring the <br />reservoir up to its stated target content (see paragraph 4.2 [page 24]), and divides by the <br />canal efficiency to determine the gross diversion requirement. <br />(4) Population requirements are calculated just like irrigation requirements, with the units to be <br />'irrigated' expressed as 'each', and the unit requirement expressed as the volume per month <br />per unit. . <br />(5) A bypass diversion is expressed by a monthly table of flows; HYDROSS will atte!Tlpt to <br />divert all water over the table flow value. <br /> <br />4.5.11 Canal caoacitv: Optional. Constant. If this value is present, HYDROSS will <br />not divert water in excess of this value (and will declare a shortage). If this value is omitted or zero, <br />there will be no such constraint and HYDROSS will attempt to deliver the required flow as calculated <br />above. <br /> <br />4.5.l2.Maximum annual diversion: Optional. Constant. If this value is present, <br />HYDROSS will keep a running total of the amount diverted (year-to-date) and stop diverting water <br />when the total reaches this amount. If this value is omitted or zero, there will be no such constraint. <br /> <br />March 25, 1991 <br /> <br />HYDROSS 4.1 <br /> <br />Page 27 <br />