-
Notifications
You must be signed in to change notification settings - Fork 118
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
Compiler warnings #307
Comments
where are the cloning and build guidelines for the https://github.com/NOAA-GFDL/GFDL_atmos_cubed_sphere repository ? |
@amd-krishnoz - if you are using FV3 within the UFS, you will need to download the ufs-weather-model repository which includes this repo as a submodule. |
@bensonr I was trying to compile the https://github.com/NOAA-GFDL/GFDL_atmos_cubed_sphere/ in a standalone manner and since |
@amd-krishnoz Thank you for your interest in FV3. The FV3 code in this repository cannot be compiled by itself, and needs to be compiled within a driver as part of a full model (SHiELD, UFS, GEOS, etc.). If you could describe what sort of benchmark you are interested in we can help you choose which path forward would be best for you. We can take this offline if you need. My Email address is available at my website (GitHub obscures Email addresses for privacy reasons). |
@bensonr May I ask if you have any suggestions on resolving the warning messages? Thanks |
@junwang-noaa - I assumed Dusan was taking care of it since he created the issue. If you'd like us to take care of it, we can. |
After discussions with @junwang-noaa, I have self-assigned and will be getting a PR out soon. |
Is your question related to a problem? Please describe.
Currently compiler warnings are suppressed when this repo (dev/emc branch) is compiled as a sub-module in the ufs-weather-model/fv3atm, which is not allowed by NCO (see ufs-community/ufs-weather-model#1984). The following warnings must be fixed before this code is implemented in production:
Describe what you have tried
A clear and concise description of what steps you have taken. Include command
lines, and any messages from the command.
The text was updated successfully, but these errors were encountered: