Laserfiche WebLink
<br />I'l,,""" ~7 <br />t. :J t,... .. ;J <br /> <br />"I <br />H <br /> <br />July 7, 1993 <br /> <br />Gunnison Planning Model - Info Theme No.2 <br /> <br />Information Related to Demands <br /> <br />1. All Demands. Before and after the water rights step, the ops <br />code will need to open and close "water rights gates" and save <br />and unsave flows through those gates for all demands, including <br />both the separate points of use along canals and the demands <br />which divert directly from streams. (Similar operations will be <br />performed upon reservoirs, minimum streamflow rights, and <br />hardwired structures, such as canal headgates, the Gunnison <br />Tunnel, etc.) <br /> <br /> <br />The notion of a "demand" is similar to that of a "ditch." Usually "demand" <br />bundles together the means for getting water from a stream (water rights, project, etc.) <br />with the end disposition of the water diverted (consumption, return flows, etc.) In the <br />planning model, all potential and most existing demands will have this tightly-coupled <br />relationship between the diversion and the disposition. <br /> <br />In other cases, which will be hard-wired, the diversion-related attributes of a <br />demand may be separated from the consumption/shortage/return-flow attributes by a <br />special delivery system with a variety of customized rules. Three demand sub-systems <br />within the planning model which have non-standard characteristics are the <br />Uncompahgre Valley Project (see Info Theme No.7), Project 7 (see Info Theme No. <br />S), and the Cimarron Canal (see Info Theme No.3). <br /> <br />Ops Code: The Cramhook code needs to be able to build lists of the demands <br />which fall into several different (but not mutually exclusive) categories, in order to <br />perform various operations at appropriate points in the solution step sequence. The <br />record for each demand in each list will include the link numbers upon which the <br />corresponding operations will be performed: <br /> <br />2. Demands Affiliated with Projects. The ops code will check for <br />shortages and make a variety of network connection changes and <br />gate openings and closings for those individual demands where <br />shortages were found, at canal headgates and the Gunnison <br />Tunnel and at the corresponding project reservoirs. <br /> <br />3. Demands to be Operated During the Augmentation Step. <br />Similar to projects--check for shortages and open and close gates, <br />but without changing network connections. <br /> <br />4. Demands to be Operated During the Replacement Step. <br />Identical to Augmentation. <br /> <br />User Interface: The user interface will have to deal with many aspects of <br />demands that are unknown to or simply taken for granted by the operations code. <br />These categories of information include: <br /> <br />> <br /> <br />;I ~ <br /> <br />: ,",^~i~. :.. ~ <br /> <br />, . . .~_~; :,1l1~,,~,- ~ <br />