Laserfiche WebLink
<br />{j . , " l r; <br />'v .1.11 <.0 <br /> <br />SCRIB2.FOR was adjusted to include pumped water and water lost to the <br />sediment adjustment. <br /> <br />. Double precision capability was implemented by including the global statement <br />IMPLICIT DOUBLE PRECISION A-H, O-Z in each subroutine and function. <br />The only real variables which are not currently double precision are those <br />associated with reading the Binary data generated by MHYDRO. (Note: To allow <br />these variables to be double precision, would have required editing MHYDRO). <br />Once the variables provided by MHYDRO are read as single precision, they are <br />recast to double precision. <br /> <br />In addition, to complete the conversion to Double preCIsIon, the following <br />subroutines or functions were edited: HYDRBAL, INITIAL, RULES, SEDADJ, <br />AF, and VOL. They were adjusted as follows because a constant value (ex <br />elevation 9010.0) cannot be passed in a calling argument which expects a double <br />precision variable. <br /> <br />OLD <br />VNV6010 = VOL(INA V, <br />60 I 0.0) <br /> <br />NEW <br />x6060=6010.0 <br />vnv6010 = vol(inav, <br />x601O) <br /> <br />. Sedimentation which accrues in a reservoir is used within CRSM to adjust the <br />reservoir area-capacity relationship and reservoir storage prior to beginning the <br />next time step of the simulation in subroutine SEDADJ.FOR. By adjusting <br />storage, water is lost. To confirm this concern was responsible for the observed <br />reservoir imbalance and provide a simple mechanism to investigate alternative <br />methods to account for sediment accumulation, CRSM91, INITIAL, and <br />SEDADJ were revised to provide the user the ability to 1. Operate as originally <br />programmed. 2. Not adjust sediment (do not call SEDADJ), 3. Call the sediment <br />adjustment but put all sediment inflow into the dead storage pool and do not <br />adjust the elevation-area-capacity relationship. These options, which are specified <br />in the file CRSM91.RSP, allow the user to choose which method he or she wishes <br />to implement and confirm the model can maintain continuity. <br /> <br />. Two branch logical if statements were revised. For example: <br /> <br />OLD <br />IF(A.EQ.B) 100,110 <br /> <br />NEW <br />if(a.eq.b) goto 100 <br />goto 11 0 <br /> <br />. Data statements were revised. For example: <br /> <br />4 <br />