Go to Home Page
CHEP INFORMATION
Bulletins
Committees
Scientific Program
Docs by topics
Social events
Conference location
Secretariat
GRID INFORMATION
 • Grid WShop & Tutorial
 • Grid Program
USEFUL LINKS
 • Visiting Padova
 • INFN Padova
 • University of Padova
 • CHEP: '94 '95 '97 '98

Last update: Apr 1, 2000

to first abs  to previous absby abs number to next abs  to last abs

  

to first abs on this KT  to previous abs on this KTon same keytopic to next abs on this KT  to last abs on this KT


C201

The CDF Run II Event Data Model
Robert Kennedy1, Dan Amidei2, Liz Buckley-Geer1, Paolo Calafiura3, Chris Green4, Todd Huffman5, Jim Kowalkowski1, Al Lee6, Kevin McFarland7, Pasha Murat1, Simona Rolli8, Liz Sexton-Kennedy1, Marge Shapiro3, Prem Singh9, Rick Snider1, Peter Tamburello6
  1. Fermilab
  2. University of Michigan
  3. Lawrence Berkeley National Laboratory
  4. Purdue University
  5. Oxford University
  6. Duke University
  7. Rockefeller University
  8. TUFTS University
  9. University of Illinois

Speaker: Robert Kennedy

  The CDF Event Data Model describes how CDF C++ and F77 software may access event data in CDF Offline software. The CDF Event Data Model Working Group has reviewed the Run I Event Data Model which was based on YBOS data banks stored in a global array. While this model was successful for Run I analyses, it did not take advantage of the Object-Oriented design of the CDF Run II Offline software.
   In this paper, we describe the CDF Run II Event Data Model. Event data is passed via an EventRecord amongst user-written software modules whose execution is coordinated by the AC++/Framework package. C++ classes meeting a few criteria can have instances stored in the EventRecord. Objects in the EventRecord are assigned a unique identifier and become write-locked, key changes in behavior from the old model. Support for storable links, collections, YBOS banks, and data access by Fortran software are accommodated. The ROOT Object I/O system is used to read/write the EventRecord to diskfiles. This model has simplified the effort to make event data persistent, without requiring an overwhelming effort to retrofit our large, existing code base written to the old event data model.

Presentation:  Adobe Acrobat pdf Short Paper:  Adobe Acrobat pdf 
  | Top | Home | Bulletins | Committees | Scientific Program | Docs by topics | Social Event | Conference Location | Secretariat | Privacy Policy |