<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 at
<a class="moz-txt-link-freetext" href="https://halldweb1.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_January_7,_2015#Minutes">https://halldweb1.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_January_7,_2015#Minutes</a>
and below.<br>
<br>
-- Mark<br>
___________________________________________<br>
<br>
<br>
GlueX Offline Meeting, January 7, 2015<br>
<span class="mw-headline" id="Minutes">Minutes</span><br>
<br>
Present:
<br>
<ul>
<li> <b>FIU</b>: Mahmoud Kamel
</li>
<li> <b>FSU</b>: Aristeidis Tsaris
</li>
<li> <b>JLab</b>: Mark Ito (chair), David Lawrence, Paul
Mattione, Kei Moriya, Nathan Sparks, Simon Taylor
</li>
<li> <b>NU</b>: Sean Dobbs
</li>
</ul>
<br>
<span class="mw-headline" id="Review_of_Minutes_from_December_10">Review
of Minutes from December 10</span><br>
<br>
We looked over the <a
href="https://halldweb1.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_December_10,_2014#Minutes"
title="GlueX Offline Meeting, December 10, 2014">minutes</a> of
the last meeting.
<br>
<ul>
<li> Kei is using the gxproj1 account for offline monitoring jobs
and Mark is using gxproj2 for Data Challenge 3 (DC3).
</li>
<li> Mark was able to get the stand-alone version of Dmitry's Run
Conditions Database (RCDB) running. He will circulate
instructions on how to do that. He will also approach the
Computer Center on installing it on halldweb1.
</li>
<li> Paul mentioned that he could not find documentation on the
version management system that Mark presented last time. Turns
out it does not exist yet. Paul suggested that the documentation
be featured in the "getting started" section of the wiki.
</li>
<li> Mark presented a <a
href="https://halldweb1.jlab.org/wiki/index.php/Offline_Software_Wiki_Re-organization"
title="Offline Software Wiki Re-organization">new version</a>
of the main "Offline Software" wiki page. It is still under
development.
</li>
</ul>
<br>
<span class="mw-headline"
id="DAQ_and_TTab_Plugins_Converted_into_Libraries">DAQ and TTab
Plugins Converted into Libraries</span><br>
<br>
David reviewed for us the <a
href="https://mailman.jlab.org/pipermail/halld-offline/2015-January/001904.html"
class="external text" rel="nofollow">email</a> he sent today. Now
it is no longer necessary to specify these plugins as JANA command
options.
<br>
<br>
<span class="mw-headline"
id="HDDM_Versions_and_Backward_Compatibility">HDDM Versions and
Backward Compatibility</span><br>
<br>
We reviewed <a
href="https://mailman.jlab.org/pipermail/halld-offline/2014-December/001900.html"
class="external text" rel="nofollow">principles</a> that Richard
proposed for future changes to REST format. The issue is
preservation of backward compatibility, being able to analyze old
REST data with new code. The scheme does the preservation at the
cost of complication in the element names for those that are changed
from the elements they replace. We did not decide if this approach
should be enshrined in policy, but will discuss it further in the
future.
<br>
<br>
<span class="mw-headline" id="Commissioning_Run_Review">Commissioning
Run Review</span><br>
<br>
We reviewed tasks and progress from the recent run.
<br>
<br>
<span class="mw-headline" id="Offline_Monitoring_Report">Offline
Monitoring Report</span><br>
<br>
Kei presented <a
href="https://halldweb1.jlab.org/wiki/images/8/87/2015-01-07-weeklyruns.pdf"
class="external text" rel="nofollow">issues</a> from the offline
monitoring reconstruction jobs during the run. The slides:
<br>
<ul>
<li> Offline Monitoring Summary
</li>
<li> Disk Usage For Each Week
</li>
<li> 2-track Skim Output
</li>
<li> Number of Files Processed
</li>
<li> EVIO Statistics
</li>
<li> Errors found:
<ul>
<li> DAQ plugin
</li>
<li> Too Many FDC Hits
</li>
<li> Insufficient Buffer Space
</li>
<li> Bad Alloc
</li>
<li> Mismatch in Trigger Bank
</li>
<li> Crash
</li>
<li> Unknown Module Type
</li>
<li> F1TDC Block Header
</li>
<li> JEventSource_EVIO::MergeObjLists
</li>
</ul>
</li>
<li> Looking Ahead
</li>
</ul>
<br>
<span class="mw-headline"
id="Commissioning_Branch-to-Trunk_Migration">Commissioning
Branch-to-Trunk Migration</span><br>
<br>
Most of the development that went on during the run was checked into
the commissioning branch. A lot (but not all) of this code now has
to be moved the trunk, in particular those changes that improve the
reconstruction in general. Simon has been managing the commissioning
branch and will look into doing this transfer.
<br>
<br>
<span class="mw-headline" id="REST_Data">REST Data</span><br>
<br>
There was interest during the run for REST-formatted data for
high-level analysis. Kei has already produced these files (see his
talk above). They can be found in
/volatile/halld/RunPeriod-2014-10/offline_monitoring/danarest/2014-12-19/REST
.
<br>
A lot of recent analysis has been based on raw data with corrections
done on raw or reconstructed quantities to get better results. At
present these corrections are not reflected in the REST data. In
order to make future production of REST data more useful we need to
move corrections and calibrations into the standard reconstruction.
<br>
Sean will coordinate production/update of calibration constants and
capture of correction algorithms through the Calibration Working
Group. The goal is to make a push for some substantial progress and
then to re-make the REST data set.
<br>
<br>
<span class="mw-headline" id="Trains">Trains</span><br>
<br>
Paul brought up the a private discussion we had on the email list on
"data reconstruction trains". The idea is to have a single set of
jobs do reconstruction on raw data and have several "cars" attached
to the jobs for specialized purposes. Each individual project would
then avoid having to fetch the data from tape and pay the CPU price
of reconstruction. However such an effort requires significant
coordination and management. We did not move to start designing a
system right away since (a) the need is only prospective at this
point and (b) a lot of the savings for high-level analysis can be
achieved with useful REST-formatted data.
<br>
<br>
<span class="mw-headline" id="Storage_of_Data_Taken_between_Runs">Storage
of Data Taken between Runs</span><br>
<br>
David pointed out that there will be cosmic and test running in the
coming months before the spring run and we need to decide where in
the tape directory hierarchy they should be stored. The consensus
was to simply create a new run period directory in parallel to
"RunPeriod-2014-10" (used to store data from the commissioning run
just ended), something like "RunPeriod-2015-01".
<br>
<div class="printfooter">
Retrieved from "<a
href="https://halldweb1.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_January_7,_2015">https://halldweb1.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_January_7,_2015</a>"</div>
<br>
<pre class="moz-signature" cols="72">--
Mark M. Ito, Jefferson Lab, <a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org">marki@jlab.org</a>, (757)269-5295</pre>
</body>
</html>