OCR Text |
Show Final Report Hydrologic Model Analysis of the Provo River Basin 2.6 Model Coding, Documentation and Calibration The source code for PROSIM was developed based upon guidance received from the Technical Advisory Committee and the Conceptual Model Study, and the information gained from the hydrologic and water rights analyses of the Provo and Weber rivers. This section describes the development and documentation of the source code and the calibration of the model using historical data. 2.6.1 Model Coding The source code itself is written in structured FORTRAN. The more than 14,000 lines of code are organized into 175 subroutines, which are grouped into 23 files. The subsidiary program that generates virgin flows for input into PROSIM consists of 39 additional subroutines, grouped into 11 files. The groupings are by function and are intended to facilitate modifying and debugging the code. The basic operation of the source code is displayed in Figure 2- 1. A separate graphical user interface ( GUI) was developed for PROSIM. The graphical interface permits the user to edit input data, review output results, produce tabular summaries, graphically review results, and perform simulation runs. The graphical interface is written in Visual Basic for operation within the Microsoft Windows environment. A sample screen from the graphical interface is shown in Figure 2- 2. 2.6.2 Model Documentation A draft PROSIM User's Manual was prepared ( CUWCD, 1993g) to assist CUWCD staff in: 1. Running the executable version of the model by specifying the required input and output files and their formats, 2. Better understanding and using the model results by outlining PROSIM capabilities, limitations, and the design of the output files, 3. Making minor changes in the model input files to simulate different " what if" scenarios. The manual includes a description of how to set up the model to operate on a new computer system, and how to create a new or revised simulation scenario. The manual also describes model input files and output tables. The source code structure is outlined and presented in a series of flowcharts. January 1998 Page 19 |