<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_2,_2022#Minutes">here</a>
and below.</p>
<p> -- Mark</p>
<p> ________________________________</p>
<p>
</p>
<div id="globalWrapper">
<div id="column-content">
<div id="mw-content-text" dir="ltr" class="mw-content-ltr"
lang="en">
<h2 id="firstHeading" class="firstHeading" lang="en"><span
dir="auto">Minutes, GlueX Software Meeting, March 2, 2022</span></h2>
<p>Present: Alex Austregesilo, Nathan Brei, Sean Dobbs, Bryan
Hess, Mark Ito (chair), Igal Jaegle, Richard Jones, David
Lawrence, Curtis Meyer, Keigo Mizutani, Wesley Moore, Simon
Taylor, Beni Zihlmann
</p>
<p>There is a <a rel="nofollow" class="external text"
href="https://jlab-org.zoomgov.com/rec/share/eCPvaj8NwRYSbGzYjDDr3wte-jwzRT23yoUfeTQl1k38WUkD-KcgduIdbrOxOMUw.WiMdUxV6bhMu3Z7M?startTime=1646245833000">recording
of this meeting</a> on the ZoomGov site. (Passcode:
htzd69.p)
</p>
<h3><span class="mw-headline" id="Announcements">Announcements</span></h3>
<p>Mark mentioned that there are <b>a series of pull requests
from Simon</b> responding to a request from Richard to
modify Simon's recent changes to the hddm_s schema, to
support the CPP muon chambers, backward compatible with
existing hddm data. The pull requests are for halld_recon,
halld_sim, and hdgeant4. Once they work their way through
the system, we will need a new version set.
</p>
<h3><span class="mw-headline"
id="OSG.2FOffsite_Computing_Update">OSG/Offsite Computing
Update</span></h3>
<p>Bryan brought us up-to-date with work over the last few
years to stand up the infrastructure, both hardware and
software, that allows us to use the OSG and other off-site
computing resources. Please see his slides for the details.
From the discussion:
</p>
<ul>
<li> With the new token-based authentication used in version
3.6, there is an issue with having multiple instances of
the submit host on the same physical node. We need this to
support the GlueX, JLab, and EIC VOs. A solutions is being
developed. </li>
<li> Bryan described the difficulty in exposing our large
Lustre partitions to access from offsite via XRootD.</li>
<li> He described the plan to use existing file servers to
carve out space to serve out GlueX data on StashCache.</li>
<li> Wes gave some details on a problem accessing StashCache
data via CVMFS from the farm. Work on this is on-going.</li>
<li> Sean mentioned the need for GlueX to communicate our
ideas on OSG-related workflows to SciComp and for SciComp
to keep us up-to-date with current work and new directions
in this area. Along these lines, Wes expressed a desire
for a channel where they can get feedback on solutions
that SciComp is pursuing. We agreed that we should have
regular meetings with interested parties to discuss these
topics, much as they were discussed at today's meeting.
Bryan will mention the concept at tomorrow's SciComp
meeting (where the other Halls are represented), Sean will
put together a list of the workflow ideas we are
contemplating and Mark will arrange a kick-off meeting at
the end of March.</li>
</ul>
<h3><span class="mw-headline"
id="Review_of_Minutes_from_the_Last_Software_Meeting.5D.5D">Review
of Minutes from the Last Software Meeting]]</span></h3>
<p>We looked at the <a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_February_16,_2022#Minutes"
title="GlueX Software Meeting, February 16, 2022">minutes
from February 16th meeting</a>. We need to get going on a
new system for producing containers. Related to that Mark is
working on adjustments to our builds so that there is no
difference between builds on the JLab CentOS 7 farm nodes
and those produced with a CentOS 7 container. Then these two
builds can be consolidated into one and this single build
can be shipped to Oasis for use off-site.
</p>
<h3><span class="mw-headline"
id="FAQ_of_the_Fortnight:_What_do_I_have_to_know_when_transitioning_from_SWIF_to_SWIF2.3F">FAQ
of the Fortnight: What do I have to know when
transitioning from SWIF to SWIF2?</span></h3>
<p>We looked again at Alex's <a
href="https://halldweb.jlab.org/wiki/index.php/Transition_from_SWIF_to_SWIF2"
title="Transition from SWIF to SWIF2">wiki page</a> giving
advice on the topic.
</p>
<p>Alex also mentioned that Chris Larrieu liked <a
rel="nofollow" class="external text"
href="https://groups.google.com/g/gluex-software/c/F3u3wQSS0CI">the
related discussion on the Software Help list</a>, but
Chris lamented the fact that folks in the other Halls will
not benefit from this and similar exchanges. Mark mentioned
that <a rel="nofollow" class="external text"
href="https://halldweb.jlab.org/doc-public/DocDB/ShowDocument?docid=4522">we
had proposed upgrading from Mailman</a> some time ago, but
that effort never got off the ground.
</p>
<h3><span class="mw-headline" id="Software_Coordination">Software
Coordination</span></h3>
<p>We went over the <a rel="nofollow" class="external text"
href="https://docs.google.com/document/d/1QF8fWjIoLHejyhXPgAzwjp6s5JLl6PM64efow1WnoBQ/edit">list
of responsibilities</a> that will have to be taken over by
others when the current Software Coordinator retires.
</p>
</div>
</div>
</div>
<div id="globalWrapper"><br>
</div>
</body>
</html>