<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>Rocky, I know it is installed by the system folks on Theia. I don't have access to wcoss, surge and luna, and do not know. Can you find out who would be the right contact for those systems? I assume they have previous versions of esmf available. They really run nems on those?</div><div>-Gerhard </div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Sent via the Samsung Galaxy S® 5 ACTIVE™, an AT&T 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: Rocky Dunlap - NOAA Affiliate <rocky.dunlap@noaa.gov> <br>Date: 4/13/2016 17:19 (GMT-08:00) <br>To: Gerhard Theurich <theurich@sourcespring.net> <br>Cc: Jun Wang - NOAA Affiliate <jun.wang@noaa.gov>, ncep.list.emc.nems.tickets@noaa.gov, Cecelia DeLuca - NOAA Affiliate <Cecelia.Deluca@noaa.gov>, NEMS developers <ncep.list.nems.announce@lstsrv.ncep.noaa.gov> <br>Subject: Re: [Ncep.list.nems.announce] [Nems.tickets] NEMS trunk FREEZE and Re: NEMS Ticket #161: Unifying merge of branches/NUOPC/development and NEMS trunk <br><br><div dir="ltr">Gerhard,<div><br></div><div>At the NEMS tutorial today, it was asked if ESMF v7 has been installed and tested on all systems on which NEMS should be running, especially since v7 will be required after the merge. The Cray systems Surge and Luna were specifically mentioned.</div><div><br></div><div>Rocky</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 13, 2016 at 3:39 PM, Gerhard Theurich <span dir="ltr"><<a href="mailto:theurich@sourcespring.net" target="_blank">theurich@sourcespring.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jun,<br>
<br>
Thank you very much! That is very helpful!<br>
<br>
Unless I hear otherwise let's declare NEMS -r74057 / GSM -r73903 to be<br>
the trunkRev1.<br>
<br>
Ratko, could you please make copies of your current<br>
.../Ratko.Vasic/REGRESSION_TEST dirs on wcoss and Theia to<br>
.../Ratko.Vasic/REGRESSION_TEST_r74057. This will allow us to work with<br>
trunkRev1 for the next few days without loosing the ability to validate<br>
the trunk regression tests - just in case the trunk keeps moving and<br>
requires changes to the baselines.<br>
<br>
Patrick and/or Dusan, will you be available to run NMMB trunk regression<br>
tests on wcoss and Theia when we get to that point?<br>
<br>
-Gerhard<br>
<span class=""><br>
On 04/13/2016 02:24 PM, Jun Wang - NOAA Affiliate wrote:<br>
> Gerhard,<br>
><br>
> For gsm side, I think the current trunk version (nems -r74057, gsm<br>
> -r73903) is a stable version. Maybe someone from NMMB can confirm that<br>
> for nmmb. If both gsm and nbb confirm the version, I think you can<br>
> create nems branch trunkRev1. Dusan just committed the code, so<br>
> currently all the regression tests for both GSM and NMMB for this<br>
> version passed on both wcoss and theia. Please see the log files at<br>
> trunk/tests/RegressionTests_wcoss.log and<br>
> trunk/tests/RegressionTests_theia.log. The baseline from the trunk<br>
> version above are saved in Ratko's directory on both theia and wcoss:<br>
><br>
> wcoss:<br>
> /meso/noscrub/Ratko.Vasic/REGRESSION_TEST<br>
> Theia:<br>
> /scratch4/NCEPDEV/meso/noscrub/Ratko.Vasic/REGRESSION_TEST<br>
><br>
> I can help test gsm regression test once you have a stable merged<br>
> version. Thanks.<br>
><br>
> Jun<br>
><br>
><br>
><br>
> On Wed, Apr 13, 2016 at 4:52 PM, Gerhard Theurich<br>
</span><div><div class="h5">> <<a href="mailto:theurich@sourcespring.net">theurich@sourcespring.net</a> <mailto:<a href="mailto:theurich@sourcespring.net">theurich@sourcespring.net</a>>> wrote:<br>
><br>
> Hi NEMS developers,<br>
><br>
> I just opened a new NEMS ticket (#161) to serve as a reference for the<br>
> upcoming merge task. This more than a simple merge in that we are trying<br>
> to unify the coupled system with the default "trunk mode" of NEMS. The<br>
> result will be much cleaner superstructure code (removal of #ifdefs in<br>
> the EARTH component). Also the emerging system will exclusively use the<br>
> latest ESMF release (v7.0.0).<br>
><br>
> As previously discussed, there is an upcoming FREEZE of the NEMS trunk<br>
> for the entire next week (i.e. week of 04/18/16). We will try to have an<br>
> early test candidate of the new NEMS trunk available some time middle of<br>
> next week.<br>
><br>
> There are some critical pieces that I need help with from EMC:<br>
><br>
> 1) Prior to the trunk freeze next week, I would need someone to identify<br>
> a recent and stable NEMS trunk revision. Let's call this revision<br>
> trunkRev1<br>
><br>
> 2) I will need someone (or a few folks) that are well versed at running<br>
> the NEMS trunk regression tests. I am thinking it would be good to have<br>
> GSM and NMMB experts available for this. They would run the regression<br>
> tests on trunkRev1 and make a backup copy of the results, so that we can<br>
> retest against the same baseline, even if the default baseline on Theia<br>
> and WCOSS may still change (because trunk is not yet frozen).<br>
><br>
> 3) During the unification process I am expecting to have versions of<br>
> NEMS available at different times. It would be great of the same people<br>
> from #2 were available to check out these revisions and test them again<br>
> against the saved baseline from #2.<br>
><br>
> Thanks,<br>
> -Gerhard<br>
><br>
><br>
><br>
> On 04/13/2016 01:26 PM, NEMS Trac Ticket wrote:<br>
> > #161: Unifying merge of branches/NUOPC/development and NEMS trunk<br>
> > -------------------------+-----------------<br>
> > Reporter: theurich@… | Owner:<br>
> > Type: task | Status: new<br>
> > Priority: major | Milestone:<br>
> > Component: NEMS | Version: 3.1<br>
> > Resolution: | Keywords:<br>
> > -------------------------+-----------------<br>
> > Changes (by theurich@…):<br>
> ><br>
> > * type: defect => task<br>
> ><br>
> ><br>
> > --<br>
> > Ticket URL:<br>
> <<a href="https://svnemc.ncep.noaa.gov/trac/nems/ticket/161#comment:1" rel="noreferrer" target="_blank">https://svnemc.ncep.noaa.gov/trac/nems/ticket/161#comment:1</a>><br>
> > NEMS <<a href="https://svnemc.ncep.noaa.gov/trac/nems" rel="noreferrer" target="_blank">https://svnemc.ncep.noaa.gov/trac/nems</a>><br>
> > My example project<br>
> ><br>
> _______________________________________________<br>
> Ncep.list.emc.nems.tickets mailing list<br>
> <a href="mailto:Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov">Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov</a><br>
</div></div>> <mailto:<a href="mailto:Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov">Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov</a>><br>
> <a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.emc.nems.tickets" rel="noreferrer" target="_blank">https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.emc.nems.tickets</a><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
_______________________________________________<br>
Ncep.list.nems.announce mailing list<br>
<a href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov">Ncep.list.nems.announce@lstsrv.ncep.noaa.gov</a><br>
<a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce" rel="noreferrer" target="_blank">https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce</a><br>
</div></div></blockquote></div><br></div>
</body></html>