<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Please find the minutes <a moz-do-not-send="true"
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_November_26,_2019#Minutes">here</a>
      and below.</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, November 26, 2019, </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:
              </p>
              <ul>
                <li> <b> CMU: </b> Naomi Jarvis</li>
                <li> <b> JLab: </b> Thomas Britton, Mark Ito (chair),
                  Igal Jaegle, David Lawrence, Keigo Mizutani, Justin
                  Stevens, Simon Taylor, Beni Zihlmann</li>
              </ul>
              <p>There is a <a rel="nofollow" class="external text"
                  href="https://bluejeans.com/s/TdSMk/">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://mailman.jlab.org/pipermail/halld-offline/2019-November/003819.html">New
                    version set: version_4.11.0.xml</a> The latest set
                  of default version was released on November 19.</li>
                <li> <b>"atime" enabled on the work disk (/work/halld)</b>.
                  Until yesterday, files on the work disk have not had
                  their access times updated by the filesystem in order
                  to boost performance. Yesterday atime updates were
                  turned on on /work/halld. to be precise "relatime," a
                  ZFS feature was enabled. Atimes less than 24 hours in
                  the past are left alone. Having this feature will help
                  us distinguish between old files that have been used
                  recently and those that have gone unread for a long
                  time.</li>
                <li> <b>Work disk still full</b>. The work disk is at
                  98% full see the plot below for recent history and
                  follow <a rel="nofollow" class="external text"
                    href="https://halldweb.jlab.org/disk_management/work_report.html">this
                    link</a> to see a report on work disk usage.</li>
              </ol>
              <table>
                <tbody>
                  <tr>
                    <td>
                      <div class="thumb tright">
                        <div class="thumbinner" style="width:302px;"><a
href="https://halldweb.jlab.org/wiki/index.php/File:Work_disk_3.png"
                            class="image"><img alt=""
src="https://halldweb.jlab.org/wiki/images/thumb/0/03/Work_disk_3.png/300px-Work_disk_3.png"
                              class="thumbimage" width="300"
                              height="225"></a>
                          <div class="thumbcaption">Work Disk Usage</div>
                        </div>
                      </div>
                    </td>
                  </tr>
                </tbody>
              </table>
              <ol>
                <li> <b>Mirrors of CCDB SQLite Files</b>. Thomas
                  pointed out that there are still some MCWrapper users
                  out there using old versions that are pointing their
                  JLab Farm jobs to the SQLite files on the work disk.
                  The work disk has a known pathology with file locking
                  that causes these jobs to hang. He asked that those
                  files be deleted.
                  <ul>
                    <li> David suggested that we remove some legacy
                      magnetic field maps from the CCDB. They were kept
                      in to allow old code to access them there, but
                      that code is now many years old. Field maps are
                      now accessed as a JANA Resource. Deleting them
                      will save a lot of space in the database, and in
                      particular in the SQLite files generated from
                      MySQL, perhaps a factor of two or more. Mark will
                      look into doing this. </li>
                    <li> Added in press: the deed was done. See <a
                        rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2019-November/003824.html">this
                        email message from Mark</a> for more details.</li>
                  </ul>
                </li>
              </ol>
              <h3><span class="mw-headline"
                  id="Review_of_Minutes_from_the_Meeting_on_October_29">Review
                  of Minutes from the Meeting on October 29</span></h3>
              <p>We went over <a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_October_29,_2019#Minutes"
                  title="GlueX Software Meeting, October 29, 2019">the
                  minutes</a>.
              </p>
              <p>Beni emphasized the issue of upgrading from Python 2
                (P2) to Python 3 (P3). [Added in press: he refers us to
                <a rel="nofollow" class="external text"
href="https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html">this
                  link</a> on the subject].
              </p>
              <ul>
                <li> We run with a mixture of the two, scattered all
                  over the source code base.</li>
                <li> David pointed out last time that conversion from P2
                  to P3 mostly consists of changing "print" statements.</li>
                <li> He also told us that Python 2 official support ends
                  in January 2020.</li>
                <li> He has been using #!/usr/bin/python3 to identify
                  scripts that are meant for the P3 interpreter.</li>
                <li> And SCons uses P2 at present.</li>
                <li> P2 vs. P3 differs from C++ vs. C++11 in that the
                  compiler choice is made before building the entire
                  code base and so builds fail with the wring choice.
                  Whereas the interpreter choice is important only at
                  run-time allowing for more flexibility. In addition,
                  the choice of interpreter can be made explicitly on
                  the command line, e.g., <code>/path/to/python
                    script.py</code>.</li>
              </ul>
              <p>The clear path forward is still not visible.
              </p>
              <h3><span class="mw-headline"
                  id="Review_of_the_HDGeant4_Meeting_on_November_19">Review
                  of the HDGeant4 Meeting on November 19</span></h3>
              <p>We went over <a
