My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC05517
CWCB
>
Water Supply Protection
>
Backfile
>
18000-18999
>
WSPC05517
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 11:09:45 AM
Creation date
10/9/2006 5:15:08 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
10/16/1992
Title
PRYSH-River Simulation System-Technical Reference Manual
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.
/
62
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 />, , PU G 1 78 <br /> <br />Opera lion Policies in RSS <br /> <br />POLICY sumsto TO_DETERMINE sum_storage FOR ResDown <br />BEGIN <br />sum_storage = ResUp.Beginning_storage <br />+ ResDown.Beginning_storage <br />END <br /> <br />A second poficy statement would use this new variable 'sum_storage" to define <br />the release from 'ResOown": <br /> <br />POLICY D release TO DETERMINE Outflow FOR ResDown <br />BEGIN <br />Outflow = 0.3* sum_storage <br />END <br /> <br />These last two policy statements named 'sumsto" and 'O_release" are equiva- <br />lent to the policy statement named "O_outflow" above. <br /> <br />The "O_release" policy statement above could also be written as a conditional <br />policy statement. The condition checks on the existence of a policy statement <br />defining the variable 'sum_storage". <br /> <br />POLICY resrel TO DETERMINE Outflow FOR ResDown <br />BEGIN <br />IF sum_storage <br />THEN Outflow = 0.3*( sum_storage) <br />END <br /> <br />This example has focused on the distinction between the two types of variables: <br />slot variables and user defined variables, Before leaving this topic and this <br />example, note that the underscore "_~ was used to connect muitiple words into a <br />single variable_ The names of user defined variables are entirely the choice of <br />the user. If, for example 'sum_storage" is objectionable, other options are to use <br />what was common to those working with early versions of programming <br />languages that limited words to only a few characters, say SUMSTO or <br />TOTSTO, or to replace underscoring with a mix of upper case and lower case <br />letters, for example, SumStorage or TotalStorage. <br /> <br />Summary <br /> <br />In summary, the user can define any variable names desired. If a value of a slot <br />is to be assigned to a variable, that slot reference must be the name of the slot <br />preceeded by the object name. A period (.) separates the object name from the <br />slot name, Variables to be determined may not contain any periods or spaces. <br />Periods are reserved for separating an object name from the data slot variable <br />name. User-detined variables contained in the headers of policy statements <br />may be used in the body of other policy statements. <br /> <br />Operators <br /> <br />Policy statements define the variable identified after the 'TO_OETERMINE" <br />keyword in the header, Each definition contains an equals (=) sign separating <br />the variable whose value is to be determined on the left from some expression <br />onthe right. Any combination of the +, -,', I and exponentiation" operators <br />may be used in an expression, If an expression includes division, it is often wise <br /> <br />Operation Policies in RSS <br /> <br />23 <br />
The URL can be used to link to this page
Your browser does not support the video tag.