Laserfiche WebLink
u.. . <br /> <br />The first line contains the title which describes the data <br />C~ file. The maximum length of TITLE is 80 characters. The ID is <br />~ the 8-digit identification code of a node. I1'R and C are the <br />water year and the monthly data associated with that water year <br />~ as described above. The ID's and IYR in the file should be in <br />ascending order. Each C element is a monthly mean strramflow <br />)• <br />for a given water year IYR. This file is not optional and should <br />~ be supplied by the user prior to executing the WATBAL program. <br /> <br />•} 7.4 The WATBALP Module <br />--- ------- ------ <br />~ Structurally, WATBALP is very similar to WATBALC except <br />instead of having Lhe option of computing data from correlations, <br />all the input data must be read from data files. In addition, <br />. execution of WATBALP requires the specification of a "base" year <br />or years from which the calibrated data are selected for a given <br />~ model run. All data related to the "base" years in the <br />~ calibrated data file (CFTC) will be used as input. for the nodes <br />described in the streamflow network system. The user may <br />~ override she calibrated data by supplying data for any node in <br />~ the system through the mine plan data file (PFIL). <br />Fundamentally, the water-balance analyses performer by the <br />~ WATBALP and the WATBALC modules are different. In the WATBALC <br />analysis, Lhe flow and water quality for a node are calculated <br />from the input data (marked as "I") of the node(s) immediately <br />~ upstream. Whereas, in the WATBALP calculations, the hydrological <br />quantities are obtained from the predicted data (marl~:ed as "U" or <br />"P") of the node(s) immediately upstream from that same node. <br />The "U" and "P" data will be e~cplained lacer. <br />Ex. 13-15 <br />