My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC00985
CWCB
>
Water Supply Protection
>
Backfile
>
13000-13999
>
WSPC00985
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 11:08:35 AM
Creation date
10/9/2006 2:29:01 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
5/1/1985
Author
DOI-BOR
Title
CRSS - Colorado River Simulation System - System Overview
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.
/
184
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 />00164:' <br /> <br />(9) Water delivered from Lake Mead in excess of normal downstream <br />demands is distributed equally to Arizona via CAP and California via <br />MWD. If either CAP or MWD reaches its capacity, the other user can <br />take rema i ni ng excess up to its capacity. After both CAP and MWD <br />reach their capacities, remaining excess water flows to Mexico. <br /> <br />The above provisions are normally applied in studies using the CRSS. <br />Most of the values and procedures described, however, can be easily <br />modifi ed or bypassed by si rnply changi ng the input data. Therefore, <br />studies can be made using variations of these provisions; or modifica- <br />tion to the provisions themselves can be studied using the CRSS. <br /> <br />3. 5Comp~'!.~'!.t.s__o_~t.I!.~ CRS~ <br /> <br />The CRSS is composed of a number of programs, data bases, and input data <br />control files. The relationship between these programs and files is <br />shown in figure 3.1. <br /> <br />The components of the CRSS can be divided into three parts: the demand <br />files, the hydrology files, and the CRSM and accompanying input and out- <br />put files. The demand files are shown in the upper left part of <br />figure 3.1. These programs and files are described in section 4: <br />Demand Data. The hydrology files are shown in the upper right part of <br />figure 3.1 and are described in section 5: Hydrology Data. The CRSM, <br />control files, and output programs and files are described in section 6: <br />Colorado River Simulation Model. <br /> <br />r <br />t <br />~ <br /> <br />3.6 Basin Configuration <br /> <br />The Colorado River Basin is currently divided into 25 reaches for <br />modeling purposes. Each reach is then divided into a maximum of <br />10 inflow points and 10 diversion points. <br /> <br />The basin map found in front of the System Overview shows how the <br />Colorado River Basin is divided into reaches. Figure 3.2 shows a block <br />diagram of the reaches. Each block in the figure represents one reach. <br />Reach 500, the Yampa River, for example, flows into Reach 411, Flaming <br />Gorge. The reach schematic for Reach 411 (fig. 3.4) shows the Yampa <br />Rtver as an inflow point to Reach 411, below Flaming Gorge Reservoir. <br /> <br />Figure 3.3 is a typical reach schematic which shows how a reach is <br />broken down into inflow points and demand points. This reach, <br />Reach 401, Fontenelle, contains an inflow point (Q+l), a demand with a <br />return flow (D-l and Q+2), a demand with no return flow (D-2), a reser- <br />voir (5R+3), and a salinity checkpoint (Q+9). <br /> <br />~ <br />b <br /> <br />The location and relationship of the reaches as shown on the basin map <br />and figure 3.2 is the configuration normally used. The reach con- <br />figuration could be rearranged if necessary by modifying the input data <br />to the model. This is a time-consuming task, but can be accomplished <br />without revision to the CRSM computer code. <br /> <br />11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.