<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <p>People,</p>
    <p>Please find the minutes <a moz-do-not-send="true" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_July_20,_2021#Minutes">here</a>
      and below.</p>
    <p>  -- Mark</p>
    <p>     _____________________________________</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, July 20, 2021, </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, Sean Dobbs, Mark Ito
                (chair), Richard Jones, David Lawrence, Churamani
                Paudel, Simon Taylor, Jon Zarling, Beni Zihlmann
              </p>
              <p>There is a <a rel="nofollow" class="external text" href="https://bluejeans.com/s/Ksrj6a84hWJ">recording
                  of this meeting</a>. Log into the <a rel="nofollow" class="external text" href="https://jlab.bluejeans.com">BlueJeans site</a>
                first to gain access (use your JLab credentials).
              </p>
              <h3><span class="mw-headline" id="Announcements">Announcements</span></h3>
              <ol>
                <li> New work disk is up and running as a disk server.
                  Files are being migrated from old server to new.
                  Initially we will have about 400 TB on the new server
                  compared to the 200 TB we have on the current
                  /work/halld and 50 TB we have on /work/halld3. After
                  the transition is complete, the old servers will have
                  their operating systems upgraded and will be
                  redeployed, so we will recover the old disk space in
                  addition to the new.</li>
                <li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-July/008582.html">AmpTools
                    v0.12.1</a>. We reviewed Matt Shepherd's
                  announcement. There is a new version set available
                  that has this bug-fix release of AmpTools (version set
                  4.42.1)</li>
              </ol>
              <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 the <a href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_July_6,_2021#Minutes" title="GlueX Software Meeting, July 6, 2021">minutes
                  from the meeting on July 6th</a>. Turns out we did
                have a work disk squeeze since the last meeting. Mark
                Dalton and George Vasileiadis helped out to reduce usage
                on /work/halld.
              </p>
              <h3><span class="mw-headline" id="Review_of_Minutes_from_the_Last_HDGeant4_Meeting">Review
                  of Minutes from the Last HDGeant4 Meeting</span></h3>
              <p>We reviewed the <a href="https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_July_13,_2021#Minutes" title="HDGeant4 Meeting, July 13, 2021">minutes from
                  the meeting on July 13th</a>. Richard has made
                progress on adding realism to the FDC efficiency
                modeling. See <a rel="nofollow" class="external text" href="https://github.com/JeffersonLab/HDGeant4/issues/181#issuecomment-884957518">this
                  Issue</a> on the HDGeant4 GitHub site.
              </p>
              <h3><span class="mw-headline" id="FAQ_of_the_Fortnight">FAQ
                  of the Fortnight</span></h3>
              <p>Mark introduced a new segment of the Software Meetings:
                FAQ of the Fortnight. At future meetings, he will lead
                us through one of the FAQ's (or similar pieces of
                documentation) in an effort to boost collaboration
                productivity. This week we reviewed <a href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_FAQ#Where_do_I_find_version_set_files.3F" title="GlueX Offline FAQ">Where do I find version set
                  files?</a>. You can find the tour starting at 14:30 in
                the recording.
              </p>
              <h3><span class="mw-headline" id="DSelector_Choices_and_Disk_Footprints">DSelector
                  Choices and Disk Footprints</span></h3>
              <p>Jon has been looking several ROOT-related and
                ROOT-adjacent software ideas with an eye toward reducing
                storage size of ROOT trees and improving I/O performance
                when reading them back. See <a href="https://halldweb.jlab.org/wiki/images/d/df/OfflineJZ_footprint_and_uproot_7.20.21.pdf" class="internal" title="OfflineJZ footprint and uproot
                  7.20.21.pdf">his slides</a> for all of the details.
                His conclusion slide reads:
              </p>
              <ul>
                <li> Either ROOT::Math::LorentzVector or four doubles
                  could reduce our footprint by about 50%
                  <ul>
                    <li> ROOT::Math::LorentzVector could probably be
                      wrapped into DLorentzVector (replacing
                      TLorentzVectors currently implemented)</li>
                  </ul>
                </li>
                <li> Fiducial kinfit cuts could reduce the footprint
                  even more (but might need analyzer input)</li>
                <li> Using LZ4 compression (ROOT 6.24.00+) increases
                  size by 15-20%
                  <ul>
                    <li> But can parse 1.5-2× faster</li>
                  </ul>
                </li>
                <li> Working on a wrapper for uproot in flat tree
                  format, stay tuned!</li>
              </ul>
              <h3><span class="mw-headline" id="System_for_using_GCC_8_with_the_GlueX_software_stack">System
                  for using GCC 8 with the GlueX software stack</span></h3>
              <p>Mark reviewed <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-July/008587.html">his
                  email message</a> outlining a new system, ready for
                testing, for accessing a more advanced version of the
                GCC compiler that is shipped with CentOS 7. This allows
                access to more modern versions of our support software,
                in particular at present the latest version of Geant4.
              </p>
              <p>There is a <a href="https://halldweb.jlab.org/wiki/index.php/HOWTO_Run_Gluex_Software_with_GCC_8" title="HOWTO Run Gluex Software with GCC 8">new HOWTO</a>
                on...well...how to use the system in a Singularity
                container. This method is currently available on the OSG
                and the HPC centers. Mark is working on other approaches
                including running CentOS 8 and using GCC "modules" at
                JLab.
              </p>
              <h3><span class="mw-headline" id="Review_of_recent_issues_and_pull_requests">Review
                  of recent issues and pull requests</span></h3>
              <p>We discussed halld_recon issue #537, <a rel="nofollow" class="external text" href="https://github.com/JeffersonLab/halld_recon/issues/537">Problems
                  with photon energies in MC samples</a> posted by Sean.
                Please see the issue for all of the details. This one is
                tough because it is hard to reproduce.
              </p>
              <p>On another front, Sean also mentioned that Igal is
                having a non-reproducible issue with the last of the
                hundreds of jobs in a run hanging at the end of its
                file.
              </p>
              <h3><span class="mw-headline" id="Action_Item_Review">Action
                  Item Review</span></h3>
              <ol>
                <li> Decide on needed tape volume sets. (Sean, Mark I.)</li>
                <li> Review disk usage when re-repatriating recon launch
                  data. (Alex, Mark)</li>
                <li> Discuss automatically making CCDB entries for
                  selected RCDB items. (Mark I., Sean)</li>
                <li> Modify the documentation on how to copy files from
                  JLab. (Mark I.)</li>
                <li> Generate finer-grained info on small cache files.
                  (Mark I.)</li>
              </ol>
            </div>
            <br>
          </div>
        </div>
      </div>
    </div>
  </body>
</html>