Laserfiche WebLink
<br />Object-oriented <br />structure <br /> <br />Networks of objects <br /> <br />RSS CcnC6pls and Melhodology <br /> <br />1, <br /> <br />RSS Concepts and Methodology <br /> <br />~;~~ <br />,I <br /> <br />The simulation procedure used in the River Simulation System program is based <br />on its object-oriented structure. Individuals using this program will benefit from an <br />understanding of the main features of the program's objects and their operation. <br />The RSS model structure and event-driven simulation procedure differ substan- <br />tially from that of other time-driven river simulation system models such as HEC-5, <br />IRIS, MITSIM, and MODSIM). <br /> <br />This section of the User's Manual provides an overview of both the object- <br />oriented structure of the program and its simulation procedure. This overview is <br />designed to assist users of the program. Programmers responsible for model <br />updating and maintenance and others wishing more detail should refer to the <br />Programmer's Reference Manual. Those new to RSS may wish to use the RSS <br />Tutorial to become better acquainted with some of its essential features. <br /> <br />1.1 River System Network: <br /> <br />In RSS, river systems are represented by node-link networks. The nodes of each <br />network represent components or objects. These component objects include sites <br />where two tributaries or streams join together (confluence nodes), where reser- <br />voirs store and release water (reservoir nodes), and where diversions or with- <br />drawals of water take place (diversion nodes), All of these types of component <br />objects are called water objects. Non-water objects or components include the <br />sites where input data needed for the simulation are kept and where output data <br />resulling from the simulation are stored and possibly analyzed. These non-water <br />component objects are also known as Inputloutput tables. <br /> <br />Water objects can also represent river or stream reaches where evaporation, <br />seepage or routing takes place (reach objects). River reaches are not required if <br />the water flowing into each reach equals, in each simulation time period, the water <br />flowing from that reach, <br /> <br />The links of a node,link network in RSS primarily serve to transfer information <br />among the system's nodes, This information includes, but is not limited to, water <br />or flow data, Information of all types can travel through a link connecting any two <br />nodes. <br /> <br />4 <br /> <br />RSS Concepts and Methodology <br />