Laserfiche WebLink
<br />Policy or rule base <br /> <br />'. <br /> <br />RSS Concepls and Methodology <br /> <br />.. <br /> <br />'.. ::~ <br />}' <br /> <br />'" <br /> <br />'Reservoir_class <br />State Info <br />Slots <br />inflow 1 <br />Water_class inflow-2 <br />State Info Outflo; <br />Slots diversion <br />inflow_1 beginning_storage <br />inflow_2 ending_storage <br />outflow evaporation <br />diversion Policy_statements <br />Node~cla~s Policy_statements Functions <br />State Info Functions mass balance <br />Slots mass_balance bank3torage <br />Policy_statements evaporation <br /> <br /> <br /> <br />LTOO._cl~ <br />State Info <br />Slots <br />series1 <br />series2 <br /> <br />) . <br />Policy-statements <br /> <br />'FI~URE.1. Typical object data slots associated w~h various object types. <br /> <br />. understand given their simple if-then format. Another advantage is the ease in <br />which operating policies can be changed by the user (without the need of a <br />programmer) in performing numerous 'what if" simulations, Furthermore, such <br />policy statements offer much more flexibility than what has been incorporated into <br />most other interactive river simulation system programs in which users can alter <br />the input data to change the operating policies being simulated. <br /> <br />Policy statements are stored in the rule- or polley base. They can be attached to <br />their objects prior to simulation, after which the policy statements become active <br />during actual simulation runs. <br /> <br />Figure 2 illustrates the general format or syntax of the policy statements used in <br />the RSS program. Users are able to define their own variables in these policy <br /> <br />6 <br /> <br />RSS Concepts and Methodology <br />