<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,_March_17,_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">
<h1 id="firstHeading" class="firstHeading" lang="en"><span
dir="auto">GlueX Software Meeting, March 17, 2020, </span><span
class="mw-headline" id="Minutes">Minutes</span></h1>
<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, Sean Dobbs,
Mark Ito (chair), Naomi Jarvis, David Lawrence, Keigo
Mizutani, Zisis Papandreou, and others perhaps[?]
</p>
<p>There is a <a rel="nofollow" class="external text"
href="https://bluejeans.com/s/6R_VR">recording of his
meeting</a> on the BlueJeans site. Use your JLab
credentials to access it.
</p>
<h3><span class="mw-headline" id="Announcements">Announcements</span></h3>
<ol>
<li> <a rel="nofollow" class="external text"
href="https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4384">Compute
Canada Award</a> Zisis announced the award of 265
core-years on Compute Canada. See the link for
details.
<ul>
<li> Thomas asked if there was a use-it-or-lose-it
aspect to the award with respect to the amount of
awards in subsequent years. If so he could arrange
it so that Compute Canada would be favored for
GlueX simulation jobs. Zisis will get back to
Thomas on this.</li>
</ul>
</li>
<li> <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2020-March/003938.html">New
Version Set released: version_4.16.0.xml</a> This
version set came out last week. It includes the new
version of CCDB (see the next announcement). Also,
this file the does <i>not</i> appear in the DIST
directory.
<ul>
<li> Note that the DIST directory has not
disappeared. All files that have been served from
there in the past remain there with the exception
of the version set files, which are now in
HALLD_VERSIONS.</li>
</ul>
</li>
<li> <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2020-March/003940.html">New
sub-minor release: CCDB 1.06.07</a>. This version
has substantially improved performance on the MySQL
servers.</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 <a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_March_3,_2020#Minutes"
title="GlueX Software Meeting, March 3, 2020">the
minutes from March 3</a>.
</p>
<h4><span class="mw-headline"
id="Recon_Launch_halld_recon_vs._Analysis_Launch_halld_recon">Recon
Launch halld_recon vs. Analysis Launch halld_recon</span></h4>
<p>We had further discussion of the
recon-launch/analysis-launch halld_recon version issue.
</p>
<ul>
<li> Thomas pointed out that the problem is complex. The
fact that the analysis library is part of halld_recon
is the root cause. There is no easy way out of the
situation.</li>
<li> He also mentioned that the pick-an-analysis-launch
approach could be done, but it does not solve all
problems. In particular, there are users who want
simulated REST files and have no interest or knowledge
about which analysis launch they should align with. In
addition, changes to MCwrapper-bot to implement this
are not simple. He also reminded us that the current
system is not missing functionality in the sense that
you can do nearly everything you would reasonably want
to do with it as it stands.</li>
<li> Sean suggested documentation so that users with
well-defined use cases can figure out what choices to
make on the bot-gui. </li>
<li> Alex reminded us that the recon launch versions
themselves need get rebuilt from time to time with
patches necessary to make them compatible with new
halld_sim versions, another complication.</li>
<li> Alex suggested trimming down the number of choices
on the bot-gui. That could be done but requires an
expert.</li>
<li> Mark admitted that there are some recon-launch
compatible versions sets that have yet to be built
against version set 4.16.0 (mentioned above).</li>
</ul>
<h4><span class="mw-headline" id="CCDB_Access_Control">CCDB
Access Control</span></h4>
<p>Mark spoke to Dmitry Romanov about this since the last
meeting. The access control is available in CCDB 2.0 and
can be implemented once that becomes the standard.
Dmitry said that a full-blown administrative interface
to configure the access control scheme is not there;
that is going to take a lot of Python coding. On the
other hand the scheme in its current state is
configurable; configuration is an expert operation
probably requiring use of the MySQL command line. So we
will accept that and use the feature.
</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 went over <a
href="https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_March_10,_2020#Minutes"
title="HDGeant4 Meeting, March 10, 2020">the minutes
from March 10</a> without significant discussion.
</p>
<h3><span class="mw-headline" id="Corrupt_EVIO_Files">Corrupt
EVIO Files</span></h3>
<p>Beni <a rel="nofollow" class="external text"
href="https://groups.google.com/forum/#!topic/gluex-software/s-AUOaXpPw0">reported
jobs crashing</a> on recently taken raw data files.
The problem has been traced to a single channel of a
Flash-250 in ROC 17. That module has been replaced.
Richard Jones has observed the problem in the data
already taken and is instituting a fix so that programs
can skip over the problematic blocks of data. David
expressed interest in reviewing the solution once it
becomes available.
</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> Alex will revisit <a rel="nofollow"
class="external text"
href="https://github.com/JeffersonLab/halld_recon/issues/166">halld_recon
Issue #116</a> "Vertex z dependent reconstruction
efficiency" to see if it is still with us.</li>
<li> Sean asked people to review changes in <a
rel="nofollow" class="external text"
href="https://github.com/JeffersonLab/halld_recon/pull/332">halld_recon
Pull Request #332</a> "Timing monitoring updates" to
make sure the guidance is correct and the expert email
lists are as they should be.</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>.
</p>
<p>Mark reported that the CCDB problem Igal Jaegle
reported over the weekend was due to a full root
partition on hallddb.jlab.org, our main MySQL server. We
were not able to determine the cause of the problem, but
Marty Wise has added disk space to the VM; the partition
was running at 36% full when he last checked.
</p>
<h3><span class="mw-headline" id="Action_Item_Review">Action
Item Review</span></h3>
<ol>
<li> Trim choices in MCwrapper-bot. (?)</li>
<li> Write a wiki page to describe how to navigate
MCwrapper-bot. (Thomas)</li>
<li> Implement a pick-your-analysis-launch option to
MCwrapper-bot (Thomas, long-term)</li>
<li> Build recon-launch compatible version sets with the
latest versions of halld_sim. (Mark)</li>
<li> Review changes to monitoring plot guidance from
Sean. (all)</li>
</ol>
</div>
<div class="printfooter">
Retrieved from "<a dir="ltr"
href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_March_17,_2020&oldid=97421">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_March_17,_2020&oldid=97421</a>"</div>
</div>
</div>
</div>
<div id="footer" role="contentinfo">
<ul id="f-list">
<li id="lastmod"> This page was last modified on 18 March
2020, at 17:42.</li>
</ul>
</div>
</div>
</body>
</html>