search

JCSDA / spack-stack

Creative Commons Zero v1.0 Universal
21 stars 41 forks source link

[INSTALL]: spack-stack with Intel compiler 2023.2.0/impi 2023.2.0 #1147

Open junwang-noaa opened 1 week ago

junwang-noaa commented 1 week ago

Package name

spack-stack

Package version/tag

1.6.0

Build options

Intel compiler 2023.2.0 and impi 2023.2.0 on Hera.

Installation timeframe

We got some issues with SFS long time forecast, please see the issue https://github.com/ufs-community/ufs-weather-model/issues/2320 Would you please install a test version so that we can see if the issues is gone with the new Intel compiler?

Other information

No response

climbfuji commented 1 week ago

@junwang-noaa Please specify which HPC. Also, the most recent Intel compiler is 2024.1.2 (which has icx (no icc), icpx (no icpc), ifx and ifort).

junwang-noaa commented 1 week ago

Hera. I updated the issue. Thanks.

climbfuji commented 1 week ago

@RatkoVasic-NOAA Would you be able to do this?

RatkoVasic-NOAA commented 1 week ago

Sure, I'm currently busy with Orion installations, but I think I can squeeze this one in my schedule.

RatkoVasic-NOAA commented 1 week ago

@junwang-noaa I just checked, he was using old version of spack-stack:

To Reproduce:
The experiment used the following hash of https://github.com/ufs-community/ufs-weather-model
commit 5bec704
Author: Brian Curtis 64433609+BrianCurtis-NOAA@users.noreply.github.com
Date: Fri May 31 14:52:06 2024 -0400

I suggest he update to 1.6.0 first (newer version of ufs-weather-model is using new spack-stack), and then try other options.

junwang-noaa commented 1 week ago

@RatkoVasic-NOAA Please see Denise's testing with c48 with the latest model code with spack-stack 1.6.0. The issue is related to Intel compiler. Thanks

RatkoVasic-NOAA commented 1 week ago

@junwang-noaa , which one do you want to try with new compiler, 1.5.1, or 1.6.0?

junwang-noaa commented 1 week ago

1.6.0, I listed it in the issue description.

AlexanderRichert-NOAA commented 2 days ago

@junwang-noaa please try /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.6.0/envs/ue-intel-2023.2.0/install/modulefiles/Core

junwang-noaa commented 1 day ago

@AlexanderRichert-NOAA Thanks for installing the library, this intel/impi version does resolve the problem!

May I ask if we can have this spack-stack library installed on all other R&D platforms?

AlexanderRichert-NOAA commented 1 day ago

It's tricky because 2023.2 (2023.2.1, specifically) is the last ever release of the classic compilers. As far as platforms, Gaea, Hercules, and Orion don't have 2023.2 (they all have 2023.1). I don't know about S4 since I don't have access.

Looping in @climbfuji. If it wouldn't adversely affect other applications, we could see about requesting admins to install 2023.2.

climbfuji commented 20 hours ago

S4 has 2023.0.0.

There wouldn't be any problem moving up to 2023.2.1 from an app point of view - actually a good idea to use the very latest release that ships with the classic compilers.

The problem is that such install requests can take a looooooong time. Another option is to install the compiler ourselves under the spack-stack directory structure. That is easy, but it does take a bit of our time. If we do that, we probably want to also pick ONE RDHPCS platform were we also install 2024.2.0 to test the new LLVM compilers for C and C++ (still has the classic ifort compiler).

AlexanderRichert-NOAA commented 17 hours ago

Yeah I think it's probably best to do our own installations. I'll create an issue.

climbfuji commented 16 hours ago

I agree, but to limit our workload we need to be selective creating new installations for older spack-stack releases. For 1.8.0, it's totally fine to update to 2023.2.1 as the default intel compiler for all applications. For previous releases, you need to decide for which systems you want to add 1.6.0 (and/or 1.7.0) environments for these compilers.