<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Folks,<br>
    <br>
    Please find the minutes reproduced below and at
    <a class="moz-txt-link-freetext" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_March_2,_2016">https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_March_2,_2016</a>
    .<br>
    <br>
      -- Mark<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;">
        <h1 id="firstHeading" class="firstHeading" style="font-weight:
          bold;" lang="en"><span dir="auto">GlueX Offline Meeting, March
            2, 2016, </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">
            <table>
              <tbody>
                <tr>
                  <td>There is a<span class="Apple-converted-space"> </span><a
                      rel="nofollow" class="external text"
                      href="https://bluejeans.com/s/9dy1/" 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 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>FSU</b>: Brad Cannon</li>
                      <li><b>JLab</b>: Sergey Furletov, Mark Ito
                        (chair), Paul Mattione, Dmitry Romanov, Nathan
                        Sparks</li>
                      <li><b>NU</b>: Sean Dobbs</li>
                      <li><b>UConn</b>: Richard Jones</li>
                    </ul>
                  </td>
                  <td>
                    <div class="thumb tleft" style="page-break-inside:
                      avoid; border: none; width: auto; margin: 0.5em
                      1.4em 0.8em 0px; float: left; clear: left;
                      background-color: transparent;">
                      <div class="thumbinner" style="border: 1px solid
                        rgb(204, 204, 204); font-size: 15.04px;
                        text-align: center; overflow: hidden; padding:
                        3px !important; width: 202px; background-color:
                        white;"><a href="https://bluejeans.com/s/9dy1/"
                          style="color: rgb(85, 34, 0); padding: 0px
                          !important; text-decoration: underline;
                          background: transparent;"><img alt=""
                            src="cid:part2.09050602.09040206@jlab.org"
                            class="thumbimage"
                            srcset="/wiki/images/thumb/0/0d/Software_meeting_2016-03-02.png/300px-Software_meeting_2016-03-02.png
                            1.5x,
                            /wiki/images/thumb/0/0d/Software_meeting_2016-03-02.png/400px-Software_meeting_2016-03-02.png
                            2x" style="page-break-inside: avoid; border:
                            1px solid rgb(204, 204, 204);
                            vertical-align: middle;" height="132"
                            width="200"></a>
                        <div class="thumbcaption" style="border: none;
                          text-align: left; line-height: 1.4em;
                          font-size: 14.1376px; padding: 3px
                          !important;">Software Meeting</div>
                      </div>
                    </div>
                  </td>
                </tr>
              </tbody>
            </table>
            <h3 style="page-break-after: avoid; font-weight: bold;"><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/2016-February/002223.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">Deleting legacy builds</a>.
                They were backed up and deleted.</li>
              <li><a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/jlab-scicomp-briefs/2016q1/000120.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">Lustre upgrade</a>. The
                upgrade had to be abandoned for now. SciComp will
                continue to study the upgrade path.</li>
              <li>Software Help Forum delayed. Mark had a concern about
                whether we should be mixing scientific paper discussions
                and software questions and answers on the same site.
                Computer and Network Infrastructure (CNI) is putting
                together a Drupal-based forum for us to test drive.</li>
              <li>Paper Review Status. The requested materials have been
                submitted to Graham Heyes:
                <ol>
                  <li>Responses to recommendations to past software
                    reviews.</li>
                  <li>Progress in GlueX software since the last review
                    (Feb. 2015)</li>
                  <li>A revised computing resource need estimate.
                    <ul style="list-style-type: square;">
                      <li>Mark and Graham are still going back and forth
                        on the spreadsheet format.</li>
                    </ul>
                  </li>
                </ol>
              </li>
              <li><a
                  href="https://halldweb.jlab.org/wiki/index.php/SWIF_Analysis_Jobs"
                  title="SWIF Analysis Jobs" style="color: rgb(85, 34,
                  0); padding: 0px !important; text-decoration:
                  underline; background: transparent;">SWIF Analysis
                  Jobs</a>. Paul put together a wiki page on how to get
                started with the Scientific Workflow Indefatigable
                Factotum (SWIF). He provides a simple set of scripts.
                The system is oriented toward using REST data to do
                physics analysis.
                <ul style="list-style-type: square;">
                  <li>Dmitry mentioned that he is interested in a system
                    that starts from data in the RCDB and generates a
                    template for batch analysis of chosen files. He will
                    talk to Paul about whether Paul's system might help
                    with this.</li>
                </ul>
              </li>
            </ol>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Review_of_minutes_from_February_3">Review of<span
                  class="Apple-converted-space"> </span><a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_February_3,_2016#Minutes"
                  title="GlueX Offline Meeting, February 3, 2016"
                  style="color: rgb(85, 34, 0); padding: 0px !important;
                  text-decoration: underline; background: transparent;">minutes
                  from February 3</a></span></h3>
            <ul style="list-style-type: square;">
              <li>Mark commented that many users are taking advantage of
                the one-node/multi-thread job queue that Scientific
                Computing (SciComp) has put up recently.</li>
              <li>Dmitry reminded us that the best way to make requests
                for bug fixes or new features is to create an issue on
                the<span class="Apple-converted-space"> </span><a
                  rel="nofollow" class="external text"
                  href="https://github.com/JeffersonLab/rcdb"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">RCDB GitHub site</a>. That
                way it will not get lost in the email shuffle.
                <ul style="list-style-type: square;">
                  <li>Note that the RCDB code is still being kept in our
                    Subversion repository. Migration of the code to
                    GitHub will not occur until after the current run.</li>
                </ul>
              </li>
            </ul>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Offline_Monitoring">Offline
                Monitoring</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Paul pointed out some features of the<span
                class="Apple-converted-space"> </span><a
