<div dir="ltr"><div><div>Gerhard,<br><br></div>I would like to let you know that the planned commits for gsm and nmmb before the trunk freeze have been finished after Hang Lei made a nems trunk commit last Saturday. Please go ahead with your merge process and let me know when you have a stable merged version for gsm regression test. Thanks.<br><br></div>Jun<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 12:28 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">Thanks, appreciate it!<span class="HOEnZb"><font color="#888888"><br>
-Gerhard</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 04/14/2016 09:26 AM, Ratko Vasic wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Gerhard,<br>
I understand. I'm OK with that.<br>
Data is already copied and ready for use.<br>
<br>
Ratko<br>
<br>
<br>
On 4/14/2016 11:55 AM, Gerhard Theurich wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Ratko, I totally see your point, it is always best to have most<br>
cahnges in before starting. My only concern is time. I want to make<br>
sure we have enough time to work out the issues. There isn't only the<br>
svn based merge (with plenty of manual intervention as I foresee it),<br>
but then there is also the whole unification on the actual code<br>
(removal of #ifdefs). At this stage we will need to get the current<br>
"trunk mode" working under the unified NUOPC-based EARTH component. I<br>
was hoping to get to working on that maybe even by end of this week.<br>
<br>
On the other hand, I am still cleaning up compsets as per a call we<br>
had on Tuesday. It is taking me longer than I thought, so even the<br>
NUOPC/development branch isn't quite ready yet.<br>
<br>
If you don't mind, could you still just make copies of the<br>
REGRESSION_TEST dirs into REGRESSION_TEST_r74057? Just in case we do<br>
decide to start a first attempt of the merge work with that trunk<br>
revision? Thanks, and I appreciate your assistance during the process<br>
very much!<br>
<br>
-Gerhard<br>
<br>
On 04/13/2016 06:50 PM, Ratko Vasic wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Gerhard,<br>
I'd wait until weekend (before freeze).<br>
There is one commit in the line (GSM stuff), and as agreed on today's<br>
meeting with NMMB group, we'll update trunk with changes (at least 90%<br>
of changes) going into next production.<br>
GSM commit is adding one more regression test, and NMMB commit will for<br>
sure change NMMB results.<br>
I would like to tag that version as a reference point.<br>
I'll test everything on both machines (theia and wcoss).<br>
<br>
Ratko<br>
<br>
<br>
<br>
On 4/13/2016 5:39 PM, Gerhard Theurich 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<br>
with trunkRev1 for the next few days without loosing the ability to<br>
validate the trunk regression tests - just in case the trunk keeps<br>
moving and requires changes to the baselines.<br>
<br>
Patrick and/or Dusan, will you be available to run NMMB trunk<br>
regression tests on wcoss and Theia when we get to that point?<br>
<br>
-Gerhard<br>
<br>
On 04/13/2016 02:24 PM, Jun Wang - NOAA Affiliate wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
<<a href="mailto:theurich@sourcespring.net" target="_blank">theurich@sourcespring.net</a> <mailto:<a href="mailto:theurich@sourcespring.net" target="_blank">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<br>
for the<br>
upcoming merge task. This more than a simple merge in that we are<br>
trying<br>
to unify the coupled system with the default "trunk mode" of<br>
NEMS. The<br>
result will be much cleaner superstructure code (removal of<br>
#ifdefs in<br>
the EARTH component). Also the emerging system will exclusively<br>
use the<br>
latest ESMF release (v7.0.0).<br>
<br>
As previously discussed, there is an upcoming FREEZE of the NEMS<br>
trunk<br>
for the entire next week (i.e. week of 04/18/16). We will try to<br>
have an<br>
early test candidate of the new NEMS trunk available some time<br>
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<br>
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<br>
running<br>
the NEMS trunk regression tests. I am thinking it would be good<br>
to have<br>
GSM and NMMB experts available for this. They would run the<br>
regression<br>
tests on trunkRev1 and make a backup copy of the results, so that<br>
we can<br>
retest against the same baseline, even if the default baseline on<br>
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<br>
versions of<br>
NEMS available at different times. It would be great of the same<br>
people<br>
from #2 were available to check out these revisions and test them<br>
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<br>
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" target="_blank">Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov</a><br>
<mailto:<a href="mailto:Ncep.list.emc.nems.tickets@lstsrv.ncep.noaa.gov" target="_blank">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>
<br>
<br>
<br>
<br>
</blockquote></blockquote>
<br>
</blockquote></blockquote>
<br>
</blockquote>
</div></div></blockquote></div><br></div>