Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error during compilation #179

Open
sarriegi opened this issue Aug 25, 2023 · 23 comments
Open

Error during compilation #179

sarriegi opened this issue Aug 25, 2023 · 23 comments

Comments

@sarriegi
Copy link

Hello, so far I have been running CoastalApp in the MIT-supercloud cluster. Recently they changed the environment, so I compiled again the esmf library in the new environment. After that, I tried to compile again the CoastalApp, but I got this error, right at the beginning of the compilation process:
image

Do you know what the problem might be?

Angelos
@pvelissariou1 @saeed-moghimi-noaa

@pvelissariou1
Copy link
Collaborator

Angelos,
Are you sure you cloned CoastalApp recursively, maybe your ATMESH,WW3,ADCIRC are empty.
Try to clone the application as usual:
git clone --recurse-submodules https://github.com/noaa-ocs-modeling/CoastalApp.git

I built the application from scratch using:
build.sh --component "atmesh ww3 adcirc" --compiler gnu --tp parmetis
and everything compiled just fine.

@sarriegi
Copy link
Author

Thank you for your response Takis! I am trying to compile a code that has worked in the past, so the folders are all there. Also, the compilation of ADCIRC and WW3 as standalone models inside the CoastalApp works fine. The only thing that changed between the time that I was able to compile and run the CoastalApp, was that they changed the system's compilers. And somehow this change has made the CoastalApp compilation crushing at the very beginning of the process.

Angelos

@sarriegi
Copy link
Author

Note also, that I was trying with a previous version of CoastalApp. When I tried to compile the latest version, the compilation got through this initial stage, ADCIRC and WW3 were compiled successfully, but then just before the end of the compilation process, I got this error:
image
Do you know what could be the reason for this error?
@pvelissariou1

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 26, 2023 via email

@sarriegi
Copy link
Author

Hello Takis, I am using version 8.0.1, the same version I was always using, which was working fine before they changed the compilers.

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 27, 2023 via email

@sarriegi
Copy link
Author

I am using the new compilers that they installed in MIT Supercloud, intel 2023.1. With the previous compiler which was intel 2019.5, it was compiling fine.

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 28, 2023 via email

@sarriegi
Copy link
Author

Hello Takis, I am attaching the coastalapp compilation and the esmf build log files. The error was this (for some reason was not printed on the log file:
image
coastalapp_compile.log
esmf_make.log

Thank you for looking into this!

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 28, 2023 via email

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 29, 2023 via email

@sarriegi
Copy link
Author

Thank you for looking into this Takis, I think that they are set correctly. I am attaching the esmf.mk file

Angelos
esmf.txt

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 29, 2023 via email

@sarriegi
Copy link
Author

I don't understand either. I think I will move on by trying to run CoastalApp in a different cluster. Thank you again!

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 29, 2023 via email

@sarriegi
Copy link
Author

Hi Takis, I was able to compile it after in MIT supercloud (by adding -DESMF_VERSION_MAJOR=8 to CPPFLAGS in NEMS/src/GNUmakefile) after all. However, when I try to run I get these errors:
image
image
Have you ever seen errors like that? Do you have any idea of what the problem might be?

Angelos

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Aug 30, 2023

@sarriegi , @saeed-moghimi-noaa Angelos it seems to me that in your cloud cluster the environment variables are not propagating properly. CoastalApp and its components during the compilation stage source and/or, include the file pointed to by the ESMFMKFILE variable which, contains the definitions of all the ESMF related variables. We never had any of these issues with ESMF. May be your bash login is not configured properly. You should never have to modify the NEMS/src/GNUmakefile for this.

Regarding the errors, I think these are coming from the library libucs which is part of the ucx package in linux. In the cluster run the command: rpm -q ucx ucx-devel (I guess the cluster uses some version of RedHat/CentOS) to see what version of the ucx package is installed in your system. I believe, you should have ucx >= 1.12 installed for things to work. I had this issue before and it was all due to the ucx library. I compiled a newer version of ucx in one of our HPC clusters and all these issues were resolved. See what you can find and let us know.

@sarriegi
Copy link
Author

Thank you for this information Takis, this is the related information about Supercloud:
image
Since it is 1.12 I assume this is not the problem. Also everything was working fine with the old version of the compiler. It's the new compiler that has messed things up. I think I will move on and try to run CoastalApp in the Unity cluster (UMass).

Angelos

@sarriegi
Copy link
Author

sarriegi commented Sep 6, 2023

Hello Takis, I compile CoastalApp in a new cluster. However, when I tried to run it I received these errors in on of the PET* files:
image
Do you have any idea about what I could be doing wrong?

Angelos
@pvelissariou1 @saeed-moghimi-noaa

@pvelissariou1
Copy link
Collaborator

Have you tried this configuration before?

@pvelissariou1
Copy link
Collaborator

@sarriegi are the atm. fields given on triangular mesh? Same mesh as the ocean model? Can you try to use: remapMethod=bilinear:extrapMethod=nearest_stod to see what happens?

@sarriegi
Copy link
Author

sarriegi commented Sep 6, 2023

Thank you for the suggestion, Takis! I have used this configuration successfully before. I am using atmesh.F90 and atmesh_mod.F90 files that are not the original ones in CoastalApp. These files allow for the wind forcing file to be given on a regular (structured) grid. I am attaching these files here:
atmesh.txt
atmesh_mod.txt

Angelos

@pvelissariou1
Copy link
Collaborator

@sarriegi I guess the atmospheric grid overlaps the ocean mesh completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants