My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP01027
CWCB
>
Water Supply Protection
>
Backfile
>
1001-2000
>
WSP01027
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 12:28:58 PM
Creation date
10/11/2006 10:06:33 PM
Metadata
Fields
Template:
Water Supply Protection
File Number
8200.766
Description
Gunnison River Basin General Publications - Correspondence - Reports
State
CO
Basin
Gunnison
Water Division
4
Date
8/5/1992
Author
Unknown
Title
Gunnison Basin Models - Planning Model - 1991-1992 - Training Materials - User Session Descriptions 1-6
Water Supply Pro - Doc Type
Data
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
23
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 />.\ f ~ <br /> <br />~OQ 2 71 <br /> <br />. , , <br /> <br />'}<_ .~ ,",",*, ,W <br /> <br />, <br /> <br />Randy's notes included: (1) Exchanges/replacements must be modeled in priority classes. <br />(.2) Is historic operation of Blue Mesa the same as an undecreed historic exchange? <br /> <br />C. Analysis and Steps proposed by John Ozga: <br /> <br />I. Definition of problem (Assumed Context); decisions required as to <br />whether the exercise is aimed only at: <br /> <br />1. evaluation of Blue Mesa subordination benefits in light of protection of <br />Upper Gunnison juniors from Blue Mesa call, or <br /> <br />2. evaluation of impacts on Upper Gunnison users resulting from <br />Endangered Species contract releases, not only by increased frequency <br />of Blue Mesa calls, but also Redlands and Uncompahgre calls, or <br /> <br />3. (a) handling of Blue Mesa subordination as an exchange (counted <br />against Blue Mesa fill), or <br /> <br />(b) handling by varying priority to be most junior (selective only to <br />Upper Gunnison). <br /> <br />(Note: The increased frequency of calls may be considered as being <br />due to "conversion" offormerly "free water "from Blue Mesa power. <br />deliveries to water protected past diversions as specifically identified <br />deliveries.) <br /> <br />II. Define endangered fish demands. May have to be afunction offiows <br />at other points (e.g. Gunnison @ Whitewater, Colorado River), in <br />which case capability of computing demands (possibly by iterative <br />process) may be required, external or internal to model. <br /> <br />Ill. Select hydrology (wet, average, dry year). <br /> <br />A. Have default years as defined by model on <br />board; <br /> <br />B. Have user select hydrology period. <br /> <br />IV. Define "Blue Mesa" contract replacement (augmentation) pool <br />(reservoir account), <br /> <br />V. Indicate need to "color" endangered fish deliveries, in order to protect <br />them along a defined reach. <br /> <br />VI. Review how Blue Mesa "subordination" was handled under "B- <br />baseline. " <br /> <br />VII. Modify model to eliminate subordination (?) (create a "b-baseline" run <br />without endangered fish demands). Save results. <br /> <br />VIll Repeat VII to include endangered fish demands. <br /> <br />1,___A-.4 _'"'-_~"_ <br /> <br />~ ~___ 'A'" ~,~_,_"; _ <br /> <br />,:;" .;~~-:,,~;-i,:J <br />".~~~~'"~,_ _o~.__~~ <br />
The URL can be used to link to this page
Your browser does not support the video tag.