You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am trying to run ww3_tp2.14 on Ubuntu 24. All previous tests in the matrix compile and run. However, with ww3_tp.14, I get the following error during the compilation:
Since the MPI flag is not set the MPI libraries are not linked. The reason for the error not occurring for other users is likely that their MPI library is in one of the other directories that are included. A fix might be to include a special rule in the CMakeLists.txt to enforce that w3agcmmd.F90 is always linked to MPI.
Another fix might be to use preprocessor directives in w3agcmmd.F90.
If this is considered useful, I could try a fix using one of the two approaches.
The text was updated successfully, but these errors were encountered:
Describe the bug
I am trying to run ww3_tp2.14 on Ubuntu 24. All previous tests in the matrix compile and run. However, with ww3_tp.14, I get the following error during the compilation:
I have MPI installed on my system, which I can verify by running ww3_tp2.21, for example.
To Reproduce
./bin/run_cmake_test -s OASACM -i input_oasacm -w work_OASACM -C OASIS -f -p mpirun -n 1 ../model ww3_tp2.14
Expected behavior
The compilation is successful if MPI is installed on the system.
Additional context
The reason for this is most likely that the module is compiled without the MPI flag. In model/src/CMakeLists.txt we have
Since the MPI flag is not set the MPI libraries are not linked. The reason for the error not occurring for other users is likely that their MPI library is in one of the other directories that are included. A fix might be to include a special rule in the CMakeLists.txt to enforce that w3agcmmd.F90 is always linked to MPI.
Another fix might be to use preprocessor directives in w3agcmmd.F90.
If this is considered useful, I could try a fix using one of the two approaches.
The text was updated successfully, but these errors were encountered: