<div dir="ltr"><div><div><div><div>Moorthi,<br><br></div>That is the most common complaint.  I tried to cover that in items #1 and #2 of my &quot;feedback thus far&quot; list in the previous email.  There are really two aspects to the problem:<br><br>1. It is difficult to navigate the 1900 line NEMSAppBuilder to figure out how to change the build commands.  <br><br>2. Some users want to be able to manually build the NEMS without running an overarching script.<br><br></div>Ultimately, if there was a simpler &quot;NEMSAppBuilder&quot; (problem #1) it would be easy to pick out the few commands you need to run manually (problem #2).<br><br></div>Sincerely,<br></div>Sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 7, 2017 at 9:04 AM, Shrinivas Moorthi <span dir="ltr">&lt;<a href="mailto:shrinivas.moorthi@noaa.gov" target="_blank">shrinivas.moorthi@noaa.gov</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_5791859763537675412moz-cite-prefix">I can&#39;t compile standalone GSM on
      wcoss.  How do I do it without blackbox (appbuilder)?<br>
      Thanks<br>
      Moorthi<div><div class="h5"><br>
      <br>
      On 02/07/2017 08:46 AM, Samuel Trahan - NOAA Affiliate wrote:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>Hi all,<br>
                          <br>
                        </div>
                        The NEMS build system, NEMSAppBuilder, is
                        causing a lot of problems, especially for the
                        atmospheric model developers.  We plan on
                        replacing the build system.  What do you want
                        out of the new build system?  What do you
                        dislike about the old one?<br>
                        <br>
                        Some questions to ponder:<br>
                        <br>
                      </div>
                      <div>- How should the build system work
                        internally?  Shell script?  Make?  Cmake?<br>
                      </div>
                      <div><br>
                        - How should you run the build system?  Shell
                        script?  Run &quot;make?&quot;  Run a GUI?<br>
                      </div>
                      <div><br>
                      </div>
                      <div>- When do we replace the build system?  Do we
                        do it now, and risk breaking coupled systems? 
                        Do we wait until we can test it with the coupled
                        applications?<br>
                      </div>
                      <div><br>
                      </div>
                      Feedback thus far:<br>
                      <br>
                    </div>
                    1. It is difficult to navigate the 1900 line
                    NEMSAppBuilder to figure out how to change the build
                    commands.  <br>
                    <br>
                  </div>
                  2. Some users want to be able to manually build the
                  NEMS without running an overarching script.<br>
                  <br>
                </div>
                <div>3. Some users want a simple graphical interface to
                  select components and build the NEMS.  (Yes, there are
                  users that want this.)<br>
                </div>
                <div><br>
                </div>
                4. Sometimes, components compile with options that are
                incompatible with the linking options.  This is because
                each component has its own configuration system.  This
                causes problems, as we saw with FV3.<br>
                <br>
              </div>
              5. The logic for building a component is in the NEMS
              framework level.  Any time a component&#39;s build system
              changes, the NEMS framework has to be updated, breaking
              applications that use older versions of the component. 
              This forces applications to use non-trunk versions of the
              NEMS.<br>
              <br>
            </div>
            6.  The NEMS/src/configure script contains
            application-specific logic.  This also forces applications
            to use non-trunk versions of the NEMS.<br>
            <br>
          </div>
          Sincerely,<br>
        </div>
        Sam Trahan<br>
      </div>
      <br>
      <fieldset class="m_5791859763537675412mimeAttachmentHeader"></fieldset>
      <br>
      </div></div><pre>______________________________<wbr>_________________
Ncep.list.nems.announce mailing list
<a class="m_5791859763537675412moz-txt-link-abbreviated" href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov" target="_blank">Ncep.list.nems.announce@<wbr>lstsrv.ncep.noaa.gov</a>
<a class="m_5791859763537675412moz-txt-link-freetext" href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce" target="_blank">https://www.lstsrv.ncep.noaa.<wbr>gov/mailman/listinfo/ncep.<wbr>list.nems.announce</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
    </font></span></blockquote><span class="HOEnZb"><font color="#888888">
    <br>
    <p><br>
    </p>
    <pre class="m_5791859763537675412moz-signature" cols="72">-- 
Dr. Shrinivas Moorthi
Research Meteorologist
Global Climate and Weather Modeling Branch
Environmental Modeling Center / National Centers for Environmental Prediction
5830 University Research Court - (W/NP23), College Park MD 20740 USA
Tel:(301)683-3718</pre>
  </font></span></div>

<br>______________________________<wbr>_________________<br>
Ncep.list.nems.announce mailing list<br>
<a href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov">Ncep.list.nems.announce@<wbr>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.<wbr>gov/mailman/listinfo/ncep.<wbr>list.nems.announce</a><br>
<br></blockquote></div><br></div>