<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Sam,</p>
<p>I am forwarding this e-mail thread to Rusty Benson with a request
to provide his comments and suggested solutions. <br>
</p>
<p>Rusty - please see below and provide your response at your
earliest convenience.<br>
</p>
<p>Thanks,</p>
<p>Vijay<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 9/5/2018 1:38 PM, Samuel Trahan -
NOAA Affiliate wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ3i2WcqqtGAqEOQVYyeUXNiA7d71wfHFO9BjpL_9ZeEjsEe0Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>Apologies; there was an ambiguity in my last email. The
exact contents of the FMS are not decided yet. All that is
certain is that the FMS will reside in its own repository, and
be at the NEMS application level. I'm hoping to have a
solution within the next few days, but it is largely outside
my control.<br>
</div>
<div><br>
</div>
<div>Sincerely,</div>
<div>Sam Trahan<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 5, 2018 at 1:36 PM, Samuel
Trahan - NOAA Affiliate <span dir="ltr"><<a
href="mailto:samuel.trahan@noaa.gov" target="_blank"
moz-do-not-send="true">samuel.trahan@noaa.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>We are still awaiting a management decision on how
the FMS will be handled in NEMS applications. The "FMS
component" commit will go in, in its current form, but I
don't know yet where the FMS will reside.<br>
</div>
<div><br>
</div>
<div>Sincerely,</div>
<div>Sam Trahan<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Aug 29, 2018 at 1:00 PM,
Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a
href="mailto:samuel.trahan@noaa.gov" target="_blank"
moz-do-not-send="true">samuel.trahan@noaa.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>We're close to having a solution to the
aforementioned problem. The details are uncertain
at this time, but we'll have some kind of joint
EMC-DTC fork of FMS in github. It will track the
GFDL FMS as closely as possible, while making it
portable enough to use on all RDHPCS machines and
common clusters elsewhere. The NEMS applications
will point to the EMC-DTC fork. Management is
ruminating on details like exactly where it will
be, the choice of code manager, the commit
process, and how the changes are sent back to
GFDL; we expect to have a solution soon. These
may sound like mundane details, but having a poor
code management process causes major problems if
it goes on for too long.</div>
<div><br>
</div>
<div>The commit will go in soon, but it may be
slightly later than intended. We'll still try to
get it in by Wednesday afternoon, but it may be
later in the week if decisions on code management
practices take a lot more discussion time. We do
expect the commit to be in by the end of next week
though. </div>
<div><br>
</div>
<div>I'll send out another update when I have more
information.</div>
<div><br>
</div>
<div>Sincerely,</div>
<div>Sam Trahan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Aug 27, 2018 at
9:47 PM, Samuel Trahan - NOAA Affiliate <span
dir="ltr"><<a
href="mailto:samuel.trahan@noaa.gov"
target="_blank" moz-do-not-send="true">samuel.trahan@noaa.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>We have a proposed commit that is
urgently needed, but may have major negative
impacts to a lot of users. Please read this
email and comment. Our comment period ends
at noon Tuesday, September 4. The commit,
if accepted, will happen Wednesday,
September 5.</div>
<div><br>
</div>
<div><b><font size="4">The Commit: Overview</font></b></div>
<div><br>
</div>
<div>In NEMS apps, the FMS exists within both
the FV3 and MOM6 repositories; hence some
apps have two copies of FMS. We have a
proposed commit that will move the FMS up
one level so there is only one FMS per app.
The FMS we've chosen is the one from the
GFDL repository. The technical details of
the changes, are largely inconsequential;
the main issue is the choice of
repositories.<br>
</div>
<div><br>
</div>
<div><b><font size="4">Consequences</font></b></div>
<div><br>
</div>
<div>
<div
style="font-size:small;text-decoration-style:initial;text-decoration-color:initial">These
are the consequences of choosing GFDL's
FMS repository.</div>
<div
style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><br>
</div>
<div
style="font-size:small;text-decoration-style:initial;text-decoration-color:initial">1.
Portability changes to the FMS will be
lost permanently because GFDL rejected
them. This means the FV3 GFS will not be
usable except with certain versions of the
Intel compiler. This has been confirmed.</div>
<br
class="m_7647425042563904516m_6225856664590668753m_-1348154097504351754gmail-Apple-interchange-newline">
2. Recent and upcoming FMS bug fixes will be
lost because they are not in the GFDL
repository. </div>
<div><br>
</div>
<div>3. In general, any FV3 changes will have
to wait several weeks if they need changes
to FMS.</div>
<div><br>
</div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Items
#2 and #3 are unavoidable. GFDL FMS has a
large userbase and lengthy test process.
They will, out of necessity, have a long
delay before commits.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><b><font
size="4">Alternatives</font></b></span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I
know of three alternatives to our FMS
repository problem. Any of these may
require funding or tasking changes, in or
from NOAA:</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">1.
GFDL handles the FV3 GFS as a special
case, maintaining a branch of FMS for the
FV3 GFS, and applying changes within 2-3
days. GFDL ports FMS to other compilers.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">2.
DTC maintains a fork of FMS which all NEMS
apps use. DTC maintains any portability
changes and regularly pulls changes from
GFDL FMS. They receive any changes needed
for NEMS coupling and resolve conflicts as
needed.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">3.
EMC maintains the aforementioned fork.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Note
that DTC is presently tasked with porting
the FMS, and has successfully ported it to
other platforms and maintained an FMS
repository.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><b><font
size="4">The Branches</font></b></span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">The
changes can be found in the
"fms-component" branches of the NEMSfv3gfs
and EMC_FV3-MOM6-CICE5 repositories.
These will be updated later this week when
incoming FV3 changes are available. We
will be sure to test before committing to
the relevant branches.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">When
testing this yourself, note that
the EMC_FV3-MOM6-CICE5 warm start test
will not reliably reproduce itself; this
is a known issue that is unrelated to this
commit. Jet baselines are out-of-date, so
you cannot test there. All other tests
should pass for both apps on all supported
platforms.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><font size="4"><b>The Commit: Details</b></font></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Overview
of the changes:</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">1.
FMS is removed from the build system in
MOM6 and FV3</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">2.
FMS is added at the app level from git://<a
href="http://github.com/NOAA-GFDL/FMS"
target="_blank" moz-do-not-send="true">github.com/NOAA-GFDL/FMS</a><wbr>.
The "git" url makes this submodule
read-only. That is a workaround for
problems in the installation of "git" on
WCOSS Cray and Dell which make github
unreachable via https. This "git"
installation problem has been a known
issue for several months and remains
unresolved, so such a workaround is
necessary.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">3.
The FMS/fv3gfs directory is updated to be
able to build FMS outside of FV3. This
change was accepted by GFDL in their
repository.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">4.
The NEMSAppBuilder is updated to build
FMS. It is treated the same way as a
coupled component in the build system.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">5.
Any appBuilder files must include FMS
before FV3 or MOM6 in their component
list.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">6.
The NEMSfv3gfs tests/compile.sh is updated
to build FMS before FV3.</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Sincerely,</span></div>
<div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Sam
Trahan</span></div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ncep.list.nems.announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov">Ncep.list.nems.announce@lstsrv.ncep.noaa.gov</a>
<a class="moz-txt-link-freetext" href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce">https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Vijay Tallapragada, Ph.D.
Chief, Modeling and Data Assimilation Branch
Environmental Modeling Center, NOAA/NWS/NCEP
+1-301-683-3672 (O); +1-202-679-5629 (C)
<a class="moz-txt-link-abbreviated" href="mailto:Vijay.Tallapragada@noaa.gov">Vijay.Tallapragada@noaa.gov</a></pre>
</body>
</html>