Models and Rulesets Logs
The hydrology model and associated operating rules are in the third generation of evolution. The first two generations used hydrology data that were developed by Reclamation for 1970-1993 and were extended to 1929 by Keller-Bliesner Engineering using Colorado River Simulation System hydrology. The third generation uses Colorado Decision Support System (CDSS) hydrology data. Thefirst generation models used TCL to write rules. The second generation of rules predominately used the RiverWare rules language. The third generation rules are written entirely using RiverWare rules language. The third generation is under development and is anticipated to be completed by June, 2002.
A naming convention provides recognition of SJRIP model and ruleset development. The naming convention also provides identification of significant incremental modifications between major modifications as well as smaller incremental changes. Scenario model runs (specific runs of a model and ruleset) will be maintained in a separate tabulation. Model type is a general description of the usage of a model. The following model types and identifiers are being used:
- Natural flow model (NF) – A model that computes naturalized flows. The third generation uses a StateMod model to compute naturalized flows.
- Gains model (GM) – A model that only has hydrologic nodes used to compute gains.
- Validation model (VAL) – A model that runs without rules to validate that data water is properly conveyed through model.
- Calibration model (CAL) – A model that runs with rules under historic operating criteria to verify that the performance of operating criteria.
- Migration model (MI) – A model that moves data between two models to facilitate disaggregation and data conversions.
- Baseline model (BL) – A model that runs with rules under specified operating criteria and baseline depletions to study alternative operating criteria and baseline impacts.
An inventory of downloadable models and rulesets is available. The models tabulated in the inventory do not have saved run results. Saved run results are available from the Model Runs page. Model configurations are also available from the inventory page. The following sections are a reverse chrological narrative of model and ruleset development.
The third generation model is configured as per Colorado Water Conservation Board (CWCB)'s StateMod model for the San Juan River Basin so that StateMod hydrology can be used. The StateMod model is part of CWCB's CDSS system. It is believed that these hydrology are preferrable to the first and second generation hydrology.
The primary distinction of the second generation models and rules is the availability of RiverWare rules writer with RiverWare 2.2 Development. The second distinction of the second generation was implementation of ALP as an operating project. The first generation accounted for ALP as gains and losses. An operating ALP was developed from August, 1999 through October, 1999 and further adjusted in November, 1999. Details of these modifications made during this period are available upon request. The sections below highlight the major modifications.
All of the rulesets that were used for decision support (ALP SEIS and Navajo EIS) were bridge rulesets because the computation of the daily releases from Navajo to meet flow recommendations remained in TCL. A fully non TCL ruleset was developed late 2000 and was completed in January, 2001. This ruleset was developed to ease the transition to the third generation model. Additional information are available in the No TCL RuleSet documentation.
Models and rulesets after April, 2000, and before November, 2000, used RiverWare 3.0.3 Patch. This version of RiverWare can be used to run models and rulesets developed under RiverWare 2.2 Development. This version of RiverWare was retained because monthly evaporation coefficients were changed from length (feet) to a velocity (feet/month) data type in RiverWare 3.1.0 to be consistent with daily methods. Model and ruleset 2.5.2 were created under RiverWare 4.4.0 to reduce run times.
Model - SJ_BL_2.6.0.gz RuleSet - SJ_BL_2.6.0.RuleSet RiverWare - 4.4.0
This model includes the increased Jicarilla baseline depletions. This model and ruleset use RiverWare 4.4.0.
Model - SJ_BL_2.5.2.gz RuleSet - SJ_BL_2.5.2.RuleSet RiverWare - 4.4.0
This model and ruleset are a RiverWare 4.4.0 version of version 2.5.1.
Model - SJ_BL_2.5.1.gz RuleSet - SJ_BL_2.5.1.RuleSet RiverWare - 3.1.0
This model and ruleset corrected a bug in the long term look backup rule.
Model - SJ_BL_2.5.0.gz RuleSet - SJ_BL_2.5.0.RuleSet RiverWare - 3.1.0
This model and ruleset are identical to the August, 2000 model and ruleset. The Navajo EIS runs were made with this model were run using RiverWare 3.1.0. See version 2.4.0 notes regarding the reconfiguration of ALP.
Model - SJ_BL_2.4.0.gz RuleSet - SJ_BL_2.4.0.RuleSet RiverWare - 3.0.3 Patch
Modified Animas La Plata so that all Indian depletions occur in Colorado. This involved removing Aggregate Diversion ALPUteNMSupply and moving all of it’s depletions to be from Aggregate Diversion DemandsOnRBR. The computation of return flows that are available to Aggregate Diversion ALPNMSupply was revised accordingly. This is the configuration of the Navajo EIS runs inversion 2.5.0.
Model - SJ_BL_2.3.1.gz RuleSet - SJ_BL_2.3.1.RuleSet RiverWare - 3.0.3 Patch
1. Modified sediment flag to use current year’s sediment flag rather than previous year’s.
2. Modified sediment flag values to be one year offset from previous values.
These modifications had no net affect on operations because they were compensating. The sediment flag is used in the decision tree to
determine if a perturbation exist. These are the ALP SEIS model and ruleset.
Model - SJ_BL_2.3.0.gz RuleSet - SJ_BL_2.3.0.RuleSet RiverWare - 3.0.3 Patch
This was the first model and ruleset after the correction of the Monthly Natural Flow Balance error discovered when repairing a small (1295 acre-feet) double accounting error in depletions. See for Keller-Bliesner Engineering additional details. This model and ruleset also correspond to availability of RiverWare 3.0.3 Patch. The following rules changes were made to help the model meet flow recommendations:
1. Created rule “Stateline Long Term Lookback Rule” that looks at May and June volume of San Juan at Stateline gage for past n years (FlushingFlow.GageLookbackValues, row = StatelineLongterm, column = Years). If this volume is less than a specified volume (Flushing Flow.GageLookbackValues), row = StatelineLongter, column = MayJuneVolume), all n years, then make a maximum fish release. This rule sets path to 16.
2. Created rule “Stateline Short Term Lookback Rule” that looks at May and June volume of San Juan at Stateline gage for past n Years (FlushingFlow.GageLookbackupValues, row = StatelineShortterm, column = Years). If this volume is less than a specified volume (FlushingFlow.GageLookbackValues, row = StatelineShortterm, column = MayJuneVolume) all n years, then make a release of 550 cfs (33, 818 af) in May. This rule sets path to 17. Table slots NavajoData.FlushingConstraint5 and FlushingFlow.Peak33 were added to store the pattern (33,818 af) and flow duration table respectively.
3. Created functions EstimatedEndOfMayContent, EstimatedEndOfJuneContent, and GageWasShortInMayAndJune to support modifications.
Model - SJ_BL_2.2.3.gz RuleSet - SJ_BL_2.2.3.RuleSet RiverWare - 2.2 Development
1. Fixed an old error when checking min elevations. Should have a max to 0 when doing solve outflow at min elevation.
2. Modified Set NIIP Available rule to behave better. This included making sure that we meet min. release before meeting NIIP. This also involved unlinking available for diversion slot between Navajo and NIIP.
3. Changed Navajo no action normal release to compute the post runoff season release as the maximum of "NavajoAfterPeakRelease" and TargetSpaceRelease" in lieu of "TargetSpaceRelease".
Model - SJ_CAL_2.2.3.gz RuleSet - SJ_CAL_2.2.3.RuleSet RiverWare - 2.2 Development
Recalibration after item 3 above.
Model - SJ_BL_2.2.2.gz RuleSet - SJ_BL_2.2.2.RuleSet RiverWare - 2.2 Development
1. Implemented an additional check to Navajo storage space called “Conservative Target Space” to more closely reflect actual operations.
2. Revised COE flood control tables.
3. Revised COE flood control priority to properly give flood control highest priority.
Model - SJ_BL_2.2.1.gz RuleSet - SJ_BL_2.2.1.RuleSet RiverWare - 2.2 Development
Modified the look back pumping restriction implemented in January, 2000 to also test if a minimum or no flushing release is being made in current year.
Model - SJ_BL_2.2.0.gz RuleSet - SJ_BL_2.2.0.RuleSet RiverWare - 2.2 Development
This model incorporated the variable center date and regression operation of Navajo options into the main model and ruleset. In addition, the following modifications were made:
1. Modified Navajo Decision Tree Path to:
- a. Changed all ">"'s to ">="'s.
- b. Changed use of Spill plus Available Water to Available Water only.
- c. Modified paths 3 and 4 to use ">= 114,000" in lieu of ">= 166,000" to avoid unneeded releases.
2. Modified ALP fish mitigation rules and functions to test if June and previous n years had no fish release. If so, pumping is reduced to 0.0 to Ridges Basin reservoir. The number of years is obained from data object NavajoData.MaxYearsNoFishRelease.
3. Added Navajo regression operation (emulation of pre flushing releases) as a group to main ruleset. Navajo can now be operated by historic emulation or by flow recommendations criteria by toggling the respective groups on and off.
4. Changed forecasted depletion computations to enable palette function SumObjectsAggregatedOverTime to see computed diversion and depletion requests.
5. Modified forecast computations to consistently use average release in lieu of minimum release.
Model - SJ_BL_NavGal_2.2.0.gz RuleSet - SJ_BL_NavGal_2.2.0.RuleSet RiverWare - 2.2 Development
This model was a special configuration to study the Navajo Gallup project.
Developed a special ruleset to operate Navajo by pre flow recommendations criteria to support the Navajo No Action alternative of the Navajo EIS. This was accomplished by developing a regression of release to current storage, previous storage, and forecast volume. No model and ruleset are available but this behavoir was added to the main ruleset in January, 2000.
Model - SJ_BL_2.1.2.gz RuleSet - SJ_BL_2.1.2.RuleSet RiverWare - 2.2 Development
This model corrected a return flow linking error on NavajoTowaoc aggregate diversion, Cowboy Wash return flows.
Model - SJ_BL_VCD_2.1.0.gz RuleSet - SJ_BL_VCD_2.1.0.RuleSet RiverWare - 2.2 Development
This ruleset was created to enable the center date of the flushing hydrograph to be variable that is stored in a data object. This behavoir was implemented by Wave Engineering indepently starting with a 2.1.0 model and ruleset. The variable center date was integrated with the main model and ruleset in January, 2000.
Model - SJ_BL_2.1.1.gz RuleSet - SJ_BL_2.1.1.RuleSet RiverWare - 2.2 Development
Additional adjustements were made to daily pumping computations. It was not possible to use actually operate Ridges Basin Reservoir on a daily timestep in the monthly model. To fully reproduce a daily operation in rules would produce an unacceptable performance degradation. Therefore, daily pumping is based on daily pumping criteria and monthly volumes. If you proportion daily pumping to daily allowable pumping and monthly volume of pumping, you occasionally pumped less than the desired minimum. However, if you enforce the daily minimum, the last day of pumping for the month would occasionally go to 0 and produce slightly less total monthly pumping than allowed. It was decided these small differences were preferrable to violating daily operating criteria. This model was used to support the ALP draft SEIS.
Model - SJ_BL_Alt6_2.1.1.gz RuleSet - SJ_BL_Alt6_2.1.1.RuleSet RiverWare - 2.2 Development
This is a special model and ruleset to compute the effects of ALP Alternative 6, a non reservoir alternative for ALP.
- Model - SJ_BL_2.1.0.gz
- RuleSet - SJ_BL_2.1.0.RuleSet
- RiverWare - 2.2 Development
This is first model with an operating ALP. See Animas LaPlata Operating Criteria for additional information. The major modications during this were changing respect of historic users to use diversions rather than depletions as the comparison criteria and to improve the daily pumping behavoir of Ridges Basin pumping plant.
- Model - SJ_CAL_2.0.1.gz
- RuleSet - SJ_CAL_2.0.1.RuleSet
- RiverWare - 2.2 Development
First retained calibration of second generation model.
- Model - SJ_BL_2.0.1.gz
- RuleSet - SJ_BL_2.0.1.RuleSet
- RiverWare - 2.2 Development
This model has 3 additional depletions added called Unspecified1, Unspecified2, and Unspecified 3. It also uses the September, 1999 calibration.
Work continued on developing an operating ALP.
- Model - SJ_VAL_2.0.0.gz
- RuleSet - SJ_VAL_2.0.0.RuleSet
- RiverWare - 2.2 Development
This is the second generation validation model. It is essentially the same as the first generation but was rerun under RiverWare 2.2 Development. The rules were added to aggregate spatial and temporal values equivalent to those produced by the calibration and baseline models to facilitate comparisons.
- Model - SJ_BL_2.0.0.gz
- RuleSet - SJ_BL_2.0.0.RuleSet
- RiverWare - 2.2 Development
This is the first bridge ruleset. The model is essentially the same as SJ_BL_1.2.3.tar.gz (June, 1999). Correction a return flow linking error on the returns that originate in Pine basin and return to Florida basin. This model used an interim calibration.
Initial work on developing an operating ALP commenced.
All models and rulesets developed under the first generation used TCL to write operating rules.TCL is a scripting language that was called from RiverWare. Although extremely powerful, TCL is not user friendly. In addition, handoffs from RiverWare to TCL and visa versa were problematic in terms of object and units management and performance. The earliest models of this generation were provided irrigation depletion requests and diversion requests by Data Management Interface (DMI). Late in 1998, RiverWare was provided the ability to enter areas and evapotranspiration rates that are used to compute depletion requests and diversion requests. Computed irrigation requirments also use iccidental losses, system efficiencies, and headgate capacity in the calculation.
The early stages of development were highly dynamic and were pursued by a number of individuals. Reclamation concentrated on development of the validation model, calibration model, and operations common to the calibration and baseline models. Wave Engineering developed the San Juan Chama (SJC) Rules and the initial flow recommendation rules of Navajo Reservoir for the baseline model. The SJC rules were used in the calibration model as well. The first model and ruleset used to support decisions was version 1.2.3 for the NIIP Consulation. It is assumed that the oldest model presently available is 1.2.0 and that version 1.1.0 represents the early development models that are no longer available. Version 1.2.0 is the last model that used user provided irrigation depletion and diversion requests. Version 1.2.1 is the first model that computed irrigation depletion and diversion requests. Note that this modification was an engineering method change and had no affect on rules.
The following sections are the chronology of the first generation models that are available. All models and rulesets of the first generation will run using RiverWare 1.2 patchlevel 6.
- Model - SJ_Lite_1.2.3.gz
- RuleSet - SJ_Lite_1.2.3.tar.gz
- RiverWare - 1.2 patchlevel 6
The light model and rules were developed to improve performance. This model froze all data not involved in operation of Navajo Reservoir so that scenario runs could be run more quickly. This model and ruleset was used for NIIP Consultation runs. The June, 1999 full model and ruleset was the basis of this model and ruleset.
- Model - SJ_BL_1.2.3.gz
- RuleSet - SJ_BL_1.2.3.tar.gz
- RiverWare - 1.2 patchlevel 6
Fine tuned diversion rules and some configurations.
- Model - SJ_BL_1.2.2.gz
- RuleSet - SJ_BL_1.2.2.tar.gz
- RiverWare - 1.2 patchlevel 6
- Model - SJ_CAL_1.2.2.gz
- RuleSet - SJ_CAL_1.2.2.tar.gz
- RiverWare - 1.2 patchlevel 6
- Model - SJ_VAL_1.2.2.gz
- RuleSet - N/A
- RiverWare - 1.2 patchlevel 6
These rulesets improved the operations of Jackson Gulch reservoir by correcting excessive storage of water that should not have been diverted through the reservoir.
- Model - SJ_BL_1.2.1.gz
- RuleSet - SJ_BL_1.2.1.tar.gz
- RiverWare - 1.2 patchlevel 6
- Model - SJ_CAL_1.2.1.gz
- RuleSet - SJ_CAL_1.2.1.tar.gz
- RiverWare - 1.2 patchlevel 6
These rulesets modified the forecast error computations to have no less than a 10% forecast error after the peak runoff. This model also included a revised forecast error regression. These models are the first one with computed irrigation depletion and diversion request.
- Model - SJ_BL_1.2.0.gz
- RuleSet - SJ_BL_1.2.0.tar.gz
- RiverWare - 1.2 patchlevel 6
This is the oldest model and ruleset that is still available. This is also the last model that used user provided irrigation depletion and diversion requests.