<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Folks,</p>
    <p>Please find the minutes <a moz-do-not-send="true"
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_August_4,_2020#Minutes">here</a>
      and below.</p>
    <p>  --  Mark</p>
    <p>
    </p>
    <div id="globalWrapper">
      <div id="column-content">
        <div id="content" class="mw-body" role="main">
          <h2 id="firstHeading" class="firstHeading" lang="en"><span
              dir="auto">GlueX Software Meeting, August 4, 2020, </span><span
              class="mw-headline" id="Minutes">Minutes</span></h2>
          <div id="bodyContent" class="mw-body-content">
            <div id="mw-content-text" dir="ltr" class="mw-content-ltr"
              lang="en">
              <p>Present: Alex Austregesilo, Thomas Britton, Mark Ito
                (chair), Richard Jones, Naomi Jarvis, David Lawrence,
                Susan Schadmand, Beni Zihlmann
              </p>
              <p>There is <a rel="nofollow" class="external text"
                  href="https://bluejeans.com/s/NwcD67rD2@l/">a
                  recording of his meeting</a> on the BlueJeans site.
                Use your JLab credentials to authenticate.
              </p>
              <h3><span class="mw-headline" id="Announcements">Announcements</span></h3>
              <p><a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2020-July/008283.html">Draft
                  of DSelector documentation</a>. See Beni for the link
                to edit the Overleaf document.
              </p>
              <h3><span class="mw-headline"
                  id="Review_of_Minutes_from_the_Last_Software_Meeting">Review
                  of Minutes from the Last Software Meeting</span></h3>
              <p>We went over <a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_July_21,_2020#Minutes"
                  title="GlueX Software Meeting, July 21, 2020">the
                  minutes from July 21</a>.
              </p>
              <h4><span class="mw-headline"
                  id="Corrupt_CCDB_SQLite_Files">Corrupt CCDB SQLite
                  Files</span></h4>
              <p>Mark reported that instances of corrupt CCDB SQLite
                files have occurred several times over the past two
                weeks. Recall that the error is "Lost connection to
                MySQL server." The new size requirement has been
                catching them and bad ones are not getting shipped to
                Oasis.
              </p>
              <h4><span class="mw-headline"
                  id="Compiler_upgrade_discussion">Compiler upgrade
                  discussion</span></h4>
              <p>Mark reported that <a
href="https://halldweb.jlab.org/wiki/index.php/HOWTO_use_prebuilt_GlueX_software_from_any_linux_user_account_using_cvmfsexec"
                  title="HOWTO use prebuilt GlueX software from any
                  linux user account using cvmfsexec">Richard's HOWTO</a>
                on installing and running <a rel="nofollow"
                  class="external text"
                  href="https://github.com/cvmfs/cvmfsexec">cvmfsexec</a>
                allowed him to easily install Oasis on Mark's RHEL7 box
                at the Lab. This, coupled with our standard container,
                allows almost instant access to a JLab-like
                development/running environment, as advertised. With a
                CentOS 8 container, which is in the works, it could ease
                our transition to a more advanced version of GCC.
              </p>
              <h3><span class="mw-headline"
                  id="Restoration_of_Execution_Tests_for_Pull_Request_Builds">Restoration
                  of Execution Tests for Pull Request Builds</span></h3>
              <p><a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2020-July/008272.html">This</a>]
                is working now.
                Sean Dobbs may have more to say at the next meeting.
                Mark pointed out that there is new environment set-up
                scheme to ensure consistency between building and
                running the binary tests.
              </p>
              <h3><span class="mw-headline"
                  id="Sluggish_Response_on_halldweb.jlab.org">Sluggish
                  Response on halldweb.jlab.org</span></h3>
              <p>Several people have been noticing periods of slow
                response from our main webserver, halldweb.jlab.org,
                including, not not limited to, use of the wikis.
                Yesterday morning the server was timing out on requests,
                not good at all. Mark reported that during slow-downs,
                the webserver has plenty of idle CPU cycles and does not
                appear to be swapping. It is the case that the majority
                of web requests during these times are from the
                MCwrapper Dashboard, at the level of a few Hertz from
                multiple browser clients. Thomas assured us that those
                operations are light weight and cannot account for the
                slow-downs. Going forward:
              </p>
              <ul>
                <li> Thomas has increased the period between updates
                  requests from the browser application, despite his
                  assertion that those requests cannot possibly be the
                  problem, at Mark's request.</li>
                <li> Naomi suggested that people submit ServiceNow
                  requests (write an email to <a class="moz-txt-link-abbreviated" href="mailto:helpdesk@jlab.org">helpdesk@jlab.org</a>)
                  whenever a problem is encountered. That might raise
                  the visibility of the issue.</li>
                <li> Mark mentioned the possibility of putting up a
                  dedicated server, either a webserver, database server,
                  or both, to move the load away from other essential
                  functions on halldweb.</li>
                <li> Mark also suggested that the Computer Center
                  implement some sort of history mechanism that might
                  help identify the bottleneck.</li>
              </ul>
              <h3><span class="mw-headline"
                  id="dE.2Fdx_theta_Correction">dE/dx theta Correction</span></h3>
              <p>Naomi reported that her improvements to the CDC dE/dx
                measurement located on <a rel="nofollow"
                  class="external text"
