My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP12615 (2)
CWCB
>
Water Supply Protection
>
DayForward
>
1-1000
>
WSP12615 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 4:18:43 PM
Creation date
10/21/2007 11:22:57 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8220.101.10
Description
Colorado River Water Projects - Glen Canyon Dam-Lake Powell - Adaptive Management
State
CO
Basin
Colorado Mainstem
Date
10/27/1997
Author
Glen Canyon Dam TWG - Spike Flow Subgroup
Title
Report of the Spike Flow Subgroup - Glen Canyon Dam Technical Work Group - 10-27-97
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.
/
26
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 />002554 <br /> <br />\;lay. with limited reie:lses in June :lnd July [0 preserve !:lte-,e:lson reie:lSe r1exibility [0 <br />:lccornmodate torec:lSt incre:lSes, The monthly Glen ClIlyon rele:lSe c:lpacitv was assumed to be <br />about l.9 MAf, The method of scheduling winter ::md spring monthly releases needs to be <br />clearly explained. In attempting [0 model our operation to avoid spills. several degrees of <br />aggressiveness in scheduling these releases were ::malyzed. In other words, if the torecast <br />changed as the operation progressed through the winter ::md spring, this analysis attempted to <br />answer the question "How should our operation react to these forecast changes?". In the past. ::m <br />aggressive reaction to torec:lSt changes was the key technique we used to reduce spill frequency, <br />For example, if the forecast increased by 2 YiAF at the beginning of April, then releases in April <br />would immediately be increased, perhaps to maximum capacity, in order to preserve as much <br />flexibility for future months as practicable, <br /> <br />By reviewing the results of these computer runs, we then determined the frequency of <br />unavoidable spills as well as the circumstances under which a BHBF would be scheduled, all <br />these under a range ofBHBF-triggering and "forecast-aggressiveness" assumptions, <br /> <br />Alternative BHBF Decision Criteria <br /> <br />The subgroup considered several methods that could serve as threshold triggering mechanisms <br />for implementing BHBF's. These include (I) various levels of risk associated with forecast error <br />curves previously discussed with the TWG, (2) monthly volumes, and (3) runoff forecast <br />percentages. Each of these methods attempts to answer the question. "Under what conditions <br />should a BHBF be triggered?". <br /> <br />As these alternatives were analyzed. an attempt was made to eliminate operational errors in <br />reacting to runoff forecasts, errors of omission as well as commission, An omission error would <br />be to not release a March BHBF when a spill actually would occur later in the year, accompanied <br />by high powerplant releases. As an example, Graph I shows the evolving spring runoff forecast <br />during water year 1985. The drop in the forecast on March I would have dissuaded the release <br />of a BHBF. when in actuality the dam would have spilled later in the spring when the inflow was <br />much higher than expected. A commission error is the release of a BHBF when a subsequent <br />spill would not have actually occurred. Graph 2 shows this type of situation in water year 1972. <br />where the runoff forecast was originally high early in the winter, but dropped dramatically in the <br />spring as the result of dry climatic conditions, <br /> <br />A range of forecast risks from 2 to 50 percent were investigated, A very liberal risk level of 2 <br />percent recognizes all actual spill years but also allows BHBF's in many years in which there <br />was no justification for such, The years 1970 and 1971 are good examples of such and had only <br />slightly above normal runoffwith very little risk of spill. Requiring high levels of risk as a <br />threshold more accurately handles the non-spill years, but fails to identify many of the actual <br />spill years. Because of the complexity in evaluating spill risk using forecast error curves. it was <br />suggested.that forecastS"should be evaluated from a "percent of normal" basis. The subgroup <br />found that such an approach was actually an alternate expression for spill risk. but more <br />straightforward and simpler to employ, Various percent of normal thresholds were evaluated. <br /> <br />5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.