Reduce the number of stack files about hpc-stack HOT 5 CLOSED

We can follow Rahul's suggestion to add a stack_add.ymal to add additional versions. e.g esmf bs36 etc.

from hpc-stack.

I can try to compile the NOAA stack on gaea, but I am pretty sure this will be an uphill battle. Regarding macOS: when using LLVM clang that comes via homebrew (just as GNU does), there is OpenMP support. The nice thing about using LLVM clang + GNU gfortran is then that the same config can be used with GNU gcc + GNU gfortran and have OpenMP support. I have instructions on how to do that, compiled hpc-stack on macOS Catalina with LLVM clang 10 and GNU gfortran 10 as well as with GNU gcc+gfortran 10 (I also tried with 9 on macOS Mojave0.

from hpc-stack.

IMHO

noaa, gaea, ncar should be combined into one. These will build static and all libraries (except compiler and mpi).
The libraries are used by a variety of applications; ufs, jedi, etc.

custom and mac are used for CI and should build all libraries. Static/Shared does it matter for CI?

ufs_weather_ci could be eliminated in favor of (noaa, gaea, ncar). Sure, there is overhead (extra space/time) due to additional libraries in the container, but what is the size difference in the container including/excluding these additional libraries? This should be evaluated.

from hpc-stack.

Let's bump this issue to the 1.3.0 release of hpc-stack so we can get the 1.2.0 release out.

from hpc-stack.

Going to close this. I think we're fine with the files we support. Mac, custom, and NOAA are general purpose while we have other more specialized stacks.

from hpc-stack.