My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP04021
CWCB
>
Water Supply Protection
>
Backfile
>
4001-5000
>
WSP04021
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 12:53:19 PM
Creation date
10/12/2006 12:05:14 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8062
Description
Federal Reserved Water Rights
State
CO
Basin
Statewide
Date
9/1/1979
Author
R Barry Nehring
Title
Evaluation of Instream Flow Methods and Determination of Water Quantity Needs for Streams in the State of Colorado - September 1979
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.
/
153
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 />39 <br /> <br />O;}O;.~9 <br /> <br />Requirements for Methodology Improvement - IFG4 <br /> <br />The IFG4 model worked very well on the majority of the study <br />streams evaluated in this study. Two situations required data <br />manipulation for a satisfactory response from the IFG4 model. <br />First, in those instan~es_where the calibration flows were very <br />closely spaced, significant problems with the velocity adjustment <br />!a~tors were encountered which required manipulation of the data, <br />to "improve" the output. This occurred in only~!.e!!_instances <br />and on relatively small mountain streams. Secondly, on larger <br />streams (average discharge greater than 100 cfs) the only problems <br />with the IFG4 model response to the data occurred where large <br />boulders were strewn throughout the transect and the velocity <br />profile varied greatly across the channel over very short dis- <br />tances. Modification of the program to handle large velocity <br />variations across the transect(s) would greatly increase the <br />range and capability of the IFG4 program. <br /> <br />The IFSG should modify the printout capability of the IFG4 <br />program to give an average velocity, average depth, and total <br />cross sectional area for each input Q at each transect. Then <br />these parameters could be readily compared with the same output <br />parameters of other methodologies. The lack of this capability <br />required an additional 200 man-hours of hand calculations by t~e <br />author in order to make direct comparison between the R-2 Cross <br />and IFG4 methodologies. <br /> <br />Recalling that the average velocities predicted by the <br />IFG4 Method were underestimated by 2.0%, 67% of the time, the_ <br />question arises as to why this is the case. It is probably <br />something inherent in the program and could very well have some- <br />thing to do with the velocity adjustment factor and the manipu- <br />lation of the data inherent to that parameter. Some attempt <br />should be made to correct this problem. <br /> <br />Requirements for Methodology Improvement - IFG3 <br /> <br />I believe giving equal weight to all of the preference factors <br />for each life stage when the IFG4 Model is interfaced with the <br />IFG3 model is wrong, especially for brown trout. Several in- <br />vestigators have shown that overhead cover is the overriding <br />factor in determining brown trout habitat, much more so than <br />either depth or water velocity (Baldes and Vincent, 1969; <br />Butler and Hawthorne, 1968; Elser, 1968; and Wesche, 1974). <br />It is encouraging to know that a cover preference factor will <br />soon be an input with the IFG3 model, but it should be given a <br />heavier weighting in the calculation of weighted usable area. <br /> <br />Finally, preference factors for cutthroat trout may not be <br />reliable for the species in the streams studied, especially the <br />Rio Grande cutthroat trout, Salmo claPki virginalis. Streams <br />
The URL can be used to link to this page
Your browser does not support the video tag.