SJRIP Model and RuleSet Inventory
The following table lists all official models and rulesets and provides links to the models, rulesets, log, and scenario runs. Model and ruleset naming conventions are discussed below the table.
The hydrology model and associated operating rules are in the third generation of evolution. The first two generations used hydrology data developed by Reclamation for 1970-1993 and extended historically to 1929 by Keller-Bliesner Engineering using Colorado River Simulation System hydrology data. The third generation uses Colorado Decision Support System (CDSS) data. The first 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. The configurations of the third generation gains, validation, migration, and models will available as hypertext documents.
Third Generation Models and RuleSets | |||
Date | Model | RuleSet | Description |
First Generation Models and RuleSets | |||
Date | Model | RuleSet | Description |
July 1999 | SJ_Lite_1.2.3.gz | SJ_Lite_1.2.3.tar.gz | NIIP Consultation model |
June 1999 | SJ_BL_1.2.3.gz | SJ_BL_1.2.3.tar.gz | NIIP Consultation model |
May 1999 | SJ_VAL_1.2.2.gz | N/A | Corrected Jackson Gulch Validation model |
May 1999 | SJ_CAL_1.2.2.gz | SJ_CAL_1.2.2.tar.gz | Corrected Jackson Gulch Calibration model |
May 1999 | SJ_BL_1.2.2.gz | SJ_BL_1.2.2.tar.gz | Corrected Jackson Gulch Baseline model |
November 1998 | SJ_CAL_1.2.1.gz | SJ_CAL_1.2.1.tar.gz | First calibration model with acres and rates |
November 1998 | SJ_BL_1.2.1.gz | SJ_BL_1.2.1.tar.gz | First baseline model with acres and rates |
October 1998 | SJ_BL_1.2.0.gz | SJ_BL_1.2.0.tar.gz | Oldest Available Baseline TCL model and ruleset |
September 1998 | N/A | N/A | N/A |
The following model and ruleset conventions were employed:
Basin - Identifier that tells the watershed of the model such as SJ.
Type - Identifier that tells the type of the model as BL, CAL, Val, etc.
Qualifier - Optional field that specifies special subtypes or
scenarios.
Model or ruleset version - version number that corresponds to a specific configuration, data set, scenario, and generation as version number.
File type - Identifies if a model or ruleset as Model or RuleSet.
Underscores are used to separate basin and type from version numbers. Decimals are used to separate subversions. The ‘Qualifier’ attribute will not be used for models and rulesets that use the primary configuration.
Uncompressed RiverWare models have a “.Model” extension. Compressed RiverWare models have extensions like “.zip”, “.gz”, or “.Z”. RuleSets have a “.RuleSet” extension. The first generation rules (TCL) are linked to a compressed 'tar' file because the rulesets consist of numerous individual TCL files in mulitple subdirectories. The naming convention was applied to the compressed 'tar' file with a "tar.gz." extension instead of 'RuleSet'.Validation models do not need a ruleset to run since they are purely mass balance models. However, a 'RuleSet' was developed for the second generation validation model to compute spatial and temporal aggregations for comparison purposes.
Additional explantion of the naming convention is available.
Last Revised: 4/11/2006