<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Dear Colleagues, <br>
    </p>
    <p>We just completed a new monitoring launch over the 2019-01 PrimeX
      data set. We processed the first 5 files of 417 runs in the run
      range 61321 -  61956, selected with the RCDB query
      "@is_primex_production and @status_approved". The data was
      processed with a recent halld_recon version, but a few plugins
      created problems with the directory structure in the histogram
      file<span class="branch-details css-truncate v-align-middle">.
        This has been corrected now.<br>
      </span></p>
    <p>As usual, the monitoring plots can be found on the web pages:<br>
    </p>
    <a class="moz-txt-link-freetext"
href="https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/plotBrowser.py">https://halldweb.jlab.org/data_monitoring/Plot_Browser.html</a><br>
    <a class="moz-txt-link-freetext"
href="https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/runBrowser.py">https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/runBrowser.py</a><a
      class="moz-txt-link-freetext"
href="https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/versionBrowser.py"><br>
https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/versionBrowser.py</a>
    <br>
    <p>The merged histogram files can be found on the work disk at: <br>
      <i class="moz-txt-slash"><span class="moz-txt-tag">/work/halld/data_monitoring/RunPeriod-2019-01/mon_ver14/rootfiles/</span></i></p>
    <p>The REST files, random trigger skims and several trees are saved
      on cache: <br>
      <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>cache/halld/offline_monitoring/RunPeriod-2019-01/ver14/REST<span
          class="moz-txt-tag">/</span></i></p>
    <p><span class="moz-txt-slash"><span class="moz-txt-tag">We still
          observed about 20 crashes in the </span></span><span
        class="moz-txt-slash"><span class="moz-txt-tag">launch. Please
          find a list of the problematic log files below.</span></span><span
        class="moz-txt-slash"><span class="moz-txt-tag"> Most of them
          are due to truncated input files, but the error message for
          files 061477_000, 061507_002, 061793_003 caught my eye:<br>
        </span></span></p>
    <p><i class="moz-txt-slash"><span class="moz-txt-tag">JANA
          >>============================<br>
          JANA >> DL1MCTrigger: (brun)         --   line:281 
/u/group/halld/Software/builds/Linux_CentOS7.7-x86_64-gcc4.8.5/jana/jana_0.8.2/Linux_CentOS7.7-x86_64-gcc4.8.5/include/JANA/JFactory.h<br>
          JANA >> DL1MCTrigger<br>
          JANA >> DTrigger: (evnt)             --   line:299 
/u/group/halld/Software/builds/Linux_CentOS7.7-x86_64-gcc4.8.5/jana/jana_0.8.2/Linux_CentOS7.7-x86_64-gcc4.8.5/include/JANA/JFactory.h<br>
          JANA >> DTrigger<br>
          JANA >> JEventLoop:OneEvent  (evnt)  --   line:695 
          src/JANA/JEventLoop.cc<br>
          JANA >>----------------------------<br>
          <br>
        </span></i></p>
    <p>Best regards, <br>
    </p>
    <p> Alex <br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p>------</p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p>/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061342/stdout.061342_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061349/stdout.061349_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061434/stdout.061434_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061477/stdout.061477_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061498/stdout.061498_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061506/stdout.061506_002.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061507/stdout.061507_002.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061517/stdout.061517_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061703/stdout.061703_001.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061704/stdout.061704_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061710/stdout.061710_000.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061717/stdout.061717_002.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061753/stdout.061753_001.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061779/stdout.061779_003.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061793/stdout.061793_003.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061794/stdout.061794_004.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061806/stdout.061806_002.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061879/stdout.061879_001.out<br>
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061917/stdout.061917_003.out<br>
    </p>
  </body>
</html>