[Ncep.list.nems.announce] trying to understand a recent NEMS commit...
weiyu.yang at noaa.gov
Fri Feb 28 17:23:15 UTC 2014
For the commit, I sent e-mail and changed the NEMS ticket. May be
something wrong caused you did not received. Very sorry for it.
For the second point, yes, this 6.3.0r did not change more for the
system. The main change is to make sure the ESMF 6.3.0r can be used on
wcoss machine and add two new regression tests, one for nmm and one for
GFS run, on wcoss machine, as well as installing the ESMF 6.3.0r library
on wcoss and pointed to it when need it. I agree that everything can be
re-code to make it to look to be nice. If you like you may do anything
you want. Thank you very much.
By the way, you have to re-do the merge and tests might be caused by the
Sarah's commission, which just before my commision, because after her
commission, the all GSM baseline data changed.
Have a nice weekend
On 2/27/2014 7:47 PM, Gerhard Theurich wrote:
> I am a bit puzzled how I missed the commit announcement to the NEMS
> trunk that went in 19h ago as revision 37397. There are two issues:
> 1) It's hard to merge to the trunk when there are changes coming like
> that are not being announced. Yesterday I had merged branches/NUOPC
> changes to a trunk sandbox, resolved issues and started testing. I will
> repeat now...
> 2) The changes in question, updating to ESMF v6.3.0r in NEMS, I would
> have advised to approach the issue differently. Starting with v5.2.0r,
> ESMF guarantees a large degree of backward compatibility of the API. The
> idea behind added the "520rAPI" setting in NEMS was to use it on all
> 520rAPI compatible ESMF releases, which should be pretty much any future
> release. The same internal macros would be used in NEMS, and eventually,
> when the use of prior ESMF versions (like v3.1.0rpX) dies out in NEMS,
> all of that ESMF version specific macro jungle could be cut down. I
> think we should revisit the changes.
> Ncep.list.nems.announce mailing list
> Ncep.list.nems.announce at lstsrv.ncep.noaa.gov
More information about the Ncep.list.nems.announce