Laserfiche WebLink
<br />3Dj~,j7 <br /> <br />9, Specifying Return Flow Points. The name of the diversion appears <br />on the diagram near the head of the arrow. The user is prompted to, <br />"Choose return-jlow points for Big Bucks Acres by clicking on <br />highlighted nodes." The user clicks first on the node immediately <br />downstream of the diversion. He is prompted to indicate where the tail <br />of the return-flow arrow should be. When he does so, an arrow <br />labeled "Big Bucks Acres RF #1" appears on the screen. The reader <br />scrolls the diagram and clicks on the node at the mouth of Ohio Creek, <br />and the process repeats. <br /> <br />10. Entering Demand and Efficiency Data. A data-entry form appears <br />with two columns of twelve blanks each, the first column for monthly <br />diversion amounts and the second for the fractions consumed. The <br />user is prompted to enter the data, after which he pushes the "OK" <br />button. <br /> <br />11. <br /> <br />Entering Return-Flow Distribution Data. To complete the <br />specification of a demand represented as a diversion with return flows, <br />the user must also specify when and where the unconsumed portion of <br />each month's diversion will return to the stream. A second data-entry <br />form facilitates this and checks that the spatial and temporal <br />distribution ofretum flows adds up to 100%. <br /> <br />12. Setting a Priority for the New Diversion. The network connections <br />and capacities for the new diversion are now fully specified. The user <br />is prompted to assign a priority or "rank" for the new diversion. <br />Instead of trying to figure out an appropriate value by inspection of <br />other network ranks, the user selects a "junior-to-everyone" option, <br />and the model assigns an appropriate rank for him. <br /> <br />13. Ending the New Scenario. The "scenario creation" window now <br />shows that a new diversion has been added. Since this is all that the <br />user wants to change from the reference scenario, he indicates that the <br />new scenario is now complete. <br /> <br />14. <br /> <br />. Specifying Additional Output Data. [Because the user selected the <br />top"level activity of "comparing scenarios," the model might be smart <br />enough to look for predefined output specifications, such as graphs of <br />impacts on fiow at particular points, stored with the reference <br />scenario. The user also wants to know the "yield" of the new junior <br />water right. There might be a way for him to specify this before <br />making a run, in order to minimize the output generated.] The user is <br />now looking at a "command console" that enables him to do a number <br />of things, such as executing a run with the model, specifying additional <br />output, naming the scenario, etc. The user indicates that he wants the <br />run to generate the predefined set of outputs and comparison graphs <br />and also to generate output for the yield of the new diversion. <br /> <br />15. Executing the Run for the Comparison. The user selects the <br />"Execute Model" option in the "command console" window, and gets a <br />message that the run is underway, perhaps with a count of the years so <br />far completed. <br /> <br />".".A.i )t <br /> <br />,,""- _~, a~ ,.,...&;;.<.,.j_-~ <br /> <br /> <br />< <br /> <br /> <br />:; <br /> <br />); <br /> <br /> <br />~, <br /> <br />~,~~~~_~-_iihi~,~ <br />