<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,_September_15,_2020#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, September 15, 2020, </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: Shankar Adhikari, Alex Austregesilo, Thomas
                Britton, Mark Dalton, Sean Dobbs, Mark Ito (chair), Igal
                Jaegle, Naomi Jarvis, Simon Taylor, Nilanga
                Wickramaarachchi, Beni Zihlmann
              </p>
              <p>There is <a rel="nofollow" class="external text"
                  href="https://bluejeans.com/s/bDwJNbkUkhV/">a
                  recording of his meeting</a> on the BlueJeans site.
                Use your JLab credentials to authenticate.
              </p>
              <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,_September_1,_2020#Minutes"
                  title="GlueX Software Meeting, September 1, 2020">the
                  minutes from September 1.</a>
              </p>
              <ul>
                <li> The space situation with the work disk is better
                  now. There is <a rel="nofollow" class="external text"
href="https://halldweb.jlab.org/disk_management/work_disk_2.png">about
                    10% (or 20 TB) free now</a>. Thanks to those who
                  helped in the clean up.
                  <ul>
                    <li> <a rel="nofollow" class="external text"
                        href="https://halldweb.jlab.org/disk_management/work_report.html">The
                        work disk leader board</a> in back in operation.
                      Go there to see who is using the most space on the
                      work disk.</li>
                  </ul>
                </li>
                <li> Alex's problem with a large number of NIS lookups
                  in DSelector jobs has resolved itself. We are not sure
                  why.</li>
              </ul>
              <h3><span class="mw-headline"
                  id="Talk_at_OSG_All-Hands_Meeting">Talk at OSG
                  All-Hands Meeting</span></h3>
              <p>Mark I. reviewed some of the points he made during <a
                  rel="nofollow" class="external text"
href="https://halldweb.jlab.org/doc-public/DocDB/ShowDocument?docid=4669">his
                  talk</a> at <a rel="nofollow" class="external text"
                  href="https://indico.fnal.gov/event/22127/">the Open
                  Science Grid All-Hands meeting</a> a little over a
                week ago. The talk was meant to emphasize the
                relationship between the EIC and the OSG.
              </p>
              <ul>
                <li> Computing and software management each have at
                  least two co-leaders, one of whom is from BNL and one
                  of whom is from JLab.</li>
                <li> Computing hardware resources are also envisioned to
                  be contributed from both of the labs.</li>
                <li> GlueX figures prominently in the list of OSG users
                  from medium-sized collaborations.</li>
                <li> CLAS12 used about 5 million core hours during the
                  month of July, comparable to GlueX usage for the
                  entire year.</li>
              </ul>
              <h3><span class="mw-headline"
                  id="PID_matching_suggestions_based_on_data.2FMC_comparisons">PID
                  matching suggestions based on data/MC comparisons</span></h3>
              <p>Sean led us through the first slide (see below) of <a
                  rel="nofollow" class="external text"
href="https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4652">his
                  talk</a> on future areas for data vs. Monte Carlo
                comparisons. He will give a complete presentation at
                next week's HDGeant4 Meeting.
              </p>
              <div class="thumb tright">
                <div class="thumbinner" style="width:302px;"><a
href="https://halldweb.jlab.org/wiki/index.php/File:Sdobbs_pid_20200908.png"
                    class="image"><img alt="Sdobbs pid 20200908.png"
src="https://halldweb.jlab.org/wiki/images/thumb/9/9d/Sdobbs_pid_20200908.png/300px-Sdobbs_pid_20200908.png"
                      class="thumbimage" width="300" height="225"></a> </div>
              </div>
              <p>From the discussion:
              </p>
              <ul>
                <li> On widening TOF cuts as a function of momentum:
                  <ul>
                    <li> Simon reported that there is already a hook to
                      do this in the PIDFOM system.</li>
                    <li> Alex reported that there is also a mechanism
                      available for a momentum-dependent cut when doing
                      particle identification in the Analysis Library.</li>
                  </ul>
                </li>
              </ul>
              <h3><span class="mw-headline"
                  id="Review_of_recent_issues_and_pull_requests">Review
                  of recent issues and pull requests</span></h3>
              <p>Thomas brought up a <a rel="nofollow" class="external
                  text"
                  href="https://github.com/JeffersonLab/halld_sim/pull/153">recent
                  pull request to the halld_sim repository</a> from
                Alex. This fixes a problem where simulation jobs can go
                into an infinite loop if the CCDB does not show any flux
                for a corresponding real data run. The change was made
                to the beam properties class.
              </p>
              <h3><span class="mw-headline"
                  id="New_guidance_for_selecting_version_sets_with_MCwrapper">New
                  guidance for selecting version sets with MCwrapper</span></h3>
              <p>Sean described his new wiki page, <a
href="https://halldweb.jlab.org/wiki/index.php/How_to_choose_software_versions_on_the_MC_submission_form"
                  title="How to choose software versions on the MC
                  submission form">How to choose software versions on
                  the MC submission form</a>. This led to discussion on
                related topics.
              </p>
              <ul>
                <li> Shankar asked for advice on how to specify the RCDB
                  query to be used for a range of runs. Turns out that
                  each run period has a different query and they are not
                  called out on the form. This is because the "best"
                  underlying query to the RCDB is different for each run
                  period, thus different query aliases are needed for
                  each instance. This needs better documentation.</li>
              </ul>
              <h3><span class="mw-headline"
                  id="Specifying_Simulation_Runs">Specifying Simulation
                  Runs</span></h3>
              <p>Mark D. noted that when filling out the MCwrapper web
                form, it is hard to remember the "correct" responses,
                those that worked well in a previous project. Thomas
                pointed out a feature ("mod=2") where parameters from a
                previous project can be copied into a new form, with the
                exception of some fields that probably should not be
                re-used, such as the output file location.
              </p>
              <h3><span class="mw-headline"
                  id="Need_for_a_New_Version_Set">Need for a New Version
                  Set</span></h3>
              <p>Sean and Shankar pointed out that we are due for a new
                version set that incorporates recent improvements to
                several packages. Mark I. agreed to produce one.
              </p>
              <h3><span class="mw-headline" id="Action_Item_Review">Action
                  Item Review</span></h3>
              <ol>
                <li> Ask the Computer Center about staging the start of
                  jobs in time.</li>
                <li> Make sure that the automatic tests of HDGeant4 pull
                  requests have been fully implemented.</li>
                <li> Create a new version set with the latest
                  improvements. (Mark I.)</li>
              </ol>
            </div>
          </div>
        </div>
      </div>
    </div>
  </body>
</html>