Difference between revisions of "GlueX Offline Meeting, February 22, 2012"
(→Reconstruction Output Format: all) |
(→EventStore) |
||
Line 79: | Line 79: | ||
==[https://mailman.jlab.org/pipermail/halld-offline/2012-February/000859.html EventStore]== | ==[https://mailman.jlab.org/pipermail/halld-offline/2012-February/000859.html EventStore]== | ||
+ | Matt declined to describe the EventStore system, stating that everything that needed to be said was in the email he sent out. As such we dove directly into discussion. | ||
− | + | skims without duplication of events | |
+ | versioning of reconstruction code | ||
+ | hooks for skimming events based on various criteria | ||
+ | possibility for alternate reconstruction algorithm on previously reconstructed data | ||
+ | |||
+ | do we want to pursue? at what priority? | ||
+ | |||
+ | Matt knows the developers | ||
+ | Many users over a number of years | ||
+ | Good pedigree | ||
+ | |||
+ | Questions: | ||
+ | |||
+ | how portable is the code base? | ||
+ | how easy to add new (our) event formats to the system? random access scheme in particular | ||
+ | how much disk space is required to use effectively? | ||
+ | when do we need this functionality? | ||
random access needs to be explored | random access needs to be explored | ||
10's of TB level at cleo-c | 10's of TB level at cleo-c | ||
access to large amount of disk space | access to large amount of disk space |
Revision as of 18:44, 22 February 2012
GlueX Offline Software Meeting
Wednesday, February 22, 2012
1:30 pm EST
JLab: CEBAF Center F326
Contents
Agenda
- Announcements
- Single-track jobs running: Simon, Mark
- Review of minutes from the last meeting: all
- Reconstruction sub-group reports
- Calorimeters
- Tracking
- PID
- Offline Software Review Planning
- Reconstruction Output Format: all
- EventStore
- Action Item Review
- Review of recent repository activity: all
Communication Information
Video Conferencing
- ESNet: 8542553
- EVO:
- Meeting URL: http://evo.caltech.edu/evoNext/koala.jnlp?meeting=ete8eavBvvanaaIiaiIt
- Phone Bridge ID: 11 6471
Slides
Talks can be deposited in the directory /group/halld/www/halldweb1/html/talks/2012-1Q
on the JLab CUE. This directory is accessible from the web at https://halldweb1.jlab.org/talks/2012-1Q/ .
Minutes
Present:
- CMU: Will Levine, Curtis Meyer
- FSU: Nathan Sparks
- IU: Ryan Mitchell, Kei Moriya, Matt Shepherd
- JLab: Mark Ito (chair), Simon Taylor, Beni Zihlmann
Announcements
Simon and Mark reported that single-charged-track diagnostic jobs are now running nightly on an ifarm machine at JLab. The success probability is still a bit low (due to Computer Center controls of multiple jobs) and adjustments will have to be made, but some results can be seen at the top-level web page.
Review of minutes from the last meeting
We reviewed the minutes from the previous meeting, from before the collaboration meeting, without significant comment.
Reconstruction sub-group reports
Calorimeters
Will gave a summary of his work thus far characterizing photon reconstruction in events. See his wiki page for details and plots. He studied the BCAL and FCAL separately. In the BCAL he sees about a factor of three more photons reconstructed than thrown but a simple timing cut eliminates most of the spurious reconstructed photons, leaving the right number and a reasonable energy spectrum. In the FCAL there is a similar multiplication in photons from generated to reconstructed, but timing only removes half of the total (a larger factor is desired). Will is investigating these issues further.
Tracking
Simon told us about his recent change to the tracking code. Simple version [oversimple?]: FDC hits are no longer used by the CDC track factory.
Reconstruction Output Format
DST format, exists, starting point, uconn, default, collaboration support, at least this one
analysis should take place with object in DANA
high level objects, DST should have minimal info to allow re-creation, need not, should not 1 to 1 correspondence between DST tags and analysis objects. some computation may be required
focus on our design on the interfaces, re-work DST and lower level objects to support those interfaces.
design efforts have been separate, but no reason that these roles cannot be filled
some tweaking and iteration will be necessary
We talked about being able to make say ROOT trees from dst's Matt: root trees from data objects, DST's to provide data to create said objects
EventStore
Matt declined to describe the EventStore system, stating that everything that needed to be said was in the email he sent out. As such we dove directly into discussion.
skims without duplication of events versioning of reconstruction code hooks for skimming events based on various criteria possibility for alternate reconstruction algorithm on previously reconstructed data
do we want to pursue? at what priority?
Matt knows the developers Many users over a number of years Good pedigree
Questions:
how portable is the code base? how easy to add new (our) event formats to the system? random access scheme in particular how much disk space is required to use effectively? when do we need this functionality?
random access needs to be explored 10's of TB level at cleo-c access to large amount of disk space