href="https://halldweb.jlab.org/wiki/index.php/Data_Monitoring_Procedures#Procedures:_Overview"
                title="Data Monitoring Procedures" style="color: rgb(85,
                34, 0); padding: 0px !important; text-decoration:
                underline; background: transparent;">Monitoring Plan</a>.
              He commented on the three steps during experimental
              running:</p>
            <ol>
              <li>Incoming. This is underway on all new data as it hits
                the tape library.</li>
              <li>Monitoring Launches. He is waiting on calibration
                constants from the Calibration Train to show up before
                starting.</li>
              <li>Initial Reconstruction Launch. We are not there yet.</li>
            </ol>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">We decided not to wait for the
              ultimate constants from calibration and go ahead and start
              a Monitoring Launch on Friday, after Sean has done some
              touch-up to the timing constants. Also since there is not
              a lot of data yet, that launch could go ahead and process
              all of the data collected so far, effectively making it an
              preliminary Initial Reconstruction Launch.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Mahmoud mentioned that the monitoring
              plugin for the Start Counter is not seeing any TDC hits.
              He and Paul will get together to track down the problem.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="Calibration_Challenge.2FProcessing"><a
                  rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2016-March/002257.html"
                  style="color: inherit !important; padding: 0px
                  !important; text-decoration: inherit !important;
                  background: transparent;">Calibration
                  Challenge/Processing</a></span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Sean described details of the the
              newly initiated calibration passes on recently taken data.
              See<span class="Apple-converted-space"> </span><a
                rel="nofollow" class="external text"
href="https://halldweb.jlab.org/wiki/images/0/02/Sdobbs_OfflineMtg_2Mar16.pdf"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">his two slides</a><span
                class="Apple-converted-space"> </span>for all of the
              bullets. In addition to the calibration steps, he
              discussed doing π<sup>0</sup><span
                class="Apple-converted-space"> </span>skims and a couple
              of items left to do.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">The last of the to-do items prompted
              a discussion on how we should feedback our experience with
              farm performance to SciComp and what metrics should be
              included in that feedback. We decided to discuss this next
              week after we see how the weekend's launch goes.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Geant4_Update">Geant4 Update</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Richard has been busy with diamond
              production lately, a good thing for all of us, and will
              return to work on Geant4 when the run is over.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline"
                id="C.2B.2B_version_upgrade_discussion">C++ version
                upgrade discussion</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">After lengthy discussion we settled
              on June 1, 2016 as the date for sim-recon conversion to
              GCC 4.9. See the<span class="Apple-converted-space"> </span><a
                rel="nofollow" class="external text"
                href="https://bluejeans.com/s/9dy1/" style="color:
                inherit !important; padding: 0px !important;
                text-decoration: inherit !important; background:
                transparent;">recording</a><span
                class="Apple-converted-space"> </span>for details. More
              precisely, after that date code that relies on language
              features present in that version of GCC will be accepted
              on the sim-recon master branch. When this happens
              collaborators will be required to upgrade their compilers
              if they have not done so.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Nathan agreed to write a wiki page to
              describe the<span class="Apple-converted-space"> </span><a
                rel="nofollow" class="external text"
                href="https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">Software Collections</a><span
                class="Apple-converted-space"> </span>system that allows
              installation of binaries for recent versions of GCC (among
              other things) for RedHat and CentOS systems. This has the
              potential to greatly simplify the compiler upgrade process
              and subsequent environmental set-up.</p>
            <h3 style="page-break-after: avoid; font-weight: bold;"><span
                class="mw-headline" id="Photon_beam_polarization">Photon
                beam polarization</span></h3>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Curtis called our attention to a<span
                class="Apple-converted-space"> </span><a rel="nofollow"
                class="external text"
href="http://argus.phys.uregina.ca/cgi-bin/private/DocDB/ShowDocument?docid=2968"
                style="color: inherit !important; padding: 0px
                !important; text-decoration: inherit !important;
                background: transparent;">recent note from Ken
                Livingston</a><span class="Apple-converted-space"> </span>where
              Ken gave his thoughts on how polarization information
              should be recorded and how that information should be used
              in data analysis. We agreed that this was required reading
              for those who would like to contribute to the discussion
              going forward.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Despite this admonition, we launched
              into a discussion of dealing with shifts of the location
              of the coherent edge during a run (i. e., beyond the
              photon energy dependence of the polarization for a fixed
              coherent edge position). This lead to whether it should be
              done by event ranges in the CCDB, which would require
              significant CCDB development, or fixed table of event
              dependent parameters, one table per run which could itself
              be kept in the CCDB.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">Mark pointed out that the need for
              this approach has not been demonstrated. Richard thought
              that it was likely that a thin diamond would not be
              stable. Mark conceded that in the end we would need event
              ranges in the CCDB, if not to handle this problem, then
              for others that might arise. That feature, however, will
              not be there tomorrow.</p>
            <p style="widows: 3; orphans: 3; margin: 1em 0px;
              line-height: 1.2em;">In the end we agreed that the first
              step is to assess the need, and if something has to be
              done, we will do it.</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,_March_2,_2016&oldid=73461"
              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,_March_2,_2016&oldid=73461</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 2 March 2016, at
          18:55.</li>
      </ul>
    </div>
    <br>
  </body>
</html>