Laserfiche WebLink
<br />data, depending upon the computer system, Before loading the source <br />deck, the unit could be redefined by changing a nominal number of <br />Fortran statements. <br /> <br />It is possible to enter the river hydrograph based on a different <br />but longer time interval than the routing time interval by using Jl <br />card input variables NXRPV and KLAG. When doin~ this, a minimum of <br />four river hydrograph values must be input, The program fits a spline <br />curve to the river hydrograph points (4 points at a time) and then <br />interpolates intermediate hydrograph points. Two of the input river <br />hydrograph pOints must represent values prior to the start of the routing <br />computation and two must also occur after the last routing time interval, <br />Thus, KLAG < - (NXRPV + 1), KLAG is always < 0, If the first river <br />hydrograph pOint corresponds to 21 routing time intervals before the <br />first routing time interval, KLAG = -21 and NXRPV must be < 20. KNRQ <br />must be specified when using this option. <br /> <br />6. OUTPUT <br /> <br />a, Output is by a l32-column printer, An example of program output <br />is shown in Exhibit 4; all output begins with a listing of input data <br />used, followed by a detailed prin~out as illustrated, <br /> <br />b, A feature of the program enables the user to have the time shown <br />in the output either in terms of hours or hours, day, and month, <br /> <br />c, It is possible to obtain extensive sequential output and/or sum- <br />mary output. <br /> <br />d, Output data is as follows: 1) River elevation and flow is end- <br />of-period; 2) Ponding area inflow and outflow is average; 3) Ponding <br />area elevation, storage, and area is end-of-period. <br /> <br />7, PROPOSED FUTURE DEVELOPMENT <br /> <br />No future development is now contemplated by HEC or San Francisco <br />District personnel, There are, however, three modifications which may <br />be effected by program users if they would make the program more functional <br />for the user: <br /> <br />(1) Alter the program to accept pond elevation minus river ele- <br />vation head vs, pump discharge data rather than the presently used pond <br />elevation vs. pump discharge relationship; this would, or could, take the <br />siphoning action of pumping over a levee into account, <br /> <br />(2) The pump criteria could be further altered, if required, to <br />accept data from pumps (single- or multi-stage) turning on and off at <br />different elevations. In effect, this can already be done using the <br />variable pumping versus pond elevation relationship, <br /> <br />4 <br />