<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,_December_6,_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, December 6, 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, Edmundo Barriga, Thomas
                Britton, Sean Dobbs, Sergey Furletov, Mark Ito (chair),
                Igal Jaegle, Richard Jones, Simon Taylor, Jon Zarling,
                Beni Zihlmann
              </p>
              <p>There is a <a rel="nofollow" class="external text" href="https://bluejeans.com/s/iHsrd3ouohh">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> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-October/008671.html">New
                    version set: 5.1.0</a> This version set was released
                  on October 29. Mark is preparing a new version set and
                  now that <a rel="nofollow" class="external text" href="https://github.com/JeffersonLab/halld_recon/pull/605">Pull
                    Request #605</a>, "Remove incorrect logic in TRUTH
                  photon construction," submitted by Sean, has been
                  merged by Alex, a new tag of halld_recon can be
                  applied and added to the new set.</li>
                <li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-November/008681.html">first
                    step toward a global filesystem for Gluex</a>.
                  Richard led a discussion of how we can use <a rel="nofollow" class="external text" href="https://opensciencegrid.org/docs/data/stashcache/overview/">StashCache</a>
                  to create, maintain, and analyze a global file system.
                  See <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-November/008681.html">his
                    email</a> for details.
                  <ul>
                    <li> The OSG is moving away from user X509
                      certificates and towards tokens for user
                      authentication. This (and other issues) have
                      caused a stoppage in job submission to the OSG
                      over the past few weeks
                      <ul>
                        <li> The stoppage was confirmed by Thomas. "We
                          are on the cutting edge of OSG use," he
                          reports.</li>
                      </ul>
                    </li>
                    <li> We should leverage efforts from the larger
                      community on data management. StashCache is an
                      example of an opportunity to do so.</li>
                    <li> Igal is interested in using this for PrimEx and
                      SRC/CT.</li>
                    <li> One leading candidate for using this is for
                      doing analysis launches on the OSG. This requires
                      having our REST data out there on StashCache.</li>
                    <li> Mark: We (aka he) need education on StashCache.
                      Perhaps Richard can give a pedagogically oriented
                      presentation at some point.</li>
                    <li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld/2021-December/000943.html">Transitioning
                        to Zoom</a> Mark put a wiki page together on the
                      topic and invited us to contribute content.</li>
                    <li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-November/008710.html">New
                        version set for simulating 2019-11 data</a>
                      There will be a new version sets coming out soon
                      to pick up the fix from Sean mentioned above (Pull
                      Request #605) as applied to the recon-launch
                      compatible builds (2017-01, 2018-01, 2018-08, and
                      2019-11).</li>
                  </ul>
                </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,_October_25,_2021#Minutes" title="GlueX Software Meeting, October 25, 2021">minutes
                  from the meeting on October 25th</a>.
              </p>
              <ul>
                <li> Thomas reported that the node formerly known as
                  scosg16 is being rebuilt as scosg16-dev and will serve
                  as a test platform for changes to OSG-related
                  software. This avoids bringing in changes, untested,
                  on the production Submit Host (now scosg20).</li>
                <li> CentOS Stream looks to be the choice (not yet
                  final) for a future upgrade of the JLab Farm.</li>
                <li> On <b>Package Structure</b>, Mark has concluded
                  that the project to render halld_sim and hdgeant4
                  independent of halld_recon by splitting out the pieces
                  of code used by all three is not easily done and will
                  require coding of interface routines, i.e., a
                  significant refactoring effort. He has succeeded in
                  doing the split in on a technical basis, but the
                  extracted code represents an unacceptably large
                  fraction of the various detector reconstruction
                  packages. The split code, though not suitable for
                  general use, may guide us if we want to pursue this
                  change in the future.</li>
              </ul>
              <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 went over the <a href="https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_November_29,_2021#Minutes" title="HDGeant4 Meeting, November 29, 2021">minutes
                  from the meeting on November 29</a>.
              </p>
              <p>Hao Li has marked <a rel="nofollow" class="external
                  text" href="https://github.com/JeffersonLab/HDGeant4/issues/195">Issue
                  #195</a>, "Crash adding daughters on RHEL/CentOS 8" as
                resolved.
              </p>
              <h3><span class="mw-headline" id="Report_from_the_November_4th_SciComp_Meeting">Report
                  from the November 4th SciComp Meeting</span></h3>
              <p>Mark promised a report soon. He knows y'all can't
                wait. ;-)
              </p>
              <h3><span class="mw-headline" id="FAQ_of_the_Fortnight:_How_do_I_get_notified_of_changes_in_a_repository_on_GitHub.3F">FAQ
                  of the Fortnight: How do I get notified of changes in
                  a repository on GitHub?</span></h3>
              <p>We took a quick look at the link provided in the <a href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_FAQ#How_do_I_get_notified_of_changes_in_a_repository_on_GitHub.3F" title="GlueX Offline FAQ">answer to this FAQ</a>.
              </p>
              <h3><span class="mw-headline" id="Upcoming_Computing_Review">Upcoming Computing
                  Review</span></h3>
              <p>We went over a few items linked from the <a href="https://halldweb.jlab.org/wiki/index.php/Software_and_Computing_Review_6" title="Software and Computing Review 6">Computing
                  Review wiki page</a>.
              </p>
              <ul>
                <li> There will be a meeting to show slides this
                  afternoon. All presenters in the review will present
                  what they have.</li>
                <li> A few of the slides that Mark prepared were
                  flashed.</li>
                <li> The pre-review handout document now runs to about
                  16 pages.</li>
              </ul>
              <h3><span class="mw-headline" id="Documentation_Upgrade">Documentation
                  Upgrade</span></h3>
              <p>Beni presented his thought on how we should improve
                software documentation. See <a rel="nofollow" class="external text" href="https://halldweb.jlab.org/talks/2021/usedoxy.pdf">his
                  slides</a> for all of the details. Some points (for
                emphasis):
              </p>
              <ul>
                <li> User's are well-positioned to comment on the
                  documentation and should be encouraged to do so.</li>
                <li> An overview presentation of the data analysis flow,
                  from reconstruction to analysis to ROOT analysis is
                  lacking.</li>
                <li> Richard: there are additional valuable resources
                  for software information:
                  <ul>
                    <li> The HOWTO wiki page.</li>
                    <li> Recordings of past Tutorials/Workfests</li>
                  </ul>
                </li>
                <li> Beni proposed forming a task force
                  <ul>
                    <li> Those present unanimously agreed that Beni
                      should be the chair.
                      <ul>
                        <li> Richard remarked that "we are all 100%
                          behind you, Beni."</li>
                      </ul>
                    </li>
                    <li> Mark volunteered to provide advice to the new
                      chair.</li>
                    <li> Beni will call an organizational meeting.</li>
                  </ul>
                </li>
              </ul>
            </div>
            <br>
          </div>
        </div>
      </div>
    </div>
  </body>
</html>