<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Please find the minutes below and at
    <a class="moz-txt-link-freetext" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_December_9,_2015#Minutes">https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_December_9,_2015#Minutes</a>
    .<br>
    <br>
    _______________________________<br>
    <br>
    <br>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    <div id="column-content" style="margin: 0px !important; color:
      rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: medium;
      font-style: normal; font-variant: normal; font-weight: normal;
      letter-spacing: normal; line-height: normal; orphans: auto;
      text-align: start; text-indent: 0px; text-transform: none;
      white-space: normal; widows: 1; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
      255);">
      <div id="content" class="mw-body" role="main" style="direction:
        ltr; color: black; border: none !important; padding: 1em;
        margin: 0px !important; background: white;">
        <h2 id="firstHeading" class="firstHeading" style="font-weight:
          bold;" lang="en"><span dir="auto">GlueX Offline Meeting,
            December 9, 2015</span>, Minutes</h2>
        <div id="bodyContent" class="mw-body-content"><span
            class="mw-headline" id="Minutes"></span>
          <div id="mw-content-text" dir="ltr" class="mw-content-ltr"
            lang="en">
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Present:</p>
            <ul style="list-style-type: square;">
              <li><b>CMU</b>: Naomi Jarvis, Curtis Meyer</li>
              <li><b>FIU</b>: Mahmoud Kamel</li>
              <li><b>JLab</b>: Alex Barnes, Mark Ito (chair), David
                Lawrence, Paul Mattione, Kei Moriya, Dmitry Romanov,
                Nathan Sparks, Justin Stevens, Simon Taylor</li>
              <li><b>NU</b>: Sean Dobbs</li>
            </ul>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">There is a<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
                href="https://bluejeans.com/s/8UyN/" style="color:
                inherit !important; padding: 0px !important;
                text-decoration: inherit !important; background:
                transparent;">recording of this meeting</a><span
                class="Apple-converted-space"> </span>on the BlueJeans
              site.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Announcements">Announcements</span></h3>
            <ul style="list-style-type: square;">
              <li><a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-November/002175.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">sim-recon 1.7.0</a><span
                  class="Apple-converted-space"> </span>was released on
                November 23.</li>
              <li><a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-December/002177.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">CCDB v1.06.00</a><span
                  class="Apple-converted-space"> </span>was released on
                December 3. v1.06.00 is about to come out. It fixes
                issues with password prompts on creation new variations.
                The C++ library is unaffected. Dmitry is responding to<span
                  class="Apple-converted-space"> </span><a
                  rel="nofollow" class="external text"
                  href="https://github.com/JeffersonLab/ccdb/wiki"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">issues</a><span
                  class="Apple-converted-space"> </span>reported on the
                GitHub site and has identified some of them as<span
                  class="Apple-converted-space"> </span><a
                  rel="nofollow" class="external text"
                  href="https://github.com/JeffersonLab/ccdb/wiki"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">milestones</a><span
                  class="Apple-converted-space"> </span>for v1.07.
                Documentation for CCDB is now kept on the<span
                  class="Apple-converted-space"> </span><a
                  rel="nofollow" class="external text"
                  href="https://github.com/JeffersonLab/ccdb/wiki"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">wiki</a><span
                  class="Apple-converted-space"> </span>on the CCDB
                GitHub site.</li>
              <li>JANA 0.7.4 was released on December 1. See<span
                  class="Apple-converted-space"> </span><a
                  rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-online/2015-December/000692.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">David's announcement</a><span
                  class="Apple-converted-space"> </span>for the details
                of this new version. 0.7.4p2 is the latest version and
                should be used for new builds.</li>
              <li>Curtis reported that we should expect a Software
                Review in Summer 2016.</li>
            </ul>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Review_of_Minutes_from_November_11">Review of
                Minutes from November 11</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">We went over the [[GlueX Offline
              Meeting, November 11, 2015#Minutes|minutes].</p>
            <ul style="list-style-type: square;">
              <li>Nathan updated the situation with binary
                distributions. After the last report some instabilities
                were encountered that have been addressed. Currently
                downloads for CentOS 6 and 7, RedHat 6 and 7, Ubuntu 14,
                and Fedora 22 are available.</li>
              <li>After our review of results from the semi-weekly b1pi
                tests, Paul went in a fixed a number of issues. The main
                one outstanding is the issue of BCAL timing (discussed
                later in the meeting).</li>
            </ul>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Offline_Monitoring_Report">Offline
                Monitoring Report</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Kei gave the report. He pointed out
              several webpages that compile statistics on each launch
              and do comparisons them between launches. See<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="https://halldweb1.jlab.org/wiki/images/0/0c/2015-12-09-offline_monitoring.pdf"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">his slides</a><span
                class="Apple-converted-space"> </span>for the details.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">We talked a bit about exit status
              codes from our binaries. JANA 0.7.4 reports a set of error
              codes when problems are detected, but main programs need
              to ask for the information and post them upon exit. None
              of our current programs do this. Sensible exit codes are
              very convenient and should be implemented going forward.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Paul noted that last Friday's launch
              had to be aborted due to software package
              incompatibilities. The re-launch was on Monday. Initial
              results are available.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Sean mentioned that the post-launch
              macros are not being run. He will get with Paul to get the
              directory location right.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Paul will be taking over the effort.
              He and the group thanked Kei for running the show and
              developing the system over the last year.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Update_to_CCDB_Microscope_Energy">Update to CCDB
                Microscope Energy</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Alex led us through<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="https://mailman.jlab.org/pipermail/halld-tagger/2015-November/000565.html"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">Richard's email</a><span
                class="Apple-converted-space"> </span>describing the
              change to the CCDB that corrects the (previously)
              anomalous relation between energy bins in the tagger
              microscope and those in the tagger hodoscope. The upshot:
              survey data was correct, but not reflected properly in the
              CCDB.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Justin asked if the constants are
              correct for simulation. That has been taken care of.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Alex cautioned the group: channels
              101 and 102 of the microscope exist as physical detectors,
              but there is no read-out instrumentation for them.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="BCAL_timing_calibration_and_pion_ID_in_Simulation">BCAL
                timing calibration and pion ID in Simulation</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Paul noticed a feature of the BCAL
              timing in the b1pi tests affecting both charged and
              neutral clusters. In particular as the momentum of pions
              increases, beta asymptotes at a value several percent
              below 1.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Sean has been looking into the issue.
              The individual hits times are OK, but the shower times are
              off from the truth in simulation by about half a
              nanosecond. Tegan has modified the clustering code, mainly
              to account for the curvature effect in the BCAL, and Sean
              has found that it does a better job on the timing than the
              standard algorithm. We will run some large-scale tests to
              confirm the effect. The BCAL group is comfortable with
              switching to the new algorithm if the tests come back
              favorable.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Sean mentioned that one lesson from
              this is that we should be paying closer attention to the
              b1pi test results. He will re-raise the issue at a future
              BCAL meeting.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="C.2B.2B_code_analyzer_.2B_clang_3.7.0">C++ code
                analyzer + clang 3.7.0</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">David led us through<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-December/002179.html"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">his email</a><span
                class="Apple-converted-space"> </span>announcing
              auto-generation (nightly) of a web page that reports
              possible problems in our C++ code. The report itself is
              available at<a rel="nofollow" class="external free"
                href="https://halldweb.jlab.org/scan-build/LATEST/"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">https://halldweb.jlab.org/scan-build/LATEST/</a><span
                class="Apple-converted-space"> </span>. The Clang/LLVM
              compiler suite generates the report simply by inspecting
              the source code. Richard and Simon have already modified
              code to avoid these warnings.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Dmitry mentioned another system
              called PVT Studio[?] that performs a similar function.
              There might be some non-overlap in the Venn diagram of
              problems detected.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="JANA_Status_Bits">JANA Status
                Bits</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">David us through<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-November/002172.html"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">his email</a><span
                class="Apple-converted-space"> </span>announcing a
              64-bit status word available in the new DStatusBits class.
              Please see his email for the rather complete details.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Run_Number_Assignments_for_Simulation_for_Future_Fun_Periods">Run
                Number Assignments for Simulation for Future Fun Periods</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Justin introduced the topic.
              Traditionally run numbers increment by one for each run
              started by the DAQ. Justin described the scheme used by
              STAR where the first 2 digits of the run number are the
              year, the next 3 are the Julian date, and the lower order
              digits are a serial number, reset to 1 (zero?) each day.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">The topic was raised at last week's
              calibration meeting. Our current policy is that when we
              generate simulated data that is supposed to match real
              detector conditions, the run numbers should be in the same
              range as the corresponding real data and the "mc"
              variation of CCDB should be used for calibration
              constants. Sean wants to generate data to match data to be
              taken in the Spring, but does not know what run number to
              use. This is a problem since the run numbers are encoded
              into the events at generation time. Sean advocated having
              a break in the run number sequence so that the next run
              range is predictable, say 10,000 to 19,999 for example.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">We did not come to any conclusions
              about this. David pointed out that others in the
              collaboration, especially the Online Working Group, and
              the JLab Data Acquisition Group will likely have important
              comments to make.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Review_of_Recent_Pull_Requests">Review
                of Recent Pull Requests</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">We went over all<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="https://github.com/JeffersonLab/sim-recon/pulls?q=is%3Aclosed+is%3Apr"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">pull requests for sim-recon</a>going
              back to the last meeting. We noted that<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
                href="https://github.com/JeffersonLab/sim-recon/pull/131"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">David's pull request</a><span
                class="Apple-converted-space"> </span>to implement
              64-bit run numbers required changes to 301 files.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Deleting_Old_Pull-Request_Builds">Deleting Old
                Pull-Request Builds</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Sean reported that we have
              accumulated about half a terabyte of builds to test pull
              request. He proposed deleting those older than a month and
              the group endorsed this. Mark will put together a cron job
              to do the deed.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Running_Tests_on_Pull-Requests_Builds">Running Tests
                on Pull-Requests Builds</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Nathan presented his thinking on
              running the pull-request builds as a further test of code
              viability. Please see<span class="Apple-converted-space"> </span><a
                rel="nofollow" class="external text"
                href="https://halldweb.jlab.org/talks/2015/crash-testing.pdf"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">his slides on "crash testing"</a>.
              He is putting together a script as proof-of-principle, to
              be run after successful pull-request builds.</p>
          </div>
          <div class="printfooter" style="padding: 1em 0px;">Retrieved
            from "<a dir="ltr"
href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_December_9,_2015&oldid=71858"
              style="color: rgb(85, 34, 0); padding: 0px !important;
              text-decoration: underline; background: transparent;">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_December_9,_2015&oldid=71858</a>"</div>
        </div>
      </div>
    </div>
    <div id="footer" role="contentinfo" style="color: rgb(0, 0, 0);
      margin-top: 1em; border-top-width: 1px; border-top-style: solid;
      border-top-color: rgb(170, 170, 170); direction: ltr; font-family:
      'Times New Roman'; font-size: medium; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: normal; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background: white;">
      <ul id="f-list" style="list-style-type: square;">
        <li id="lastmod">This page was last modified on 11 December
          2015, at 14:27.</li>
      </ul>
    </div>
    <br>
  </body>
</html>