href="https://github.com/JeffersonLab/halld_recon/tree/nsj_dedx_theta_correction">this
                  branch</a> are ready to go. She expressed her concern
                that the dE/dx quantities would undergo a sudden change
                if this branch were merged, making those quantities
                inconsistent with those encoded in REST files from
                previous reconstruction launches. Mark said that similar
                improvements are merged all the time. Beni gave a strong
                suggestion that the pull request be composed. [Added in
                press: Naomi submitted the pull request and Beni merged
                it with the comment "too good to not have."]
              </p>
              <h3><span class="mw-headline"
                  id="Python_3_Compatible_Build_System">Python 3
                  Compatible Build System</span></h3>
              <p>Mark described the changes, <a rel="nofollow"
                  class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2020-July/008279.html">announced
                  last week</a>, that allows us to build our software on
                either a Python-2-based system or on one based on Python
                3. See <a rel="nofollow" class="external text"
href="https://docs.google.com/presentation/d/16L5cOT_Eh3a0H11I9oQvBKPFmkL46x-7-4NHswDglrw/edit?usp=sharing">his
                  slides</a> for details. This work is a first step at
                developing a container system for CentOS 8.
              </p>
              <h3><span class="mw-headline"
                  id="Review_of_recent_issues_and_pull_requests">Review
                  of recent issues and pull requests</span></h3>
              <p>David called our attention to halld_recon Issue #418, <b>hd_root
                  hangs at the end of evio file with is_valid_run_end =
                  false</b>, originally submitted by Naomi. Richard will
                have a look.
              </p>
              <h3><span class="mw-headline"
                  id="Review_of_recent_discussion_on_the_GlueX_Software_Help_List">Review
                  of recent discussion on the GlueX Software Help List</span></h3>
              <p>We went over two items:
              </p>
              <ul>
                <li> <a rel="nofollow" class="external text"
                    href="https://groups.google.com/g/gluex-software/c/tDLG5qcStjA">JLab
                    logbook image upload problem</a>. We heard that Mark
                  Dalton has received enough feedback to proceed.</li>
                <li> <a rel="nofollow" class="external text"
                    href="https://groups.google.com/g/gluex-software/c/FFKZCBWIAgI">Simulation
                    stuck at first event</a>. Igal Jaegle is still
                  having this problem. Richard will take a look.</li>
              </ul>
            </div>
            <div class="printfooter">
              Retrieved from "<a dir="ltr"
href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_August_4,_2020&oldid=100891">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_August_4,_2020&oldid=100891</a>"</div>
          </div>
        </div>
      </div>
      <div id="footer" role="contentinfo">
        <ul id="f-list">
          <li id="lastmod"> This page was last modified on 4 August
            2020, at 19:21.</li>
        </ul>
      </div>
    </div>
  </body>
</html>