My WebLink
|
Help
|
About
|
Sign Out
Search
StateWB_UsersGuide
CWCB
>
Decision Support Systems
>
DayForward
>
StateWB_UsersGuide
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/13/2011 11:15:43 AM
Creation date
1/13/2011 11:03:33 AM
Metadata
Fields
Template:
Decision Support Systems
Title
StateWB Documentation
Description
This document was prepared to explain the features and functions of StateWB and presumes the reader has a basic understanding of water budget analyses.
Decision Support - Doc Type
Software Documentation
Date
12/22/2009
DSS Category
Water Budget
DSS
All
Basin
Statewide
Contract/PO #
C153954
Grant Type
Non-Reimbursable
Bill Number
SB01-157, HB02-1152, SB03-110, HB04-1221, SB05-084, HB06-1313, SB07-124
Prepared By
Leonard Rice Engineering
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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).
Download electronic document
Show annotations
View images
View plain text
included in the calculations, and the names of input data files to be read by the model. The <br />incidental losses reflect non -crop consumptive use incidental to irrigation, as termed by the <br />USBR CU and Losses Report documentation. If incidental losses are not considered, a zero must <br />be entered for the incidental loss factor. <br />The GUI provides a means to define scenarios. It guides the user through browsing for input <br />files, setting the study period, and specifying the incidental loss factor. The user can then save <br />the scenario information to a response file (.res). <br />2.1.3 CU and Losses Report <br />When generating the CU and Losses Report for the Colorado River basins, the calculations are <br />based on information in the CU and Losses report response file ( *.rcl). The response file <br />provides the model parameters including the reporting period, the percent of incidental losses <br />to be included in the calculations, and the file path of the folders containing the input files to be <br />read by the model. The incidental losses reflect non -crop consumptive use incidental to <br />irrigation, as termed by the USBR CU and Losses Report documentation. If incidental losses are <br />not considered, a zero must be entered for the incidental loss factor. <br />Note that all of the input files associated with each basin need to reside together in a single <br />folder. This folder convention allows the user to only have to specify five file paths (one for <br />each basin) rather than having to separately specify 55 input files. Within each basin directory, <br />the 11 input files must meet strict file naming conventions (see Figure 1). <br />The GUI provides a means to define scenarios. It guides the user through browsing for input file <br />paths, setting the study period and incidental loss factor. The user can then save the scenario <br />information to a response file (.rcl). <br />The first two characters of each file name represents the basin: <br />cm = Upper Colorado River Fusin ym = Yampa River Basin <br />gm = Gunnison River Basin sj = San Juan River and Dolores River Basins <br />wm = White River Basin <br />The next 2 <br />- 6 characters represent the data type_ <br />IWR = <br />Irrigation Water Requirement <br />MINERL <br />= Mineral Use <br />CROPCU = <br />Supply - limited Crop Consumptive Use <br />THERM <br />=Thermal Use <br />CROPAC = <br />Crop ,Acreage <br />MUNICU <br />= Gather Municipal and Industrial Uses <br />LIVSTK = <br />Livestock Consumptive Use <br />EXPIN <br />= Exports Inside the System <br />STKEV = <br />Stockpond Evaporation <br />EXPOUT <br />= Exports Outside the System <br />RESEV = <br />Reservoir Evaporation <br />3. Each file should have an .STM extension. <br />4. The program is not case sensitive (all parts of file names may be upper or lower case).. <br />Figure 1- File Naming Conventions for CU and Losses Report Inputs <br />Page 7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.