Laserfiche WebLink
Memorandum To: File September 28, 2001 <br />Page 3 <br />Monthly Model (ElkRvr) <br />The monthly ElkRvr model was created by editing command files for the Yampa basin model <br />designated Yampa_2001, which the State provided. Generally, the editing removed references to any <br />part of the model outside of the Elk River from the headwaters to the Clark gage (09241000). The <br />resulting model network is presented in Figure 1. <br />Anew demand node, named NewDemand, was added to the model network to accommodate a new <br />demand in the future scenario model runs. In the calibration run, this demand was set to zero. In the <br />future scenario, this new demand was the same in every year, and had the monthly values shown in <br />Table 2. <br />Table Z <br />Monthly Demand for NewDemand <br />Month Demand (af) <br />Oct-March 0. <br />Aril 19042. <br />Ma 41951. <br />June 48596. <br />Jul 39075. <br />Au ust 20152. <br />Se tember 3511. <br />Total 172327. <br />These values are the monthly equivalent of the daily pattern of demand shown in Table 3 under the <br />Average Daily Model. <br />Base name for this model was "Elkrvr". <br />Average Daily Model (Dlyelkl) <br />For this model, Statemod disaggregated monthly baseflows, diversion demands, instream flow demands <br />and reservoir targets by setting them to an average daily value (monthly volume divided by number of <br />days in the month). Specifically, this was accomplished by setting flags in the river station (*.ris), <br />diversion station (*. dds), instream -flow station (*. ifs), and reservoir station (*. res) files to zero. <br />In the future scenario, the hypothetical NewDemand was treated at a daily level. This demand pattern <br />was fairly arbitrary, but was created with two requirements in mind: 1) it needed to be large enough to <br />have a perceivable effect on the gage, given the size of the stream, and 2) it had to change at mid-month, <br />to demonstrate differences in results using daily rather than monthly models. The NewDemand daily <br />demand is shown in Table 3: <br />TaskMem2Final.doc f304~LE <br />