WSPC01928 - Laserfiche WebLink

Home Browse Search

Introduction " 7"k .,""';.,Ib..... Data' J,'<!lJi f1.' 1.5.3 Network: The Network File furnishes HYDROSS with a physical description of the study area: how the stations connect, physical facilities (reservoirs, power plants, canal capacities, etc.), and supply requirement locations (for diversions, instream flow requirements, return flow points, etc.). The connection to the operational parameters is through the use of table numbers, which are then used as pointers to the data in the Table File. . The components of the network data are discussed in Section 4 [Page 23], and the file structure is detailed in Appendix B.5 [page 41]. Preparation of a Network File to accurately model a river basin requires a very thorough understanding of the network components and how the model utilizes them. While a straight _ recitation of the system capabilities makes pretty dry reading, it is important to keep in mind that each of the system capabilities is a tool (or part of a tool) to model the system. -"'-'" 1.6 Files For each of the three basic types of data discussed in section 1.5 [Page 4], HYDROSS requires a source file which must be created by the user. THESE FILES MUST BE PURE ASCII WITHOUT ANY CONTROL CHARACTERS (I.E. NO TABS OR FORM FEEDS). The three required source files are the flow source file, the table source file, and the network source file. The user must also create an input file for the compute module (H400) and an input file for . the report generator (H450). If other than the defaults units and/or precision of the report output is desired, then a units file will also need to be generated by the user. Do NOT MODIFY ANY FILE CREATED BY THE MODULES! IF YOU HAVE TO MAKE ANY EDIT CHANGES, MAKE THEM TO THE SOURCE FILE(S) AND RE-RUN THE RESPECTIVE MODULE(S) (See section 1.7 [Page 6]). For convenience we use the following 'symbols' to refer to the actual files. The user created files are marked below with an asterisk" *" . FLOS* Flow ~ file. The format for this file is discussed in section B.1 [page 37] FLOB Flow File, created by module H420. Look but don't touch. If you have to make any edit changes, make them to the source file and re-run module H420. TBLS * Table ~ file. The format for this file is discussed in section B.3 [Page 39] TBLB Table File, created by module H410. Look but don't touch. If you have to make any edit changes, make them to the source file and re-run module H410 and H430. NETS* Network ~ file. The format for this file is discussed in section B.5 [Page 41] NETB Network File, created by module H430. This is a true binary file. Module H430 pre-processes NETS into NETB with the help of TBLB; NETB is then a checked-out Network File for input to the compute module H400. INPC * Input file for the compute module H400. Contains title, years of study, and initial reservoir contents. The format for this file is discussed in section B. 7 [Page 49] INPR * Input file for report module H450. Contains years of reports and list of desired reports. The format for this file is discussed in section B.8 [Page 50] ODS Output file from compute module H400, input to report module H450. An ASCII file of 150-character records. UFIL * Optional input to module H450, controls the units and precision of the output reports. This file is only needed if the user wants to specify other than the default units of measurc and/or number of decimal places (for defaults refer to Appendix B.10 [Page 63]). The format for this file is discussed in section B.10 [Page 63] REPT Output from report module H450, to be routed to your printer. RPRN Output from report module H450. This file is in "Commas and Quotes" format and can be loaded into most any commercial spreadsheet or database program. This file is created only if requested in the INPR file. GRF Graphics file. Contains an ASCII character "map" of the system. March 25, 1991 HYDROSS 4.1 Page 5