href="https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_November_19,_2019#Minutes"
                  title="HDGeant4 Meeting, November 19, 2019">the
                  minutes</a>. There were no significant comments beyond
                those already in the minutes.
              </p>
              <h3><span class="mw-headline"
                  id="Accidental_scaling_factors_in_DSelectors">Accidental
                  scaling factors in DSelectors</span></h3>
              <p>The scaling factors, produced by Beni and Richard
                Jones, that correct for less-than-100% duty factor of
                the machine are <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2019-October/003801.html">now
                  available in the CCDB</a> thanks to Sean Dobbs.
              </p>
              <h3><span class="mw-headline"
                  id="New_CentOS_7.7_Nodes_on_the_JLab_Farm">New CentOS
                  7.7 Nodes on the JLab Farm</span></h3>
              <p>Beni brought up the subject of using the new nodes on
                the farm, <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/jlab-scicomp-briefs/2019q4/000229.html">announced
                  on November 15</a> running with CentOS 7.7. He was not
                able to get a successful build on ifarm1802 (recently
                upgraded to 7.7); there was a problem with the MySQL
                libraries. Justin pointed out that if we get a public
                build going on these nodes we can use them for
                monitoring launches to avoid competition with other
                tasks. Mark will look into a build on this platform.
              </p>
              <h3><span class="mw-headline"
                  id="New_Translation_Tables_for_Fall_2019">New
                  Translation Tables for Fall 2019</span></h3>
              <p>Justin reported that new translations tables are on the
                way. They incorporate the upgraded TOF, the GEM/TRD
                channels, and a few new DIRC-related channels.
              </p>
              <h3><span class="mw-headline"
                  id="Using_Google_Groups_for_Email_Forums">Using Google
                  Groups for Email Forums</span></h3>
              <p>We briefly discussed some of the problem with using
                Google Groups for email discussions. There are many
                positive aspects which motivated the switch in the first
                place, but down-sides have been noted:
              </p>
              <ul>
                <li> Use of non-google emails is a bit complicated and
                  has limitations (in particular where authentication is
                  needed).</li>
                <li> The group use of a single account to own the
                  groups, accessible to the entire Collaboration is
                  running into occasional security measures from Google.</li>
                <li> Authenticated web access from some universities
                  (including CMU) using Google Suite is an on-going
                  problem.</li>
              </ul>
              <p>CLAS12 and the Geant4 Collaborations are moving to a
                product called <a rel="nofollow" class="external text"
                  href="https://discourse.org/">Discourse</a>. <a
                  rel="nofollow" class="external text"
                  href="https://trello.com">Trello</a> was mentioned as
                another options. We probably would have to lobby, in
                concert with other groups at the lab, in order to get IT
                Division to pay for a site license for any of these
                products. This is not a crisis at this point, but it is
                something for us to think about.
              </p>
            </div>
            <div class="printfooter">
              Retrieved from "<a dir="ltr"
href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_November_26,_2019&oldid=95124">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_November_26,_2019&oldid=95124</a>"</div>
          </div>
        </div>
      </div>
      <div id="footer" role="contentinfo">
        <ul id="f-list">
          <li id="lastmod"> This page was last modified on 29 November
            2019, at 17:29.</li>
        </ul>
      </div>
    </div>
  </body>
</html>