Laserfiche WebLink
<br />I' <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br /> <br />The assumption was made that the distribution of average monthly flows in <br /> <br /> <br />the historical record would remain unchanged in the augmented record. The <br /> <br /> <br />augmented record of monthly inflows was then computed by multiplying the <br /> <br /> <br />augmented annual values by the percentage of the historical mean value <br /> <br />calculated for each individual month. The historical mean values and <br /> <br /> <br />percentages used are shown in Table 5-1. <br /> <br />5.4 GENERATION OF SYNTHETIC INFLOW RECORD FOR CBT PROJECT <br /> <br />A 1000-yr synthetic record of CBT inflows was generated using the same <br />procedures described earlier in Section 4.3. As a matter of consistency, <br />only the augmented record of CBT inflows from 1927 to 1984 were used as <br />this period of record was used for the generation of synthetic Big Thompson <br />River native flows. The generation process reproduced the statistics of <br />historic CBT inflows quite closely in most months, although mean flow <br />values are quite high in comparison to historic values for the months of <br />March, September, and October. Consequently, the synthetic record will <br />often over-estimate inflows to the CBT during those months. As shown <br />earlier in Table 5-1, however, the combined historic average inflow of <br />these three months is less than six percent of the annual average. This <br />fact reduces significantly the impact on annual inflow volumes of <br />overestimates in March, September and October. On an annual basis, the <br />mean flow value of the generated record is within two percent of the <br />historic average. Table 5-2 presents the monthly and seasonal comparison <br />of synthetic versus historic statistics for inflows to the CBT. This <br />degree of accuracy is consistent with the later use of this data. <br />Additional details concerning this effort may be found in the Technical <br />Appendix. <br /> <br />5-7 <br />