My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC05258
CWCB
>
Water Supply Protection
>
Backfile
>
18000-18999
>
WSPC05258
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 11:12:27 AM
Creation date
10/9/2006 5:06:48 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System-Ray
State
CO
Water Division
5
Date
9/30/1994
Title
Consumptive Use Modeling-Task Memorandum 1.14-9-Consumptive Use Prototype-August and September Update
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
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
<br />,It 01.)1S74 <br />Task Ll4(b) - Consumptive Use Prototype Development <br /> <br />copy documentation will follow. In August, we began working on documenting the code <br />for the CU model. <br /> <br />3.62 Users' Manual <br /> <br />The on-line documentation will be used to create a hard-copy user manual. The Users' <br />Manual will include an introduction, tutorial, detailed reference guide for the GUI, <br />technical background, glossary of terms, and an index. The introduction will illustrate <br />the consumptive use model's role in the bigger picture of CRDSS and will provide <br />information about the context and scope of the model. The tutorial will run through a <br />scenario for using the Model. The scenario will be technically robust and will include <br />realistic data. The detailed reference guide will comprise the bulk of the manual and will <br />describe each possible selection of the GUI. A section will be included with the technical <br />background of the model including a literature review for the ET method selected and <br />the assumptions used. <br /> <br />The User Manual will not directly duplicate information found in the on-line <br />documentation, but there will definitely be overlap in the development. The tone of the <br />writing will be geared to the hard copy format and screen grabs showing actions will be <br />included along with other informative graphics. <br /> <br />3.6.3 Developers' Manual <br /> <br />The Developers' Manual will be targeted at the more sophisticated users of the system. <br />This will provide detailed technical and programming information and will also contain <br />a glossary, index, and a list of source code. Other features will include a listing and <br />definitions of each of the variables and routines used in the model. A list of event call- <br />backs with a flow chart will also be included. <br /> <br />4.0 References <br /> <br />Blaney, H.E, Rich, L.RI, Criddle, W.D., et al. (1952). "Consumptive use of water." Trans. <br />ASCE,117:948-967. <br /> <br />Jensen, M.E., R.D. Burman, and R.G. Allen. (1990). "Evapotranspiration and Irrigation <br />Water Requirements." ASCE Manuals and Reports on Engineering Practice No. 70. <br />American Society of Civil Engineers, New York, NY. <br /> <br />USBR, Untied States Bureau of Reclamation. (1986) "Colorado River Systems <br />Consumptive Uses and Losses Report (1981-1985) Technical Appendix Volume 1. <br /> <br />USDA., Soil Conservation Service. (1970). "Irrigation water requirements." Tech Release <br />No.21," (rev.), 92 pp. <br /> <br />5.0 Conclusions and Recommendations <br /> <br />The CU model is progressing according to schedule. In the next few weeks as the model's <br />numerical and GUI components will be ready to be tested and more emphasis will be devoted <br />to the data compilation, calibration of the models, and verification of the results. <br /> <br />9/30/94 - September Update (1.14-9) <br /> <br />9 <br /> <br />IDS Group, CSU <br />
The URL can be used to link to this page
Your browser does not support the video tag.