Laserfiche WebLink
<br />Oull208 <br /> <br />During the detailed design task of this project, we will be performing a post-mortem analysis of <br />the RSS implementation and will provide that information to interested parties. We will also <br />examine the implementation in CRSS and provide that information as well. <br /> <br />3 Data Requirements <br /> <br />General Data Requirements <br /> <br />The model will require the following categories of input data: <br />run control data <br />basin network data <br />hydrologic data <br />demand data <br />operating rule data <br /> <br />The model must provide output data representing the state of the system and all decision <br />variables at each time step and provide aggregation functions for reporting state parameters and <br />decision variables over both temporal and spatial horizons. The display and analyses of input <br />and output data is discussed in more detail in the section on Analysis Tools. The user will be <br />able to specify the units of the input and output data, <br /> <br />Run Control Data <br /> <br />Run control data will include the run parameters such as the beginning and ending month and <br />year, whether multiple runs are being requested and if so, what hydrologic and demand data will <br />be used for each run. Initial conditions for the system will be specified, including reservoir <br />volume, elevation, or area, as well as concentration of salt. A multiple-run manager will be <br />provided to aid the user in the setting up and tracking of multiple runs. <br /> <br />Basin Network Data <br /> <br />Basin network data will define all the attributes for every object specified in the network, This <br />data will include the geometric information such as volume-elevation-area coefficients of the <br />reservoirs, Also included will be hydropower and sedimentation information, and all physical <br />data that represent physical constraints, This data for the Colorado River System is given in <br />Appendix A. <br /> <br />The connections between the objects (network topology) will be provided by the model itself <br />through the user interface functions that allow for interactive model building and editing, <br /> <br />Hydrologic Data <br /> <br />The model will utilize the natural flow and salt loading data as used in the current CRSS. This <br />data will be available in an ASCII format and will not require any preprocessing to be used. <br /> <br />10 <br /> <br />DRAFT: February 17, 1994 <br />