Issue with COAWST v3.7 Installation

[yxli99-cell]

Hello, I am installing COAWST v3.7 and I have encountered an issue. I copied linux-ifort.mk to linux-mpiifort.mk and modified the FC, CC, and other variables, but when I run coawst.bash, it still shows mpif90 and -f90=ifort, and the installation eventually fails. Why is this happening? Below are the specific files.

Linux-mpiifort.mk.txt
coawst.bash.txt
build.txt

Regarding the mpif90 issue, can I modify the corresponding content in arch/archive_configure.defaults？

[jcwarner-usgs]

looks like this is a wrf issue. i see:

mpif90 -real-size 32 -i4 -ip -fp-model precise -w -ftz -align all -fno-alias -FR -convert big_endian -o module_internal_header_util.o -c module_internal_header_util.f
�[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[K32: No such file or directory
�[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kprecise: No such file or directory
�[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kall: No such file or directory
�[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kbig_endian: No such file or directory

so mpif90 is not recognizing some of the flags, like '32' 'precise' 'all' etc etc.
when you type
mpif90 -version (or something like that)
do you get that mpif90 is for gfortran?

can you try coawst v3.8?

[yxli99-cell]

looks like this is a wrf issue. i see:

mpif90 -real-size 32 -i4 -ip -fp-model precise -w -ftz -align all -fno-alias -FR -convert big_endian -o module_internal_header_util.o -c module_internal_header_util.f �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[K32: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kprecise: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kall: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kbig_endian: No such file or directory

so mpif90 is not recognizing some of the flags, like '32' 'precise' 'all' etc etc. when you type mpif90 -version (or something like that) do you get that mpif90 is for gfortran?

can you try coawst v3.8?

Thank you very much for your advice! I’m not sure which change finally did the trick, but I was able to compile COAWST v3.7 and run the Sandy test case successfully.
I have one more question: if I want to run two different projects at the same time, what is the recommended workflow?

[yxli99-cell]

looks like this is a wrf issue. i see:

mpif90 -real-size 32 -i4 -ip -fp-model precise -w -ftz -align all -fno-alias -FR -convert big_endian -o module_internal_header_util.o -c module_internal_header_util.f �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[K32: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kprecise: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kall: No such file or directory �[01m�[Kgfortran:�[m�[K �[01;31m�[Kerror: �[m�[Kbig_endian: No such file or directory

so mpif90 is not recognizing some of the flags, like '32' 'precise' 'all' etc etc. when you type mpif90 -version (or something like that) do you get that mpif90 is for gfortran?

can you try coawst v3.8?

Hello, I also attempted to install COAWST v3.8 and encountered the following error. Could you please advise me on how to resolve it?

Linux-mpiifort.txt

build.txt

build_coawst.txt

[jcwarner-usgs]

• not sure the best work flow for 2 different projects. But perhaps you could just make 2 different directories, with a copy of the code in each directory. Then you can compile WRF and roms etc with different options in each folder. keep things separate.

[jcwarner-usgs]

in the build.log i see

CMake Error at CMakeLists.txt:6 (cmake_minimum_required):
CMake 3.12 or higher is required. You are running version 2.8.12.2

-- Configuring incomplete, errors occurred!
make[1]: Entering directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build'

looks like you need to update Cmake to a higher version.

[yxli99-cell]

• not sure the best work flow for 2 different projects. But perhaps you could just make 2 different directories, with a copy of the code in each directory. Then you can compile WRF and roms etc with different options in each folder. keep things separate.

Thank you very much for your valuable suggestions — I have successfully installed COAWST v3.8.
Regarding running two projects simultaneously:
If the two projects share exactly the same coawst.bash (i.e., the same *.h file) and differ only in the namelist.input inside WRF, would it be safe to launch both cases like this?

./coawstM /test01/coupling_ocean.in &
./coawstM /test01/coupling_ocean_other.in &

Both coupling_ocean.in files point to different path namelist.input files in separate folders, while ./coawstM was built from the same .h file.
Could this approach succeed? Additionally, should the output from WRF's ./real.exe be placed in the same directory as its corresponding namelist.input file to ensure that each run finds the correct initial/boundary data?

Or should I create two separate project folders—test01 and test02—place the respective files in each, and then run:
./coawstM test01/coupling_ocean.in &
./coawstM test02/coupling_ocean.in &
so that each project has its own isolated directory and inputs? Two projects share exactly the same coawst.bash (i.e., the same *.h file)

[jcwarner-usgs]

I cant tell you what is best for you. I can only tell you this: A year from now, if you had to recreate the run, could you do that easily?
In my world, I keep all the code separate for each run. so if I need to redo that run, i am just going into that directory and sending the runscript again.

[yxli99-cell]

in the build.log i see

CMake Error at CMakeLists.txt:6 (cmake_minimum_required): CMake 3.12 or higher is required. You are running version 2.8.12.2

-- Configuring incomplete, errors occurred! make[1]: Entering directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build'

looks like you need to update Cmake to a higher version.

I would also like to ask which versions of WRF and WPS correspond to COAWST v3.8.
Can results from WRF 4.7.1 and WPS 4.6.0 be used?

[yxli99-cell]

in the build.log i see
CMake Error at CMakeLists.txt:6 (cmake_minimum_required): CMake 3.12 or higher is required. You are running version 2.8.12.2
-- Configuring incomplete, errors occurred! make[1]: Entering directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build'
looks like you need to update Cmake to a higher version.

I would also like to ask which versions of WRF and WPS correspond to COAWST v3.8. Can results from WRF 4.7.1 and WPS 4.6.0 be used?

If I have already run build_coawst.sh, do I only need to compile WPS?

[yxli99-cell]

in the build.log i see
CMake Error at CMakeLists.txt:6 (cmake_minimum_required): CMake 3.12 or higher is required. You are running version 2.8.12.2
-- Configuring incomplete, errors occurred! make[1]: Entering directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build'
looks like you need to update Cmake to a higher version.

I would also like to ask which versions of WRF and WPS correspond to COAWST v3.8. Can results from WRF 4.7.1 and WPS 4.6.0 be used?

If I have already run build_coawst.sh, do I only need to compile WPS?
WPS have been sucessul compiled.
But After compiling WRF with build_coawst.sh, I ran mpirun -np 2 ./real.exe to generate the wrfinput file, but the following error appeared. What could be the reason?
./real.exe
starting wrf task 1 of 2
Abort(336151557) on node 1 (rank 1 in comm 0): Fatal error in PMPI_Comm_rank: Invalid communicator, error stack:
PMPI_Comm_rank(107): MPI_Comm_rank(comm=0x0, rank=0x7ffd53afa7dc) failed
PMPI_Comm_rank(64).: Invalid communicator

[jcwarner-usgs]

You will have to look in the COAWST_v3.8 directories to see the versions of the WRF and WPS code.
I am not sure the compatibility of other versions of WPS to what we have in COAWST.

If you want to run real.exe, then i suggest you make a folder, put COAWST in there, compile for just WRF, and then run WPS and real etc. Then either
change the .h to add roms and recompile,
or,
make a new folder and put COAWST in there, and recompile with all the options.

sometimes you need to run real as an mpi job
mpirun -np X ./real.exe
it usually works with just 1 processor.

[yxli99-cell]

in the build.log i see

CMake Error at CMakeLists.txt:6 (cmake_minimum_required): CMake 3.12 or higher is required. You are running version 2.8.12.2

-- Configuring incomplete, errors occurred! make[1]: Entering directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /data2/share/elpt_2025_001148/yxli/COAWST_v3.8/SWAN/build'

looks like you need to update Cmake to a higher version.

Thank you for your previous advice. I have a new issue:
Could you please tell me what causes the following error when I run
mpirun -np 2 ./coawstM Projects/windfarmno/couping_sandy.in?
Abort(604624900) on node 1 (rank 1 in comm 0): Fatal error in PMPI_Send: Invalid tag, error stack:
PMPI_Send(159): MPI_Send(buf=0x7ffef6c088f8, count=1, MPI_INTEGER, dest=0, tag=155291648, MPI_COMM_WORLD) failed
PMPI_Send(97): Invalid tag, value is 155291648

If I change the parameters to NnodesATM = 1 and NnodesOCN = 1, the run fails immediately. At which step does the problem occur? Could the problem be that I chose mpiifort while build_coawst.sh was actually using mpifort?

sandy.h.txt
coupling_sandy.in.txt
ocean_sandy.in.txt

[jcwarner-usgs]

you dont want this:
#define MCT_INTERP_OC2WV
you dont have the waves on. turn that off and recompile. see if that helps.