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 />002043 <br /> <br />. <br /> <br />2. INPUT DATA AND DEFINITIONS <br /> <br />2.1 System Definition - Node and Element Concepts <br /> <br />The configuration of the river system is defined by means of <br />element data cards (Type 3-1)*. Only tree-type branching systems <br />are permissible, resulting in a single downstream boundary. Model <br />nodes which correspond to an exact geographical location on the <br />river are first located. They are chosen to coincide with existing <br />gaging stations, to locate points at which model output is desired, <br />to delimit portions of the river system such as reservoirs or <br />river reaches, and to subdivide lengths of the river to obtain <br />the desired resolution for water use inputs. Nodes are consecu- <br />tively numbered using integer values starting at 1. However, <br />there is no restriction on their order: Node 1 can be downstream <br />from Node 20 and upstream from Node 7. <br /> <br />. <br /> <br />Elements are defined as that portion of the river system between <br />geographically adjacent nodes. The only exception is for upstream <br />boundary elements which have no upstream node. Consequently, <br />nodes represent a single location and elements embody the dimen- <br />sions of length or area. By convention, elements assume the <br />number of the downstream node. All inputs for an element must <br />reference this element number. <br /> <br />Five types of elements are allowed, with the type specified by <br />the numeric code ITYPE on the element data Card 3-1. They are: <br /> <br />ITYPE <br /> <br />Description <br /> <br />1 <br />2 <br />3 <br />4 <br />5 <br /> <br />Upstream boundary <br />Downstream boundary <br />River reach <br />Junction <br />Reservoir <br /> <br />. <br /> <br />Both water and salt are introduced to the system at the upstream <br />boundary elements. These generally provide the main driving force <br />or input to the system. Desired flows at the downstream boundary <br />are specified as target values which mayor may not be realized. <br />River reach elements are assumed to have no storage properties <br />(surface or bank) and merely route flows from the upstream to <br />downstream nodes encompassing the element. Reservoir elements <br />provide for storage of water (and salt) and may be operated in a <br />variety of ways as specified on input. Both evaporation and bank <br />storage are included. The confluence of several river branches is <br />accomplished through use of the junction elements. <br /> <br />* See footnote for Section 4.5. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.