My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task2-10_WaterResourcesPlanningModel
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task2-10_WaterResourcesPlanningModel
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:32:32 AM
Creation date
7/11/2008 1:00:04 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 2.10 - Water Resources Planning Model
Description
This task memorandum describes the use and details of the Water Resources Planning Model.
Decision Support - Doc Type
Task Memorandum
Date
12/5/1996
DSS Category
Surface Water
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
8
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
watright basin="modeled basin" -rightss rin=makenet.rin -rin -ostatemod <br />The evaporation data file consists of several monthly evaporation estimates for a reservoir at a <br />given elevation range. The evaporation data file was created using the netresev DMI utility. <br />Each set of evaporation estimates is based upon a nearby precipitation station and the National <br />Oceanic and Atmospheric Administration (NOAA) monthly gross evaporation estimates: <br />(netresev yampa -ft -ave P=7936 -w.5 P=9265 -w.5 E=0 <br />JAN. 033x.1x.2x.3x.42x.52x.53x.43x.37x.25x.13x.05). <br />See also the netresev DMI documentation. <br />The end-of--month content file, similar to the historic streamflow file, was constructed using the <br />tstool DMI. Here, modeled reservoirs are selected in order of the reservoir station file, and tstool <br />creates a time series file of historic end-of--month reservoir contents in StateMod format. As with <br />the streamflow file, tstool has the capability to do various data filling procedures to address <br />incomplete reservoir end-of--month records. <br />The last reservoir file, the reservoir target content file (*. tar), is constructed in the same format <br />as the end-of--month file. The one exception is that each reservoir has two lines of information <br />per year: a maximum target content and a minimum target content. Reservoir target data may <br />reflect historic operations or estimated future operations. Please refer to the target file in <br />Appendix A in any one of the CRDSS basins' model documentation for examples. <br />2. S Instream Flow Files <br />StateMod requires three instream flow files: the instream flow station file (*. ifs), the instream <br />flow right file(*.ifr), and the instream flow demand -annual file (*.ifa). The instream flow <br />station file and the instream flow right file represent the location of the instream flow node <br />within the model and its corresponding water rights, respectively. As with the station and water <br />rights files for the diversions and reservoirs, the equivalent instream flow files are generated <br />using the watright DMI utility: <br />(watright basin="modeled basin" -rightsi rin=makenet.rin -rin <br />-ostatemod) <br />The instream flow demand file - annual is manually created based on information contained in <br />the water rights tabulations or interviews. Please see the *. ifa file in Appendix A in any one of the <br />CRDSS basins' model documentation for examples. <br />2.6 Miscellaneous Files <br />All of the remaining input files for StateMod are created manually. These files include the <br />operation file (*.opr), response file (*.rsp), delay table file (*.dly), control file (*.ct~, geographic <br />information system file (*.gis), and output request file (*.out). Details concerning each of these <br />files are discussed in Section 4, Input Description, of the StateMod Manual. <br />3.0 Model Operation <br />
The URL can be used to link to this page
Your browser does not support the video tag.