<div dir="ltr"><div><div><div>Hi,<br><br></div>Sorry, one typo. The FV3 app is NEMSfv3gfs. Hence, FV3 development moves here:<br><br> FV3 -> nems/apps/FV3GFS/trunk<br><br></div>Sincerely,<br></div>Sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 19, 2016 at 4:01 PM, Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a href="mailto:samuel.trahan@noaa.gov" target="_blank">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">Fellow NEMS developers,<br><br>Soon I
will commit Jun's change to remove the atmos layer to the trunk of NEMS and
permanently freeze NEMSLegacy. Standalone development of the three
atmospheric dynamical cores will move to three new apps. The NEMS and
NEMSLegacy branches related to GSM and FV3 capping work will move to new
locations. This involves a sequence of commits that will finish either
late this week or early next week. I will announce each one before
committing it, and I will run both the old and new regression test
suites. Details are below.<br><br>As you may know, the removal of the
atmos layer will temporarily break NMMB support and make it harder for
older GSM development to be merged to the trunk. For this reason, we
will create an "uncapped" branch of NEMS for support of developers that
are not up to date with the latest trunk changes. We will continue to
backport bug fixes to the "uncapped" branch as needed. However, we
would like to end this practice as soon as possible.<br><div><br></div><div>Development of standalone models will move from nems/apps/NEMSLegacy to the following three locations:<br></div><div><br></div> NMMB -> nems/apps/NMMBTestBed/trunk<br> GFS -> nems/apps/NEMSGSM/trunk<br> FV3 -> nems/apps/FV3GFS/trunk<br><br><div>There will be no more commits to nems/apps/NEMSLegacy/trunk<br></div><div><br></div><div>Other branches will move:<br><br></div><div> nems/branches/ATM-refactor/ -> nems/trunk<br></div><div> nems/apps/NEMSLegacy/branches/<wbr>GSM-capping -> nems/apps/NEMSGSM/trunk<br> nems/apps/NEMSLegacy/branches/<wbr>jun/nems4fv3 -> nems/apps/NEMSfv3gfs/trunk<br></div><div><br></div><div>The "uncapped" branch of NEMS will be here:<br><br></div><div> nems/trunk -> nems/branches/uncapped<br></div><div><br></div><div>The
nems/apps/NMMBTestBed/trunk will a copy of the NEMSLegacy/trunk just
before the capping was merged. However, it will point to the
nems/branches/uncapped branch instead of the trunk. That will allow
back-porting of bug fixes for NMMB support until the cap is completed.<br></div><div><br></div>Sincerely,<br>Sam Trahan</div>
</blockquote></div><br></div>