<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Folks,<br>
<br>
Please find the minutes below and at<br>
<br>
<a class="moz-txt-link-freetext" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_March_4,_2015#Minutes">https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_March_4,_2015#Minutes</a>
.<br>
<br>
-- Mark<br>
______________________________<br>
<div id="globalWrapper">
<div id="column-content">
<div id="content" class="mw-body" role="main"> <br>
<span dir="auto">GlueX Offline Meeting, March 4, 2015</span><span
class="mw-headline" id="Minutes">, Minutes</span><br>
<div id="bodyContent" class="mw-body-content">
<div id="mw-content-text" dir="ltr" class="mw-content-ltr"
lang="en">
<br>
Present:
<br>
<ul>
<li> <b>CMU</b>: Curtis Meyer</li>
<li> <b>FIU</b> Mahmoud Kamel</li>
<li> <b>JLab</b>: Mark Ito (chair), David Lawrence,
Paul Mattione, Paul Mattione, Kei Moriya, Eric Pooser,
Nathan Sparks, Justin Stevens, Simon Taylor</li>
<li> <b>MEPhI</b>: Dmitry Romanov</li>
<li> <b>NU</b>: Sean Dobbs</li>
</ul>
<br>
<span class="mw-headline" id="Announcements">Announcements</span><br>
<ul>
<li> <b>FADC125 upsampling algorithm implemented in
emulation mode</b>. David led us through two recent
emails to the group (see below). Now FADC time and
charge information can be chosen between (a) firmware
supplied and (b) emulated quantities. There was also a
change in how pedestal information is reported; an
average is now reported.
<ul>
<li> <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-February/001954.html">message
1 of 2</a></li>
<li> <a rel="nofollow" class="external text"
href="https://mailman.jlab.org/pipermail/halld-offline/2015-February/001955.html">message
2 of 2</a></li>
</ul>
</li>
<li> <b>CentOS 6.5 added to b1pi test</b>.</li>
<li> <b>Code analysis</b>. David reported that Mike
Staib has been using some Intel-provided tools to
analyze our reconstruction code. Mike found a race
condition in the CCDB package that has been causing
crashes when running multi-threaded. This has been
reported to Dmitry and he is working on a fix. The
High-Performance Computing group at JLab has a license
for this software (although Mike did not access the
tool using that license). We will ask Mike to document
his experience with the package so others can try it
out.</li>
<li> <b>Why we upgraded</b>. Mark commented on the
schedule for our recent upgrade of the web and
database servers. The idea was to wait until after the
collaboration meeting, but also to switch as far in
advance of the Spring run as possible. That put things
at the Monday before last.</li>
</ul>
<br>
<span class="mw-headline"
id="Review_of_minutes_from_February_4">Review of minutes
from February 4</span><br>
<br>
We looked at the <a
href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_February_4,_2015#Minutes"
title="GlueX Offline Meeting, February 4, 2015">minutes</a>.
<br>
Dmitry has been working on the <b>Run Control Database
(RCDB)</b>. He is importing information from Sean's data
monitoring database and refreshing information from
re-parsed CODA log files. This work is on-going. He has
also released <a
href="https://halldweb.jlab.org/wiki/index.php/RCDB_conditions_python"
title="RCDB conditions python">documentation</a> for the
system.
<br>
<br>
<span class="mw-headline" id="Offline_Monitoring_Report">Offline
Monitoring Report</span><br>
<br>
Kei described the most recent launch of the offline
monitoring jobs. Please see his [Media:2015-03-04-offline
monitoring.pdf|slides] for details. Some take-aways:
<br>
<ul>
<li> difference in CPU time compared to last time: CPU
time much higher compared to wall time</li>
<li> version 10 vs. version 09 shows good correlation of
CPU times</li>
<li> version 11 has much lower CPU time than version 10
(David thought this might be due to improvements in
CDC plug-in efficiency).</li>
</ul>
<br>
<span class="mw-headline"
id="Commissioning-branch-to-trunk_migration">Commissioning-branch-to-trunk
migration</span><br>
<br>
Justin discovered the cause of the failure of the
commissioning branch to successfully reconstruct simulated
data: a default of zero B-field. Assigning a run number
taken during commissioning in bggen solved the problem;
the CCDB will then respond with the correct field map.
<br>
This led to a discussion of how we should handle the
calibration constants for simulated data. There are two
cases:
<br>
<ol>
<li> simulations intended to mimic conditions of
already-taken real data</li>
<li> simulations to explore conditions beyond those
already achieved</li>
</ol>
<br>
At present there are two degrees of freedom that we have
to play with: run number and CCDB variation. Ideas
discussed included, but were not limited to:
<br>
<ul>
<li> negative number numbers (i. e.
(-1)*real-run-number)</li>
<li> run numbers greater than 10<sup>6</sup> designated
as simulation</li>
<li> run-period specific reserved run numbers (run
ranges designated as simulation only, data taking
would then avoid these run numbers, run keep-out zones
in correspondence to run periods)</li>
<li> run numbers with year encoded in the higher-order
digits</li>
</ul>
<br>
In the end we formed a consensus on the following scheme
for the two cases:
<br>
<ol>
<li> "mc" variation of CCDB: run numbers indicate the
real-data run numbers that are being simulated. This
variation already exists.</li>
<li> user-named variations in CCDB: run numbers have a
user-defined meaning, variation name reflecting
speculative conditions being explored, e. g.,
"high-intensity", "upgrade-study-5".</li>
</ol>
<br>
<span class="mw-headline" id="EM_background_mix-ins">EM
background mix-ins</span><br>
<br>
We agreed to emphasize the importance of having a random
trigger for study and/or inclusion of electromagnetic
background.
<br>
<br>
<span class="mw-headline" id="mcsmear_execution_time">mcsmear
execution time</span><br>
<br>
David did some measurements and found that the BCAL
simulation is using most of the CPU time in mcsmear. This
is due to the detailed simulation of hits implemented when
studying different segmentation schemes in for BCAL
read-out. For other studies we should be able to get away
with a less detailed but less CPU-intensive approach.
<br>
</div>
<div class="printfooter">
Retrieved from "<a dir="ltr"
href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_March_4,_2015&oldid=64000">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_March_4,_2015&oldid=64000</a>"</div>
</div>
</div>
</div>
<div id="footer" role="contentinfo">
<ul id="f-list">
<li id="lastmod"> This page was last modified on 5 March 2015,
at 13:36.</li>
</ul>
</div>
</div>
<br>
</body>
</html>