My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC03736
CWCB
>
Water Supply Protection
>
Backfile
>
16000-16999
>
WSPC03736
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 11:36:08 AM
Creation date
10/9/2006 4:09:58 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.100
Description
Colorado River Computer Models - Colorado River Simulation System - Reclamation - CORSIM
State
CO
Basin
Colorado Mainstem
Water Division
5
Date
7/1/1973
Author
Richard W Ribbens
Title
Program NWO1 - River Network Program - Users Manual
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.
/
139
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 /> <br />0020o~ <br /> <br />. <br /> <br />input may be given a number in the consecutive string even if <br />it is not used or its value is zero. The element in which an <br />input is located is specified on the identification card for <br />that input. <br /> <br />Inputs located in reservoir elements withdrawing water are assumed <br />to do so directly. Consequently, the outlet works capacity does <br />not apply and there is no restriction on the size of the deple- <br />tion. Water can be withdrawn from the reservoir until it is dry, <br />after which the remaining demand must be satisfied using reservoirs <br />specified by the segment data. If withdrawals are to be met by <br />releases from several reservoirs, a dummy river reach should be <br />added immediately downstream from the reservoir and the input <br />located in it. <br /> <br />When the logical analysis of inputs is requested, the program <br />checks all inputs for errors (Appendix B). However, even if <br />the analysis is not requested, seve,al items ~re still checked <br />when the program establishes internal arrays. Consequently, <br />logical error messages may be produced even though this option <br />was not specified. <br /> <br />. 2.4 Boundaries <br /> <br />Boundaries include those upstream at which both flow and salinity <br />are specified as well as the downstream boundary at which desired <br />or target flows are specified. . Values at the upstream boundaries <br />normally represent. the main supply or driving force of the river <br />system. If the computed downstream boundary flow is less than <br />the target value, the difference is treated as a demand which <br />may be met by releasing water from those reservoirs indicated by <br />the segment data. Upstream flows and salinities and downstream <br />target flows should always be positive quantities, although <br />there are no program checks to assure this. <br /> <br />Upstream boundary (Major Class 11). - Inputs include an <br />alphanumeric identification, volume and salinity monthly <br />distribution use code, monthly distribution numbers, salinity <br />code, and the volume and salinity. Values of the volume and <br />salinity can be input as monthly values or as annual ones <br />distributed using monthly percentages. <br /> <br />Downstream boundary (Major Class 12). - Inputs include the <br />volume monthly distribution use code, monthly distribution <br />number, and the target volumes specified as monthly or <br />annual values. <br /> <br />. <br /> <br />2-19 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.