Laserfiche WebLink
<br />I" <br /> <br />, <br /> <br />0003~ll <br /> <br />Operati()n~ Code Overview <br /> <br />Solve [CRAMHOOK.MOOJ <br /> <br />The Solve procedure was described above. It is called again here to get' a solution for <br />the amount of project water which could be delivered to the shorted demands. <br /> <br />SetU pBlueMesa Exc ha ngeFo rFlowRoutingStep [DO PROJCT. MOD] <br /> <br />Before the project allocation step. procedure SetUpTaylorParkProjectStepReleases <br />connected and opened an extension-cord arc between Tavlor Park and Blue Mesa reservoirs <br />. . <br />with a capacity delivered by the tlow-regulation criteria apprllved in the "Refill Decree". The <br />concept is that this release of storage water from Taylor Park will be balanced by the addition <br />of an equal volume of "exchange credits" for the UVWUA in Blue Mesa Reservoir. During <br />the project allocation step. this amount would actually be transferred from Taylor Park into <br />Blue Mesa if there were storage capacity available. Since the UVWUA will be given <br />"exchange credits" in Blue Mesa (and since the model is intended to support studies of various <br />policies regarding the allocation of water stored in Blue Mesa) it is assumed that the UVWUA <br />water released from Taylor Park should be "shepherded" into Blue Mesa. <br /> <br />SetUp UVPBlueMesa ReleaseForFlowRouti ngStep [DO PROJCT. MOD] <br /> <br />Following the solution llf the Project Deliveries "allocation step" this procedure <br />recontigures network extension curds. sets capacities lelI' the allocated releases and deliveries, <br />and opens or unfreezes the normal physical pathways through which the project delivery flows <br />would be routed. Since we cannot be sure that all allocated tlows will reach their destinations. <br />the allocated amounts are saved on the TaylorParkGates of the individual canals by setting arc <br />capacities and ranks rather than by setting minimum Ilow constraints. <br /> <br />SetUpUVPR id gwayForFlowRouti ngStep [DO PROJCT. MOD] <br /> <br />This procedure is similar tll SetUpBlueMesaExchangeForFlowRoutingStep; it sets the <br />capacities and rank parameters on the Ridgway Project Release gate and unfreezes the bypass <br />and controlled outtlow links. It also reattaches the demands to their point of diversion nodes <br />and assigns them high ranks in the network to draw the water out of the reservoir. <br /> <br />SetUpOtherProjectsForFlowRoutingStep [DOPROJCT .MOO] <br /> <br />This procedure utilizes the "order iists" which were built by procedure <br />FindAnyProjectDemandsWithShortages. The lists contain only those demands which had <br />shortages prior to the current project deliveries step and which are associated with a project <br />(i.e. a supplemental source of supply). The shorted demands are organized as sub-lists of the <br />full lists of demands assllciated with each reservoir. The purpose of this organization is to <br />enable this procedure. as well as others. to work with the smallest set of demands possible <br />(only those to which project deliveries should be made). It should be noted that the three <br />reservoirs, Taylor Park, Blue Mesa and Ridgway in which the UVP may have water stored, <br />can each have another, independent set of demands aftil iated with it in a "project" relationship. <br /> <br />7 <br />