Compilation of Calpuff

[Inna_Yankova]

Hi,

Does anybody has experience with compiling Calpuff under Windows? I have compiled successfully Calpuff in the past with Compaq Visual Fortran compiler with the following compiler options:

df calpuff.for /compile_only /nologo /fpe:0 /fpscomp:general /fpscomp:ioformat /fpscomp:logicals

/iface:nomixed_str_len_arg /iface:cref /optimize:0 /warn:nofileopt /traceback

I tried with Intel compiler using similar options:

ifort /nologo /fpe:0 /fpscomp:general /fpscomp:ioformat /fpscomp:logicals
/iface:nomixed_str_len_arg /iface:cref /optimize:0 /nowarn /traceback

The program compiles but when I run I get execption which I debugged in the Visual Studio and it has something to do with empty strings. There is an empty string which is read character by character. The code breaks when attempting to read an empty character.

Any help is appreciated.

Thanks,
Inna

[Les_Neilson]

I downloaded the CALPUFF code and created a simple project to compile calpuff.for using V11.1.060
The codeis about 67000 lines long.
I got *lots* of warnings re:
"#6717: this name has not been given an explicit type"
but they are not a problem.

Then at line 35000 I started getting
#5102: Cannot open include file 'params.puf'
same for 'bcs.puf' etc.
- although all of the code prior to that line managed to include the files ok so it could be that this code hits a compiler limit.

The "missing" include files then meant that other errors appeard - arrays being thought ofas functions and so on.

This meant I was not able to generate an exe and as I don't really have much time just now I am unable to look much further for you. (Perhaps later)
Sorry

Les


I just noticed at the top of calpuff.for that it includes two other fortran files
calutils.for (2730 lines) and coordlib.for(8135 lines)
Thus the resulting code size is even bigger

It would be better to make these and possibly other code into modules and USE them. That is the modern way of programming

[Steven_L_Intel1]

I was able to build and run this with the demonstration CALPUFF.INP file without errors. I did have to edit the source that reads the command line to reflect Compaq Fortran from its Lahey default.

The Intel compiler did complain about argument mismatches, but my guess is that those are deliberate so I disabled the check.

What problems are you seeing? How can I reproduce what you saw?

By the way, I did not need any special options to build and run. If you are building from the command line, just an "ifort" command should do it.

[Les_Neilson]

Mmm I wonder if I have the right version.

I got the files from www.src.com/calpuff/download/EPA_Files/Calpuff_v5.8.zip

I must admit I didn't do much other than create a solution and project, opened the calpuff.for file and selected compile. After a long wait I got the warnings about the types not being explicitly declared and then errors about not being able to read the include files. Other errors were a consequence of this.

I also noticed the argument mismatches and saw that this is because it uses an array to hold multiple data types and calls a subroutine with that array as actual argumentsin various positions,where the subroutine has dummy arguments of integer, logical etc. (I think it is subroutine setvar or something like that)
I was unable to doany further investigating after that.

Les

[Steven_L_Intel1]

I used CALPUFF 6.262.