GeorgeVandenberghe-NOAA
commented
3 years ago ufs-utils is not a part of NCEPLIBS unless someone has again increased our scope. It's maintained by the global branch. It's a big bunch of utilities that do various things. Because of all of the different build scripts for the utilities it's tedious but not real difficult to port to new platforms. In my last port in 2019, I ripped up the build system and replaced system specific modules with a generic set and got rid of system detection logic in most of the build. It's a forklift upgrade to that build system though and I never committed it. In a 2020 WCOSS2 port I dispensed with generic modules and created one universal set for all of the utilities and changed several dozen build scripts to use the universal set thus getting rid of several dozen generic modules selected from a few hundred system specific modules . Again though it's a radical change to the build and I have not committed it.
People still seem to prefer utility and system specific modues so I'm not pushing my changes back but when I need to port to something like an AWS cloud, I go with my way.
On Thu, Nov 19, 2020 at 1:59 PM Edward Hartnett notifications@github.com wrote:
We are doing the hpc-stack-1.1.0 release in the near future. @GeorgeVandenberghe-NOAA https://github.com/GeorgeVandenberghe-NOAA has tagged a release in UFS_UTILS. Shouldn't we be using it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NOAA-EMC/hpc-stack/issues/89, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDS4FXPVR66HLTHYKRDIGTSQVTHDANCNFSM4T3ZOAGA .
--
George W Vandenberghe
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Rm. 2141
College Park, MD 20740
George.Vandenberghe@noaa.gov
301-683-3769(work) 3017751547(cell)
edwardhartnett
kgerheiser
We are doing the hpc-stack-1.1.0 release in the near future. @GeorgeVandenberghe-NOAA has tagged a release in UFS_UTILS. Shouldn't we be using it?