My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC06848
CWCB
>
Water Supply Protection
>
Backfile
>
19000-19999
>
WSPC06848
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 9:40:16 PM
Creation date
10/9/2006 6:06:22 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System-Ray
State
CO
Water Division
5
Date
2/17/1994
Title
PRYSH-Requirements for a Colorado River Policy and Planning Model to Replace the CRSS-Draft
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.
/
56
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 />, . ~; \j 1 <br />u'jU- <br /> <br />C = C""J_' (V''-'J_' <br />''-'J <br /> <br />+ V,/,J) + CinJQinJ + Cbs}JSJ - c',-,.r-,QoutJ <br />V"".,+ V,/,J + W,QoutJ <br /> <br />(19) <br /> <br />COWJ = <br /> <br />CrUJ_t ... WtCres,t <br />1 + W, <br /> <br />(20) <br /> <br />Policies and Constraints <br /> <br />We draw the distinction between physical constraints and operating constraints, guidelines, and <br />policies, which we will refer to as operating rules. Physical constraints are constraints imposed <br />on the system due to physical design criteria. These include the elevation of the top of the dam, <br />the elevation of the top of dead storage, and maximum capacities of spillways, penstocks, and <br />outlet works, Such physical constraints will be known to each object through data input and the <br />simulator will ensure that such constraints are not violated; otherwise, a error condition exists, <br /> <br />A key concept for the modeling system will be the ability to represent the operating rules as data. <br />The model will provide the user with the ability to write, modify, add/delete, debug/trace, and <br />prioritize rules, without having to recompile the program. This will represent a major <br />improvement over the existing CRSS, providing "what-if' analysis with regard to policy. In its <br />final form, the model will allow this interaction through the GUI, eliminating the need to know <br />the detailed rule language. <br /> <br />Rules may be simple (such as target elevations for particular reservoirs) or may be more <br />complex, where a conditional statement determines whether the rule is active or not. Rules will <br />have the ability to "look ahead" to anticipate future events (such as forecasted inflow) and may <br />be dynamic in that they are formulated in terms of model variables that are determined as the <br />model runs. <br /> <br />Model Control <br /> <br />The modeling framework being developed under the Regional DSS program will allow for <br />different solution methodologies or controllers, Currently, work is on-going to allow for simple <br />simulation and a linear programming-based optimization, We anticipate that the new CRSS will <br />use a rule-based simulation approach to model control. <br /> <br />This controller will require that the simulator interact with the rule processor during a modeling <br />run, In the existing CRSS, this interaction is essentially "hard-wired" in the Fortran code. Since <br />users will be able to develop their own rules. there must be mechanisms for resolving conflicts <br />among the rules, In the Bureau of Reclamation's prototype River Simulation System (Reference <br />3), the interaction between the rule processor and the simulator was less than satisfactory. <br /> <br />9 <br /> <br />DRAFI': February 17. 1994 <br />
The URL can be used to link to this page
Your browser does not support the video tag.