COAWST compilation

[smrhashemi]

Hello

I have been able to compile the COAWST code for UPWELLING case (Just ROMS) and then inlet test case which involves SWAN and ROMS coupling without any problem problem.
Using the same buildcoawst.sh file,
I started to compile the code for another applications which involves ROMS-SWAN and WRF (JOE_TCs). I configured the WRF in terms of the netcdf and compiler option, but the compilation proceeds for about 15min and stops with this error.

ifort: error #10236: File not found: 'WRF/main/module_wrf_top.o'


I would apprecaite any input to remove this error.
thanks
Reza

[jcwarner]

Reza-
I have seen this before. IT can be one of several things. Do me a favor, and type this:
script build.log
./coawst.bash
exit
and then send the build.log file to me at
jcwarner@usgs.gov
we can go from there.
thanks,
-john

[smrhashemi]

Thank you John. I am very sorry for the late reply, I was expecting to get an email if somebody replied to my post. I should have checked the forum instead.
Anyway,
I looked at the log file of the build and although I have put the right path for the MCT directories in ROMS compilation file, WRF still doesn't find the right path.
To fix that, I checked the configure.wrf and changed MCT_LIBDIR ?= /usr/local/mct/lib which is not the case for me to the right path,
MCT_LIBDIR ?= /home/reza.hashemi/MCTfiles/lib
Apparently, when I look at the log file, WRF still wants to find files from (/usr/local/mct/include) which should be /home/reza.hashemi/MCTfiles/include


thank you for your help
Reza

[jcwarner]

did you set
MCT_INCDIR and MCT_LIBDIR
in your environment?
the configure.wrf get overwritten for each build, so dont make the changes in that.

[smrhashemi]

Thanks. I added two lines in configure.wrf to define the MCT include and library files
the compilation now finishes and makes coawstM file. Unless i do clean and reconfigure wrf, it is not overwritten in my case.
In roms, I have defined these MCT paths in compiler fortran setting file.
Do you mean to put these setting into build.sh?
Thank you


Reza

[jcwarner]

actually, to build roms by itself,you should set your environment variables using something like
setenv MCT_LIBDIR=/usr/local/lib or whatever it is.
this line shuold be in your bash shell or profile or someplace like that.
that way it is in your personal settings, and if you update your roms code or whatever, that information will not be lost.

[smrhashemi]

Many thanks John. That make sense. I have done this for other models as you say.
That solves the problem

Reza