Laserfiche WebLink
<br />001982 <br /> <br />Each object has many slots. Slots are essentially place holders for information associated with that <br />object. For example, a storage reservoir has slots such as inflow, outflow, storage, evaporation, <br />elevation and volume tables, etc. To a great extent the slots available depend on the methods selected <br />by the user. Most objects have different methods available that allow the user to customize the <br />physical behavior of an object. For example, when setting up the reservoir evaporation calculations <br />the user must select from a list of evaporation methods. The appropriate slots are then added to the <br />reservoir object and the user provides the necessary data. After the objects are put into the <br />workspace and the appropriate methods are selected, they can be linked together so that information <br />from one object is propagated to another object. The outflow of a reservoir may typically be linked <br />to the inflow of a downstream reach object. Thus by selecting appropriate objects and methods and <br />linking the objects together, a river basin network is formed. <br /> <br />The following is an excerpt from the CADSWES RiverWare web page (hltp://cadswes.colorado.edul) <br />and was provided by the Bureau of Reclamation. It further describes basic functionality and features <br />of RiverWare. <br /> <br />With RiverWare you can: <br /> <br />. Model Any Basin. Select generic basin features from a palette, name the features, and <br />link them together to create your basin topology. <br /> <br />. Customize Your Model. Select the appropriate physical process equations for each basin <br />feature. Choose units for entering and displaying data. <br /> <br />. Create your own data icons for holding special data for policies or user-defined functions. <br />Configure plots and spreadsheet-like views of the data. <br /> <br />. Express Operating Policy as Dynamic Data. Get maximum flexibility and ease of use <br />thanks to RiverWare's ability to express operating policy as user-defined data. Because <br />policy is not compiled into the code, you have easy access to create it and modify it. <br /> <br />. Simulate or Optimize. Switch easily between pure simulation, rulebased simulation, and <br />optimization. RiverWare's integration of these modeling approaches in one package makes <br />it possible. <br /> <br />. Schedule, Forecast, and Plan. Manage daily scheduling, mid-term forecasting, and long- <br />range planning by using RiverWare's flexible and innovative utilities. Easily modify the <br />model to apply to new design studies or the analysis of operating policies. <br /> <br />RiverWare continues to evolve. Most of the development of the San Juan RIP Hydrology Model <br />was done under RiverWare version 1.2 patch level 1. In late July 1998 a migration was made to <br />RiverWare version 1.2 patch level 6. This version incorporates a new method that allows calculation <br />of diversion and depletion requests based on acreage and evapotranspiration. The development of the <br />SJRIP Hydrology Model pointed out the need for additional objects and methods within RiverWare. <br />Patch level 6 mentioned previously was the result of one of these needs. Other RiverWare changes <br />spawned by this study include: <br /> <br />DRAFT - SJRIP Hydrology Model Documentation <br />June 18, 1999 <br /> <br />43 <br />