My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
white_whole_report
CWCB
>
Decision Support Systems
>
DayForward
>
white_whole_report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:56 AM
Creation date
7/15/2008 11:12:46 AM
Metadata
Fields
Template:
Decision Support Systems
Title
White River Basin Water Resource Planning Model
Decision Support - Doc Type
Report
Date
3/30/1999
DSS
Colorado River
Basin
Yampa/White/Green
Contract/PO #
C153933, C154062
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.
/
78
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
File Type Description <br />*commands In ut tstool control file <br /> <br />*.eom Output StateMod Historical End-of--Month Reservoir Content <br />File <br />tstool.log Output tstool process reporting <br />Step - 7 Reservoir Target Contents File To create a StateMod Reservoir Target Contents File, the <br />user provides a file of tstool commands (*commands). Files created or used by the DMI tstool in this <br />step are described below. Note all the data required to control data filling is provided to tstool and <br />documented in the *commands file. See the tstool and StateMod documentation for further <br />information pertaining to the format and data contained in each input file and output file, <br />respectively. <br />File T e Descri tion <br />*commands In ut tstool control file <br /> <br />*.tar Out ut StateMod Reservoir Tar et file <br />tstool.lo Out ut tstool rocess re ortin <br />Step - 8 Historical Diversion File To create a StateMod Historical Diversion File, the user provides <br />the direct diversion station file (*.dds) provided by Step 1 and a file of demandts commands <br />(*commands) to generate a file of historical diversions. Files created or used by the DMI demandts <br />in this step are described below. Note all the data required to control data filling is provided to <br />demandts and documented in the *commands file. See the demandts and StateMod documentation <br />for further information pertaining to the format and data contained in each input file and output file, <br />respectively. <br />File T e Descri tion <br />*commands In ut demandts control file <br /> <br />*.ddh Out ut StateMod Historical Direct Diversion File <br />demandts.lo Out ut demandts rocess re ort detail <br />Step - 9 Demand Files To create StateMod Demand files requires a relatively complicated set of <br />procedures that varies for the Historical, Calculated and Baseline data sets. Other complicating <br />factors include the type of use (agricultural vs. M&I) and whether a structure is modeled explicitly or <br />as a part of an aggregated group. The approach used to develop StateMod demand files utilize the <br />consumptive use model CRDSS-CU, the DMI demandts and miscellaneous data stored in the <br />central database such as structure location, crop acreage, crop mix and regional temperature and <br />climate. Appendix D, Section D9 describes the development of demand data for StateMod in detail. <br />Step - 10 Other StateMod Files The remaining input files required for StateMod execution are <br />relatively small and are typically created from an example provided with StateMod program. These <br />files include the response file (*.rsp), operation file (*.opr), delay table file (*.dly), control file <br />Model Development 3-7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.