<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,_May_11,_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, May 11, 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: Alexander Austregesilo, Thomas Britton, Mark
Dalton, Sean Dobbs, Mark Ito (chair), Igal Jaegle, David
Lawrence, Simon Taylor, Nilanga Wickramaarachchi, Jon
Zarling
</p>
<p>There is a <a rel="nofollow" class="external text" href="https://bluejeans.com/s/D1H@gQXCO1M/">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 href="https://halldweb.jlab.org/wiki/index.php/HOWTO_update_a_condition_on_the_RCDB" title="HOWTO update a condition on the RCDB">HOWTO
update a condition on the RCDB</a>. Sean described
his new wiki page. He stressed that changes to the
RCDB should be coordinated; don't change it and then
fail to mention it to anybody.
<ul>
<li> David asked about the particular example in the
HOWTO, changing the number of data files per run.
Igal responded that the number of files in a run
needed to match those submitted NERSC for jobs to
succeed. The RCDB thus sometimes needed
modification for cases where not all of the files
recorded to disk in the Counting House (original
file count) actually made it to tape in the
Computer Center (modified file count).</li>
<li> Mark reminded us that we could develop a system
where RCDB entries could be copied to the CCDB
automatically. From there they could be changed in
a way that left a historical record and a method
for dropping back to previous versions.</li>
</ul>
</li>
<li> <a rel="nofollow" class="external text" href="https://github.com/JeffersonLab/build_scripts/releases/tag/2.10">Build
Scripts 2.10</a>. Mark I. pointed out that users can
now set BUILD_SCRIPTS_CONSISTENCY_CHECK=false in their
environment to suppress warnings about inconsistent
software versions. He also pointed out that they do so
at their own risk.</li>
<li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-May/008536.html">New
version sets: 4.38.0 and related
recon-launch-compatible sets</a>. Mark I. led us
through the release notes for the new packages.</li>
<li> <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2021-May/008541.html">scan-build
revived</a>. Mark I. explained the latest scheme for
generating and accessing error/warning reports for
several of our software packages.</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,_April_28,_2021#Minutes" title="GlueX Software Meeting, April 28, 2021">Minutes
from the meeting on April 28</a>.
</p>
<ul>
<li> Mark I. continues to ping collaborators about their
usage of the work disk.</li>
<li> Mark I. did some checking on the values reported on
the online plots are accurate but more investigation
is needed.</li>
<li> Mark I., Sean, and Chris Larrieu discussed setting
up volume set in the tape library to speed retrieval
of skim data in the future. This requires very little
effort, just planning.</li>
<li> Jon has not received feedback on the ROOT-related
items he brought up, but progress has been made
nonetheless.
<ul>
<li> He has built ROOT 6.24 and has looked at
exploiting its features. Among them a new
compression scheme, based on <a rel="nofollow" class="external text" href="https://en.wikipedia.org/wiki/LZ4_(compression_algorithm)">LZ4</a>,
although increasing file size by 10-20%, decreases
reading time by a factor of two.</li>
<li> Jon has also test driven <a rel="nofollow" class="external text" href="https://github.com/scikit-hep/uproot4">uproot</a>.
In a chain that starts with a ROOT tree and ends
in <a rel="nofollow" class="external text" href="https://root.cern/manual/python/">PyROOT</a>-friendly
files[?] he sees a factor of three in speed.</li>
<li> Simon mentioned that in addition to
TLorentzVector, TVector2 and Tvector3 have been
deprecated. All of these classes are used a lot in
our charged track reconstruction. Going to the
new, recommended classes seems at least worth a
try.</li>
</ul>
</li>
<li> Sean reminded us that a complete set of <a rel="nofollow" class="external text" href="https://mailman.jlab.org/mailman/private/gluex-collaboration/2021-May/007816.html">random
trigger files for Fall 18</a> have been produced.</li>
</ul>
<h3><span class="mw-headline" id="Minutes_from_the_Last_HDGeant4_Meeting">Minutes
from the Last HDGeant4 Meeting</span></h3>
<p>We went over the <a href="https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_May_4,_2021#Minutes" title="HDGeant4 Meeting, May 4, 2021">Minutes from the
meeting on May 4th</a> without significant comment.
</p>
<h3><span class="mw-headline" id="Report_from_the_May_6th_SciComp_Meeting">Report
from the May 6th SciComp Meeting</span></h3>
<p>Mark I. gave <a rel="nofollow" class="external text" href="https://halldweb.jlab.org/doc-public/DocDB/ShowDocument?docid=5091">the
report</a>. Alex volunteered to compile a list of
files that we should prioritize for recovery, files that
are holding up analysis launches for Spring 2020.
</p>
<h3><span class="mw-headline" id="Review_of_recent_issues_and_pull_requests">Review
of recent issues and pull requests</span></h3>
<ul>
<li> halld_recon <a rel="nofollow" class="external
text" href="https://github.com/JeffersonLab/halld_recon/issues/512">Issue
#512: hd_root memory leak?</a> Sean has an idea on
what may be causing this.</li>
<li> Thomas will review outstanding issues in MCwrapper.
He thinks many of them can be closed.</li>
</ul>
<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 <a rel="nofollow" class="external text" href="https://groups.google.com/forum/#!forum/gluex-software">the
list</a>. Mark I. noted that recently a lot of
software Q&A has been conducted on Slack, which is
fine, but those exchanges are not archived. Because
Slack has proved popular within the JLab community, the
record only goes back to March at present. Many of these
conversations, in hindsight, should appear on the Help
List. Although it is understandable how a thread might
originate on Slack, Mark encouraged us to encourage our
collaborators to migrate the conversation to the Help
List where a search-able record of problems and
solutions can be maintained. </p>
<h3><span class="mw-headline" id="Action_Item_Review">Action
Item Review</span></h3>
<ol>
<li> Do a build against ROOT 6.24. (Mark I.)</li>
<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> Check validity of data reported in volatile usage
plots. (Mark I.)</li>
<li> Review outstanding issues with MCwrapper (Thomas)</li>
<li> Take another look at halld_recon issue #512. (Sean)</li>
<li> Make list of high-priority files for recovery from
tape errors. (Alex)
<ul>
<li> [Added in press: Alex generated a list and sent
it to Mark]</li>
</ul>
</li>
<li> Think about Jon's list of improvements. (all)</li>
<li> Automatically make CCDB entries for selected RCDB
items. (Mark I.)</li>
<li> Modify the documentation on how to copy files from
JLab. (Mark I.)</li>
<li> Look at replacements for TLorentzVector, TVector2,
and Tvector3 (all)</li>
</ol>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>