Transient Data Store and Persistent Data

Size: px

Start display at page:

Download "Transient Data Store and Persistent Data"

Archibald Stevens
5 years ago
Views:

1 Transient Data Store and Persistent Data Current Status and Discussion of possible future plans Software Workshop, 13 Nov 2001, H. Kelly, 1

2 Introduction and food for thought As we go over the current status please keep in mind that there are 2 separate issues: The general structure of the data: Transient Data Store Persistent form The file format used to store the data. Software Workshop, 13 Nov 2001, H. Kelly, 2

Transient Data Store (TDS) Shared memory mechanism http://www-glast.slac.stanford.

3 Transient Data Store (TDS) Shared memory mechanism Software Workshop, 13 Nov 2001, H. Kelly, 3

4 /Event TDS Organization Event header: run, event id, time /Event/MC Monte Carlo data List of MC particles and List of MC vertices Energy accounting /Event/Digi /TkrDigi List of layers and their list of hit strips and ToTs /CalDigi List of logs and their ADC values for each range /AcdDigi List of tiles and their PHAs Software Workshop, 13 Nov 2001, H. Kelly, 4

5 TDS contd. /Event/Recon summery recon data /Event/TkrRecon /Event/CalRecon /TkrClusters List of silicon clusters /SiRecObjs List of tracks and gamma data /CsIClustersList List of CAL clusters /CalRecLogs List of logs and recon data /Event/AcdRecon not yet in use Software Workshop, 13 Nov 2001, H. Kelly, 5

6 TDS: To Do Review the current contents of the TDS Many of the current classes are based on old code. Design the general structure for all classes Algorithms may be in flux but we can have some idea as to what the output should look like. Use standard naming conventions Use namespaces to prevent naming conflicts Software Workshop, 13 Nov 2001, H. Kelly, 6

7 Raw/Digi ROOT files Software Workshop, 13 Nov 2001, H. Kelly, 7 Current Persistent Data In use for the 1999 BTEM and 2001 BFEM Not yet available for full-instrument simulation Recon ROOT files ROOT summary ntuples Similar to the AO ASCII ntuples where each event record consists of a fixed length set of floats. Monte Carlo ROOT classes are also available In use for 2001 BFEM Not yet available for full-instrument simulation

8 Reading/Writing Persistent Data The summary ntuple is handled by a Gaudi service called ntuplewritersvc. We do not use the Gaudi Persistency Service. Why? Gaudi s interface to ROOT does not write out proper ROOT files. Algorithms read in the digi and write out the recon data into ROOT files. We plan to start using proper Gaudi converters after the PDR. Software Workshop, 13 Nov 2001, H. Kelly, 8

9 Software Workshop, 13 Nov 2001, H. Kelly, 9 ntuplewritersvc Handles Row-Wise Ntuple (RWN) creation. Use requires: tag name of an ntuple item corresponding value output file id Possible Changes: Allow Column-Wise Ntuples (CWN) store more complex entities: arrays, matrices.. This is a minor modification, implementation time 30 minutes including testing.

digirootdata http://www-glast.slac.stanford.edu/software/root/digirootdata Event Id and Run Number List of TKR layers List of hit SSDs Two ToT values, one for each controller for each layer.

10 digirootdata Event Id and Run Number List of TKR layers List of hit SSDs Two ToT values, one for each controller for each layer. List of CAL logs Each log has an associated Id. List of ACD (XGT) tiles Each tile has an associated Id. Level One Trigger data Live Time Counter data Software Workshop, 13 Nov 2001, H. Kelly, 10 Suggested updates: ACD needs to handle 2 phototubes L1T class could use an overhaul Review the rest

reconrootdata http://www-glast.slac.stanford.

11 reconrootdata Event Id and Run Number TkrRecon object TkrGamma object List of SSD hits List of locators List of tracks found by the reconstruction List of SSD hits associated with the track List of locators List of Silicon Clusters CalRecon object List of Logs, with their reconstructed responses List of CAL clusters List of logs associated with this cluster. Software Workshop, 13 Nov 2001, H. Kelly, 11 The whole recon output structure needs an overhaul possible parallel session?

12 Needs some work Software Workshop, 13 Nov 2001, H. Kelly, 12 mcrootdata Currently, there are 3 classes defined: RMcEvent, RMcVertex, RMcParticle The main class RMcEvent represents the MC data for one event. Currently contains a list of vertices and each vertex contains a list of particles. The version in use for the balloon Contains a list of particles, which contains a list of vertices.

13 Persistency Service Future development depends upon the file format(s) we decide to utilize. No matter what file format(s) are chosen, some basic functionality is required: Gaudi I/O service(s) that provide an interface to the I/O library necessary. Gaudi converters that will handle reading data in from its persistent form, storing that data on the TDS as well as taking data off the TDS and writing that data out in some persistent format. Software Workshop, 13 Nov 2001, H. Kelly, 13

14 ROOT Persistency Service Athena has produced a real ROOT service. - ROOT I/O - ROOT interactive session by demand - ROOT share library dynamic loading by demand - ROOT control over the Gaudi algorithms They are planning to develop own data store. Will we be able to benefit from future development? Should we just take what they have and run? Do we use their code as a model and run? Discuss within a parallel session? Software Workshop, 13 Nov 2001, H. Kelly, 14

The GLAST Event Reconstruction: What s in it for DC-1?

The GLAST Event Reconstruction: What s in it for DC-1? Digitization Algorithms Calorimeter Reconstruction Tracker Reconstruction ACD Reconstruction Plans GLAST Ground Software Workshop Tuesday, July 15,