My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC06972
CWCB
>
Water Supply Protection
>
Backfile
>
19000-19999
>
WSPC06972
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 12:08:40 PM
Creation date
10/9/2006 6:11:33 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
9/1/1973
Author
DOI-BOR
Title
Application of a River Network Model to Water Quality Investigations for the Colorado River
Water Supply Pro - Doc Type
Report/Study
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
230
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 />0J1326 <br /> <br />the reservoirs were within 3 ppm for the mean and 1 ppm for the <br />standard deviation. The results for the 0.06 bank storage coef- <br />ficient were subsequently used since a positive, nonZero coeffi- <br />cient is physically more satisfying. <br /> <br />~ <br /> <br />Inspection of Figure C-25 indicates computed 1968-1970 values to <br />exhibit different properties. All values are negative, indicating <br />unaccounted for salinity diversions. The effect is apparently due <br />to the present modified salt masses at the Hoover station. <br /> <br />As noted in the River Basin System Configuration section, Node l8 <br />was introduced to allow inclusion of the ungaged inputs upstream <br />from both reservoirs. This is a practical necessity since details <br />are lost because of inadequate data. In addition, Node 19 was <br />added below Parker Dam to allow both CAP and t~~D demands to be <br />satisfied by operating Lakes Powell and Mead. Although required <br />by program convention, this approach has no effect on salinity <br />results. However, the addition of CAP and r~~D downstream could <br />result in Parker Dam capacity restraints preventing the full <br />release. In practice, this did not occur for the runs described <br />in this report. <br /> <br />~ <br /> <br />L <br /> <br />Parker-Imperial Reach <br /> <br />The upstream and downstream stations for this reach are the Colorado <br />River below Parker and at Imperial Dams. Storage behind Imperial <br />Dam is insignificant and the reach was treated as a river reach. <br />Results are given in Tables C-28 through C-30 and in Figures C-27 <br />through C-29. Figure C-27 suggests unaccounted for diversions <br />occurred during 1968-1970. Although the Lower Colorado Indian Res- <br />ervation and the Palo Verde Irrigation District were not explicitly <br />considered and are therefore included in the ungaged value, this <br />difficulty is probably related to the peculiar salt mass results <br />for the same years in the Hoover to Parker reach. Both the monthly <br />values for each year and the mean monthly values for the entire run <br />were used in obtaining a base run. <br /> <br />, <br />~ <br /> <br />Summary - All Reaches <br /> <br />I. <br />t <br />r <br /> <br />Means and standard deviations for flows and salt mass are summarized <br />in Table III. <br /> <br />t, <br /> <br />Fundamental Differences Between Network r,lodel and Biennial Report t,lethod <br /> <br />A consideration bearing on the difficulties in computing ungaged trib- <br />utary inputs are the fundamental differences between the network <br />model and the Biennial Report method. [1] In the Biennial Report, <br />historical data at a given station are merely adjusted or modified <br />to reflect additional projects. Ungaged inputs are not explicitly <br />considered, and are in effect assumed unchanged, being embodied in <br /> <br />l6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.