Laserfiche WebLink
activities (sub-tasks) under Task 6 of the Surface Component Water Scope of Work. The sub- <br />tasks, the associated model input files, and the DMI used in their creation are shown in Table 1. <br /> Table 1 <br />Task Model Input Files DMI/Utility <br />Task 6.4: Return Flow Characteristics (rg.rtn, rg.dly) makertn <br />Task 6.5: Network File (rg.net, rg.rin, rg.rib) makenet <br />Task 6.6: River System Files (rg.rih) tstool <br />Task 6.7: Diversion Files (rg. ddr, rg. dds) watright <br />Task 6.8: Reservoir Files (rg. rer, rg. res, rg. eom, rg. tar; rg. eva) demandts, tstool <br />Task 6.9: instream Flow Files (rg. ifi^, rg. ifs, rg. ifa) watright <br />Task 6.10: Operating Criteria File (rg. opr) hand edit <br />Task 6.11: Response and Control Files (rg.rsp, rg.ct~ hand edit <br />Model Execution Sequence <br />Following development of initial input data sets, the running of a StateMod application proceeds <br />through athree-step sequence. In the first step, the model is run in "baseflow mode" where base <br />streamflows are calculated based on observed conditions of streams, diversion structures and <br />reservoirs. The baseflow data set essentially has the impact of historic diversions, return flows, <br />well pumping, and reservoir storage, release, evaporation and seepage removed. The generation <br />of a base streamflow sequence is necessary for a basin planning model in order to analyze a <br />"What IF" scenario which includes a proposed water right or operating strategy that may impact <br />historic river operations. <br />In the second step of running StateMod, the model is executed in data "check mode" where all <br />input data (streamflow and diversion data) are echoed to output files, a comprehensive list of all <br />water rights sorted by priority is printed, input data for simplified reporting is tabulated, and <br />selected data checks of the input files are performed (proper network connectivity, location of <br />return flows, assignment of water rights and demands, reservoir characteristics). <br />The final step is to run StateMod in "simulation mode" were the river is operated based on user <br />specified water rights and operating criteria. It begins by reading data which is constant over <br />time such as the river network, reservoir structures, diversion structures, instream flow structures, <br />well structures and water rights. Once per year, time varying data such as streamflow, demands <br />and climate data are read. For every simulation time step, direct, instream, storage, well and <br />operational rights are then simulated from the most senior to junior priority. At the end of each <br />month, results are printed for each river node to a direct access binary file which can be accessed <br />to create a variety of reports. <br />This three-step process (baseflow, check, simulation) may be repeated numerous times during <br />model calibration efforts. <br />Phase 1a Model <br />As previously described, the Phase la surface water for the Rio Grande Basin represents <br />approximately 90 percent of the decreed surface water use along the Rio Grande and its <br />tributaries (the remaining surface diversions and river impacts associated with groundwater use <br />are left in the gage). In this phase of development, the model was executed in baseflow, check <br />C:Acdss\Task6-14.doc Phase la Model (Flistoric Monthly) February 22, 2000 -Page 2 of 10 <br />