Laserfiche WebLink
<br />n.40 , ~ or.. r <br />ulJliOL <br /> <br />. Character read commands were revised using standard FORTRAN read, write, <br />and format statements, This revision allowed the original program's use of <br />ENCODE and DECODE to be eliminated and resulted in a simpler, ported model. <br /> <br />OLD <br />DIMENSION A(8), X(8) <br />CHARACTERA*8 <br />READ (1,100) A <br />ENCODE (A,IIO) X <br /> <br />NEW <br />dimension x(8) <br />character dummy*2 <br />read (1,100) dummy, x <br /> <br />. Equivalence statements were revised to include a consistent number of <br />subscripts as follows: <br /> <br />OLD <br />DIMENSION A(5), B(1,5) <br />EQUIV ALENCE(A(1), <br />S(l) ) <br /> <br />NEW <br />dimension a(5), b(I,5) <br />equivalence (a(1),b(I,I)) <br /> <br />COMMENTS AND CONCERNS <br /> <br />Following are comments and concerns which resulted from the porting ofMHYDRO: <br /> <br />. The documentation for MHYDRO refers to a larger data base than is required for <br />executing CRSM, It appears the original code read that database, The ported <br />model reads a punched output, and not a ported version of the original database, <br />Therefor, it is not surprising that the input subroutines of the original program had <br />to be revised during the porting, <br /> <br />. Binary data created by MICROSOFT FORTRAN is not the same as binary data <br />created by LAHEY FORTRAN, Therefor all porting was performed using the <br />LAHEY FORTRAN compiler, <br /> <br />. To create a file for CRSM requires the direct access files FILE11.DIR and <br />FILEl2,DIR be constructed, This required using a separate utility provided with <br />MHYDRO named OPEN40.FOR. Therefor the following procedure was used to <br />generate an input file for CRSM. <br /> <br />4 <br />