<div dir="ltr"><div><div><div>Dusan,<br><br></div>There is one NEMS framework. That is the instruction we have received from management. This system is maintained by the NEMS trunk commit process, which requires that any NEMS change be tested against all apps. <br><br>If you want there to be many copies of the NEMS framework, then you need to direct that complaint to EMC management. Until then, I will continue to do what I was tasked to do.<br><br></div>Sincerely,<br></div>sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 3, 2017 at 2:22 PM, Dusan Jovic - NOAA Affiliate <span dir="ltr"><<a href="mailto:dusan.jovic@noaa.gov" target="_blank">dusan.jovic@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">... <span style="font-size:12.8px">The second will <b>affect all three of those</b>, plus the NMMBTestBed app, <b>to support changes</b> from the WAM-IPE app. ...</span><br style="font-size:12.8px"><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Why on earth do we need to touch NMMB app in order to support WAM-IPE. Sam, I guess you'll need to run all nmmb regression tests to support this WAM change, am I correct?. I have no idea what WAM_IPE is, but whatever it is NMMB must not be affected by the changes WAM developers need to make. This is simply not scalable solution. Everything depends on everything. </span><span style="font-size:12.8px">These kind of dependencies is what makes NEMS very difficult to use, and I'm afraid will eventually destroy the whole project. I wonder if NMMB change will require 4 or 5 repositories to be updated (branches created, merged, updated, external pointers adjusted and finally reintegrated with respective trunks, not to mention opening tickets in all repositories, asking people to review all changes, getting management approval for change etc...) and all regression tests in all repositories to be executed.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Mar 3, 2017 at 9:44 AM, Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div><div><div><div><div><div>NEMS developers,<br><br></div>There are two sets of commits coming in soon to the NEMS and three apps. The first set will change the NEMS trunk, the NEMSfv3gfs trunk, and the NEMSGSM trunk to support changes to the NEMSfv3gfs. The second will affect all three of those, plus the NMMBTestBed app, to support changes from the WAM-IPE app.<br><br></div><div>The first commit will go in between 2:00 and 5:00 Eastern time Wednesday, March 8. <br><br></div><div>The second commit has no target date yet; it will likely be about a week or two from now.<br><br></div><div><br></div>========== COMMIT #1: UPDATES FOR FV3 ==========<br><br></div><div>Commit time: 2:00-5:00 PM Eastern on Wednesday, March 8.<br></div><div><br></div><div>Relevant branches:<br><br></div><div>NEMSfv3gfs: <a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/NEMSfv3gfs/branches/appify" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/NEMSfv3gfs/b<wbr>ranches/appify</a><br></div><div>NEMSGSM: <a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/NEMSGSM/branches/appify-fv3" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/NEMSGSM/bran<wbr>ches/appify-fv3</a><br></div><div>NEMS: <a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/appify-fv3" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/appify-f<wbr>v3</a><br></div><div>produtil: <a href="https://svnemc.ncep.noaa.gov/projects/nceplibs/produtil/branches/regtests-run" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nceplibs/produtil/bran<wbr>ches/regtests-run</a><br></div><div><br></div><div>---------- NEMS TRUNK ----------<br><br></div><div>1. NEMSAppBuilder can build the FV3<br><br></div><div>2. produtil external is updated to produtil v. 4.1<br><br></div><div>3. The NEMS/src/configure script is updated so that the application-level custom compilation scripts can specify all four of the NEMS/src/conf files by specifying a path. That means the bulky "if" statement inside the configure script no longer needs to be updated when the application-level configure files change.<br><br></div><div>4. Add support for building and testing on WCOSS Cray<br><br></div><div>5. Workarounds for Luna module purging issues that users have encountered over the last week or so (see NEMS/src/conf/module-setup.*.i<wbr>nc)<br></div><div></div><div><br></div>---------- NEMSfv3gfs APPLICATION ----------<br><br>1. compsets are added. Input and baseline are the same as the rt.sh, so updating the tests/ updates compsets. To run the compsets: ./NEMS/NEMSCompsetRun -f<br></div><br>2. compile.sh uses modules and conf files and module files from the NEMSfv3gfs level<br><br></div><div>3. rt.sh files <a href="http://input.nml.IN" target="_blank">input.nml.IN</a> and model_configure.IN are in the parm/ directory so that the compset runner can use the same files<br></div><div><br></div>4. Third and fourth arguments to compile.sh are optional. Defaults: no MAKE_OPS, and the executable will be fv3.exe.<br><br></div>5. Workarounds for Luna module purging issues. (tests/* now use the NEMS/src/conf/module-setup.sh) <br></div><div><br></div>6. A fifth regression test is added: fv3_appbuilder, which is identical to the control, but uses the NEMSAppBuilder to build (via tests/appbuild.sh). All other tests use compile.sh to build.<br><br><br></div><div>---------- NEMSGSM ----------<br><br></div><div>1. FIXGLOBAL in oldtests/rt.sh now points to the versioned area.<br><br></div><div>2. Update to the latest NEMS trunk.<br><br><br><br><br>========== COMMIT #2: UPDATES FROM WAM-IPE ==========<br><br></div><div>I'm not announcing branches or exact commit date until the details of the WAM-IPE code changes are finalized.<br></div><div><br></div><div>---------- NEMS Trunk ----------<br><br></div><div>1. Space Weather mediator updated to latest wam-ipe version.<br></div><div><br>2. NEMSAppBuilder allows appBuilder files to specify which one is the default selection in GUI mode.<br><br></div><div>3. Changes to the MAIN_NEMS resource usage monitoring to work around a bug in IPE coupling. Some of the component finalize steps call MPI_Finalize without returning control to the MAIN_NEMS. This is a bug in the component, not NEMS. However, I would rather put in workarounds at the NEMS level since the bug will almost certainly come up again in another component. (If you look at the GSM source code, you will see many MPI_Finalize calls.)<br><br></div><div><br>---------- NEMS uncapped branch ----------<br><br></div><div>1,2,3. Same changes as for the NEMS trunk<br><br></div><div>4. Changes to physics and dynamics to support the WAM-IPE coupling.<br><br></div><div>NOTE: if these changes in #4 break the NMMBTestBed, then they will not be applied to the uncapped branch, and WAM-IPE will have its own fork of NEMS, supported by the NEMS code manager.<br><br><br></div><div>---------- NMMBTestBed ----------<br><br></div><div>1. Update to head of uncapped branch<br><br><br></div><div>---------- NEMSfv3gfs and NEMSGSM ----------<br><br></div><div>1. Update to head of NEMS trunk<br></div></div>
<br></div></div>______________________________<wbr>_________________<br>
Ncep.list.nems.announce mailing list<br>
<a href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov" target="_blank">Ncep.list.nems.announce@lstsrv<wbr>.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.g<wbr>ov/mailman/listinfo/ncep.list.<wbr>nems.announce</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>