Re: Need Help: compiling old Fortran program

Förster vom Silberwald wrote:
....

Things are being more complex now. Another team of researcher from the
other side of the bond is ready to hand over a Matlab interface to the
code. I wrote them that the basic Fortran code is broken. However, I
am still waiting on their interface. Could be they fixed the code. I
will see.

Rewriting the code would be cumbersome and not doable in a limited
time. Moreover, I am not specialised in inversion methods related to
atmospheric sciences.

Nevertheless, I guess a lot of papers are based on that particular
code. The principle method as dealt with in the code is described in a
paper and I assume some people have implemented it from scratch.

I posted the f90 and g77 output because I had expected that any f90 or
f95 does handle Fortran 77 code in a more restricted way as opposed
to Fortran 77 compilers.

Yes I got the message: the code is seemingly broken.

If the problems in compiling are limited to the examples you posted or similar, it would seem at least reasonably straightforward to modify them as suggested and compile the code. In an ideal world there would be at least one or two published results from which one could get sufficient information to try to duplicate those results to ensure consistency (or confirm an inconsistency). At that point either way, one would have a clearer idea of where one stood.

I suspect most regulars in this forum have been in a similar situation in the past -- I certainly have. Sometimes it's hard to be the guy in front of the train holding up the flare trying to stop the potential train wreck because a flood has weakened the bridge ahead. Maybe it will hold, maybe it won't. The project leaders look at schedules and budgets but it's the researchers' responsibility to ensure the train gets across safely...

imo, ymmv, $0.02, etc., etc., ...

Good luck, sounds like you're going in need of some.

OBTW, one last thought -- have you attempted to find out the compiler/OS/machine the code has run on in that past? If there were _any_ chance of either repeating a run on that platform w/ the original code and the modified version, that would be an ideal starting point...

--


.

Relevant Pages

  • Re: Is it time to legitimise REAL*8 etc?
    ... Some vendors phased out their F77 compilers over 10 ... No need to support a seperate F77 compiler as, ... experience with F77) that the F95 programming is safer than the F77 ... Authors are not chosing more recent Fortran ...
    (comp.lang.fortran)
  • Re: what is the most suitable Linux platform for Programmers and software developers
    ... C, C++, Perl, Python, Lisp, and a bunch of other languages are supported ... There are FORTRAN compilers, but FORTRAN ... Look at the Linux ...
    (comp.os.linux.misc)
  • Re: Is it time to legitimise REAL*8 etc?
    ... Some vendors phased out their F77 compilers over 10 ... No need to support a seperate F77 compiler as, ... experience with F77) that the F95 programming is safer than the F77 ... COMMONs remain available with any FORTRAN version. ...
    (comp.lang.fortran)
  • Declaration to get 8-bit (or 16-bit) integer?
    ... Supported by all the current compilers that I've tried it on. ... Not likely to become standard in the foreseeable future. ... Syntax standard-conforming, but semantics not guaranteed of course. ... The meaning of the code not obvious to anyone but a Fortran guru. ...
    (comp.lang.fortran)
  • Re: Casting malloc
    ... If he can make a strong case for the diagnostics, ... Uh, again, Fortran is a better tool for some sorts of work. ... familliar what Fortran compilers only in the code they generate; ... Given a variety of hard problems, Fortran consistently came up much faster with default code and no explicit optimizations. ...
    (comp.lang.c)