<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Alex, <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks a lot Alex for processing these runs.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As I've mentioned, I updated a bunch of calibration constants <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
based on the this monitoring launch. Could you run it once again, <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
it should not take long, most files are on disc.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I've just added a few histograms to lumi_mon (there is a pool request), <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
please use this updated version.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'll take a look on some of these job crashes later<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Sasha<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Alexander Austregesilo <aaustreg@jlab.org><br>
<b>Sent:</b> Tuesday, December 8, 2020 9:21 AM<br>
<b>To:</b> Alexander Somov <somov@jlab.org>; Drew Smith <andrew.p.smith@duke.edu>; Igal Jaegle <ijaegle@jlab.org><br>
<b>Cc:</b> primexd@jlab.org <primexd@jlab.org><br>
<b>Subject:</b> Monitoring Launch 2019-01 ver14: PrimeX</font>
<div> </div>
</div>
<div>
<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="x_branch-details x_css-truncate x_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="x_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="x_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="x_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="x_moz-txt-slash"><span class="x_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="x_moz-txt-slash"><span class="x_moz-txt-tag">/</span>cache/halld/offline_monitoring/RunPeriod-2019-01/ver14/REST<span class="x_moz-txt-tag">/</span></i></p>
<p><span class="x_moz-txt-slash"><span class="x_moz-txt-tag">We still observed about 20 crashes in the
</span></span><span class="x_moz-txt-slash"><span class="x_moz-txt-tag">launch. Please find a list of the problematic log files below.</span></span><span class="x_moz-txt-slash"><span class="x_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="x_moz-txt-slash"><span class="x_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>
</div>
</body>
</html>