Update the nceppost with request by using the 10.0.0 version

[Hang-Lei-NOAA]

Wen has added the nceppost with UPP version of 10.0.0. She request the installation test through hpc-stack.
We will first try it from the EMC_POST/develop branch, on each machine.
If it is okay, she needs to create a release to formally included in the hpc-stack.

A branch has been created to this issue
feature/postupdate

[kgerheiser]

What exactly is the problem?

[aerorahul]

EMC_Post is built as nceppost in hpc-stack. The library it builds is called libnceppost.a and the module files export the variable nceppost_ROOT so that the UFS can find it via find_package(nceppost).

EMC_Post is now producing the library as libupp.a. nceppost was always going to be temporary stop gap measure until EMC_Post finalized what they want the library (and executable) to be called. We also did not know what versioning they would adopt (if any).

It appears that they have now adopted the name upp in their library libupp.a and upp.x for the executable.
Also, they seem to have settled on a version number 10.0.0 for EMC_post (or UPP).

How does this affect hpc-stack?
One needs to:

1. add upp along side ncepppst in build_nceplib.sh
2. add a modulefile for upp similar to nceppost, but the variable we need in there is only upp_ROOT. All other POST_LIB etc can be purged, because there is no need for them or an update is needed in the Makefiles to use libupp.a. They can key on upp_ROOT. This makes management of the modulefile simpler and cleaner.
3. update the yaml files to add a section on upp.

For an example see https://github.com/aerorahul/hpc-stack/tree/feature/upp

[Hang-Lei-NOAA]

Yes, Rahul is correct. The similar changes has been used in the test version, feature/hpc-stack-nco We wait for further testing results, and then merge back to develop

…

On Mon, Nov 16, 2020 at 1:17 PM Rahul Mahajan ***@***.***> wrote: EMC_Post is built as nceppost in hpc-stack. The library it builds is called libnceppost.a and the module files export the variable nceppost_ROOT so that the UFS can find it via find_package(nceppost). EMC_Post is now producing the library as libupp.a. nceppost was always going to be temporary stop gap measure until EMC_Post finalized what they want the library (and executable) to be called. We also did not know what versioning they would adopt (if any). It appears that they have now adopted the name upp in their library libupp.a and upp.x for the executable. Also, they seem to have settled on a version number 10.0.0 for EMC_post (or UPP). How does this affect hpc-stack? One needs to: 1. add upp along side ncepppst in build_nceplib.sh 2. add a modulefile for upp similar to nceppost, but the variable we need in there is only upp_ROOT. All other POST_LIB etc can be purged, because there is no need for them or an update is needed in the Makefiles to use libupp.a. They can key on upp_ROOT. This makes management of the modulefile simpler and cleaner. 3. update the yaml files to add a section on upp. For an example see https://github.com/aerorahul/hpc-stack/tree/feature/upp — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKWSMFERXTKAH7BNQVDRJN3SQFUCPANCNFSM4SY2YLEA> .

[edwardhartnett]

Have these changes been merged to develop?

[Hang-Lei-NOAA]

Yes, in both develop and feature/hpc-stack-nco branch. The test installation based on feature/hpc-stack-nco has been tested fine.

…

On Thu, Nov 19, 2020 at 11:01 AM Edward Hartnett ***@***.***> wrote: Have these changes been merged to develop? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKWSMFF6GITSY7VSWSROII3SQU6LXANCNFSM4SY2YLEA> .

[edwardhartnett]

OK, I will close this issue.

[edwardhartnett]

I thought this had been completed, but apparently not?

[Hang-Lei-NOAA]

I will re-examine the develop branch, since the changes in the test versions has no problem in UFS runs.

…

On Thu, Nov 19, 2020 at 5:04 PM Edward Hartnett ***@***.***> wrote: I thought this had been completed, but apparently not? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKWSMFDE2ATIKBTNL56TTYLSQWJAFANCNFSM4SY2YLEA> .

[edwardhartnett]

@Hang-Lei-NOAA see comments in #63

[Hang-Lei-NOAA]

So, it is the issue for Mac OS. We need someone who use MacOS to help

…

On Thu, Nov 19, 2020 at 5:10 PM Edward Hartnett ***@***.***> wrote: @Hang-Lei-NOAA <https://github.com/Hang-Lei-NOAA> see comments in #63 <#63> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKWSMFGJHWGY5CAWELGCAKTSQWJTPANCNFSM4SY2YLEA> .

[aerorahul]

not just macOS. Also on ubuntu and mpich. See the other log