Program Translation - Nov. 14, 2013

[William Ray Wing]

On Nov 16, 2013, at 4:31 AM, Terence <tbwright at bigpond.net.au> wrote:

> I downloaded the packed file mentioned, extracted the files and had a look
> at the Fortran sources given:
> ETGTAB.FOR and ETGTAB.F
> 
> The ETGTAB.FOR file had double spacing, which Iremoved automatically, then
> compared the two sources automatically (passing and copying equals and
> offering choice between lexically different lines).
> 
> The two files were now very nearly identical, but the .FOR file had some
> CALLs to GEOEXT(IUIT6,DEXTIM) which were commented out in the other; also
> calls to LAHEY timing functions not used in the .F version (and a minor
> change in two format statements which effectively just changed the shift in
> the output report).
> 
> I don't see why not either source (given access to the external GEOEXT, etc,
> fuctions) shouldn't be left for compilation (and later running) by any F77
> or later compiler. The code is still valid.
> 

Then, use F2PY to put a python wrapper around the code, and it could easily be incorporated into the python workflow that the OP was originally asking for.

-Bill