[Ncep.list.nems.announce] Incoming NEMS Commit

[Samuel Trahan - NOAA Affiliate]

Hi all,

The application developer told me to go ahead with this commit, so I'll
commit it between 5-6 PM Eastern time today.  I'm going to keep debugging,
but I must reproduce the problem before I can determine its cause.  Three
different accounts were able to rerun the test with no problem, so the
problem may be fugacious, or worse, sporadic.

Lastly, I have two updates to my original email about the commit:

1. I mentioned "odin support" was added in the commit.  It is not.  Theia
support for non-Intel compilers is added in the commit.

2. The NCEPLIBS_pyprodutil submodule is updated.  This adds a ".gitignore"
that will ignore the Python *.pyc files.  The NEMS level already had this,
but that ".gitignore" lost its potency when the produtil was moved to a
submodule.  (A ".gitignore" is not applied recursively because each
submodule is its own git repository.)  Thanks to Dusan Jovic for noticing
this problem.

Sincerely,
Sam Trahan

On Mon, 29 Oct 2018 at 11:36, Samuel Trahan - NOAA Affiliate <
samuel.trahan at noaa.gov> wrote:

> Hi all,
>
> In order to debug this problem, I need to run a number of tests on Theia.
> All projects accessible to emc.nemspara or myself have hit their monthly
> CPU allocation.  That means I cannot even start debugging this until
> Thursday, when the allocations reset.  Most likely, this will delay the
> commit until next week.  I will let you know if I find another solution.
>
> Sincerely,
> Sam Trahan
>
> On Mon, 29 Oct 2018 at 10:57, Samuel Trahan - NOAA Affiliate <
> samuel.trahan at noaa.gov> wrote:
>
>> Hi all,
>>
>> I have finished running the regression test system for this commit.  One
>> of the compsets for FV3-MOM6-CICE5 failed on Theia, and all other compsets
>> for all apps succeeded everywhere else.  I'm having the app code manager
>> look into the failed case.  I don't think it is related to these changes,
>> but I want the app's code manager to decide that.
>>
>> Test results are here:
>>
>> http://www.emc.ncep.noaa.gov/projects/nems-commit/build-update-wave2/
>>
>> The tests report no failure because I reran the failed compset, and it
>> succeeded.
>>
>> Sincerely,
>> Sam Trahan
>>
>> On Fri, 26 Oct 2018 at 12:20, Samuel Trahan - NOAA Affiliate <
>> samuel.trahan at noaa.gov> wrote:
>>
>>> Hi all,
>>>
>>> Sometime Monday evening, I will commit the second wave of build system
>>> changes: bug fixes and feature additions to the new NEMS build system.
>>> Final tests are beginning now.  With these changes, DATM and GSDCHEM are
>>> confirmed to work, and several reported bugs are fixed.  We're half-way to
>>> getting CCPP fully working; some changes are still needed in FV3, and those
>>> are waiting for other commits.
>>>
>>> Most of the changes in this batch of commits are from Dom Heinzeller,
>>> who is adding support for compiling on non-NOAA machines, and for running
>>> with CCPP.  I'm only committing the NEMS and NEMSfv3gfs parts of his
>>> changes; he has some changes in FMS and FV3 which will be committed later,
>>> hopefully late next week.
>>>
>>>
>>> The branches in NEMS and NEMSfv3gfs are build-update-wave2.  For other
>>> apps, the master is used.
>>>
>>>
>>> Changes that are NOT from Dom Heinzeller:
>>>
>>> 1. Remove an extra "clean" step in NEMS/src/incmake/component_FV3.mk.
>>> This fixes a bug reported by Ratko and Dusan wherein FV3 would always be
>>> cleaned, even if you asked for it not to be.
>>>
>>> 2. Do not delete the *.tmp.f90 files when building NEMS.  This is why
>>> NEMS always rebuilt its source code.  Dusan provided this fix.
>>>
>>> 3. GSDCHEM clean rule: do not fail to clean if the Makefile is absent.
>>> This fix is from Raffaele Montuoro.
>>>
>>> 4. Use -j1 when building Wavewatch 3.  This is a temporary workaround
>>> for a Wavewatch3 build system issue.  A better solution is in progress.
>>>
>>> 5. In the build system documentation, add a big box reminding you to "cd
>>> NEMS" before building.
>>>
>>>
>>> Dom Heinzeller's changes:
>>>
>>> 1. Rename "macos" build targets to "macosx" for consistency with
>>> components.
>>>
>>> 2. Set appropriate default NEMS_COMPILER values for various platforms.
>>>
>>> 3. Skip the module-setup.sh.inc if the platform does not support the
>>> "module" command.
>>>
>>> 4. Add ccpp/include to the include flags in the CCPP's ESMF makefile
>>> fragment.  (The NEMS build system treats CCPP as a component.)
>>>
>>> 5. Update linux, macosx, odin, and cheyenne build environment logic so
>>> it actually works.  (FV3 and FMS commits are still needed for full support.)
>>>
>>> 6. Update PGI & GNU compiler suite logic so it actually works.  (FV3 and
>>> FMS commits are still needed for full support.)
>>>
>>> 7. ccpp/physics/physics/sfcsub.F update of code to compile with gfortran
>>> v8+
>>>
>>> 8. Documentation updates for porting and CCPP.
>>>
>>>
>>> Sincerely,
>>> Sam Trahan
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.nems.announce/attachments/20181029/861d9b03/attachment-0001.html