allocatable array or pointer is not allocated-- when run metgrid.exe in WPS

[Fanglin__Sun]

I used XE2011 to compile WRF and WPS. When ran metgrid.exe, it gave error like the following:

Processing domain 1 of 3
./TAVGSFC
WARNING: Couldn't open file ./TAVGSFC for input.
Processing 2006-06-10_00
FILE
forrtl: severe (153): allocatable array or pointer is not allocated
Image PC Routine Line Source
metgrid.exe 000000000060161A Unknown Unknown Unknown
metgrid.exe 0000000000600195 Unknown Unknown Unknown
metgrid.exe 00000000005AA316 Unknown Unknown Unknown
metgrid.exe 000000000054C585 Unknown Unknown Unknown
metgrid.exe 0000000000588523 Unknown Unknown Unknown
metgrid.exe 000000000047D239 Unknown Unknown Unknown
metgrid.exe 000000000044F708 Unknown Unknown Unknown
metgrid.exe 000000000044BB82 Unknown Unknown Unknown
metgrid.exe 000000000040B5D1 Unknown Unknown Unknown
metgrid.exe 0000000000403BAC Unknown Unknown Unknown
libc.so.6 00000034BFE1EC5D Unknown Unknown Unknown
metgrid.exe 0000000000403AA9 Unknown Unknown Unknown


Hope someone here can help solve it.

[mecej4]

Unless there are grounds to believe that the Intel compiler is behaving differently from other compilers or there is a question about how to set the options for the Intel compiler, support for debugging complex programs such as WRF is more likely to be found in a forum/board dedicated to the users of the package.

In this particular case, the message is straightforward enough: an input file called TAVGSFC was not found in the expected place (the working directory). You have to read the WRF documentation to find out what this file should contain, where it should be kept, etc.

You can turn on the compiler option -traceback to let you see line numbers in the traceback printout.

[Ron_Green]

I agree, WRF is so complex it could be anything in your problem setup, input files, etc. But just to be sure, have you read the Knowledge Base articles we've published on building WRF with the Intel compilers? At the front page for this forum, at the top are some links. One of these is to "Search the Knowledge Base". Use that and use "WRF" as your search string.

and along with -traceback add -g to get symbolic information in your stack traceback.

If you have built WRF correctly with the Intel compilers, then go to the WRF forum http://forum.wrfforum.com/ and see if you can get help with your problem setup. This does not look like an Intel problem.

[Fanglin__Sun]

Thank you all. Usually the TAVGSFC does not matter, that means metgrid.exe will go on produce files expected by WRF.

I will follow your suggestion.

[Fanglin__Sun]

Not sure, Because WRF was build well already, but couldn't run with files produced by WPS (which was compiled using PGI, and also WRF using PGI worked) . When I tried to prepare input data using WPS compiled by Intel, the error above occured.

[Jeremy_Gibbs]

Have you come up with a solution yet for this? I am running into the same issue.

[mecej4]

You would have a better chance by asking in a forum which users of the package are more likely to frequent. Questions regarding how to run third party packages is not something that is reasonable to ask a compiler vendor to help with.

In the present case, the issue is : is the file in question an input file that the user is supposed to provide? Will the package generate default inputs if one is not provided? Will it save a file with these default values for the next run?

Please read responses #1 and #2.