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 />002035 <br /> <br />. <br /> <br />(2) Make a specified release and meet any downstream demands <br />(3) Do not make a specified release but meet downstream demands <br /> <br />Before proceeding downstream, the reservoirs demand array is used to <br />determine if a specified release is requested. If it is, the release <br />is made subject to capacity restraints. The computational procedure <br />is identical to that used whenever releases are made from storage to <br />meet downstream demands. No water may be released if the level is <br />within the dead storage pool since the corresponding capacity is <br />zero. When levels are above the dam crest, there is no restriction <br />on the capacity. Between the spillway and dam crests, the maximum <br />flood capacity controls. Below the spillway crest and above the <br />dead storage pool the normal maximum capacity is used. When the <br />variable constraint option is used the variable constraint level <br />supersedes the dead storage level as the level below which the <br />capacity is zero as far as releases from storage are concerned. <br />Should the variable constraint level exceed that of the spillway <br />crest, the program essentially reduces it to the level of the spill- <br />way crest. <br /> <br />. <br /> <br />The program aetermines in which of the previous zones the water level <br />is located, computes the amount of water available as bank and surface <br />storage in that zone, adds it to the releases made thus far, and then <br />compares the total with the corresponding capacity. If the capacity <br />exceeds or equals this amount, available water in the next lower zone <br />is computed and handled in the same way. If the capacity would be <br />exceeded should all' available water be released, the available water <br />is reduced until the maximum capacity is just reached. <br /> <br />The available water is now compared to the demand (or required release). <br />If it exceeds the demand, releases are made to just satisfy the demand. <br />If it is less than the demand, all of the available water is released <br />and a portion of the original demand remains unsatisfied. <br /> <br />After the specified releases are made, computations proceed downstream <br />from the reservoir. If an unsatisfied demand is eneountered, segment <br />data are used to determine which upstream reservoirs can be operated <br />to satisfy the demand. However, some of these reservoirs may not be <br />available because the demand array may allow only specified releases. <br />Since the demand array is time dependent, the actual number of reservoirs <br />available to meet demands may vary from month-to-month. <br /> <br />When more than one reservoir is aVailable, their conjunctive operation is <br />based on the release rule code which permits three methods of operation: <br /> <br />. <br /> <br />3-3 <br /> <br />(rev~ 07/75) <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.