Laserfiche WebLink
<br />12 <br />FIGURE 5 10tb Percentile Elevations from Januar 2002 to December 2001 <br /> <br />Flaming Gorge Elevation <br />10th Percentile <br /> <br />6040 <br /> <br />6030 <br /> <br /> <br />.... <br /> <br />',' <br /> <br />" <br /> <br />, " <br />" <br />" <br />. <br /> <br />" , <br />'.' ", <br /> <br />'. :.... <br /> <br />" <br />"', <br /> <br />$: <br /> <br /> <br />'" <br /> <br />g 6020 <br />is <br />'," <br />" <br />~ <br />fil 6010 <br /> <br />6000 <br /> <br />AlllO%ile <br />All - I lO%ile <br />No Action lO%ile <br />All Trace 5 <br /> <br />5990 <br />01-2002 <br /> <br />01-2004 <br /> <br />01-2006 <br /> <br />01-2008 <br /> <br />01-2010 <br /> <br />01-2012 <br /> <br />Year <br /> <br />Figure 6 shows another example of how the Action(ALL) and Action(ALL-l) rulesets <br />behave under identical hydrologic conditions, In the first 8 years of trace 5, the Action (ALL) <br />reservoir elevations were the same as the Action(ALL-l) reservoir elevations, This indicated that <br />the releases made by the two rulesets were identical for the first 8 years, However, conditions on <br />the Yampa River in 2005, 2006, and 2007 triggered the Action(ALL) ruleset to attempt to <br />achieve the 18,600 cfs objective, Because conditions were very wet in the Upper Green River <br />Basin in those years, the peak release established by the Action(ALL-l) ruleset was equal to or <br />greater than the threshold peak release that the Action(ALL) ruleset would have reset the peak <br />release to, For this reason, the Action(ALL) reservoir elevations did not deviate from the <br />Action(ALL-l) reservoir elevations during the first 8 years of the trace, In 2010, this was not the <br />case, The Action(ALL) ruleset reset the peak release to achieve the 18,600 cfs objective, <br />resulting in the reservoir elevation dropping about 8 feet below the Action(ALL-l) elevation, <br />