Data Flow Description

Joined work of:

RDO Structure

Bytestream conversion is triggered on demand: A client opens the TgcRdo container in the data store and asks for a particular collection by key. If the key is not in the store, the store is programmed to activate the registered converter for that type of data (this is true for everything in the store, not just RDO). The registered converter then tries to fill the store with the requested data. In the RDO case, the stored converter activates the Bytestream converter. So the only way to see BS conversion in action is to write an algorithm that specifically asks for the data.

TgcRdo is a DataVector of TgcRawData. TgcRawData is basically a simple object which has a few different constructors, one for each bytestream fragment id and it usually assings the values given in the arguments into members.

A creation of a TgcRdo has the following flow:

-- RazAlon - 10 Dec 2007

PRD Structure

PRD (Prepared Raw Data), Also referred as RIO (Reconstruction Input Object), is an object built out of RDO. It contains a hit segments data using the global coordinate system .

The manipulation of PRD is defined by several classes and packages. (I STILL HAVE TO FIND WHO CREATES AND WHO USES PRD)

  • TrkPrepRawData - The package that defines the PrepRawData base class. The implemetation of the abstract classes is done in InDetPrepRawData and MuonPrepRawData.
    • Trk::PrepRawData - This is the base class. It contains the following members:
      • clusId - This is a 32 bit identifier of cluster that produced this PRD (strip, tube etc.). (NEED TO FIND OUT WHAT VALUES THIS IDENTIFIER TAKES AND HOW THEY ARE DETERMINED)
      • locpos - This is the local position of the measurment in the local coordinate system of the detector - This is still not the global coordinate system. This is of type Local Position
      • rdoList - This is a list (vector) of identifiers (32 bit) that procduces the PRD.
      • locerr - The errors in the measurments. Can be null. Of type ErrorMatrix.
  • MuonPrepRawData - A package that provides Muon spectrometer specific implementations of the common Trk::PrepRawData. It contains Muon::CscPrepData, Muon::RpcPrepData and Muon::TgcPrepData. All of them are derived from Muon::MuonCluster.
    • Muon::MuonCluster - This class represents a cluster in the Muon spectrometer. It is derived from TrkPrepRawData. It has the following members:
      • RODId - A 32 bit identifier of the central measurment of the cluster.
      • CollectionHash - The hash associated with the PRD collection is the storegate.
      • locpos - The position of the cluster in the detector loacal coordinate system. The first coordinate is the precision (???) coordinate, the second is set to the center of the strip.
      • rdoList - List of channels associated with the cluster.
      • locErrMat - The measurement errors.
    • Muon::TgcPrepData - This class derives from Muon::MuonCluster. In addition to the base class members it also has another member:
      • detEl - This is of type MuonGM::TgcReadoutElement. This is a pointer of the Detector Element on which the measurement was done. This object is part of the GeoModel and it is used to find the coordinates in the global coordinate system. (I THINK IT HAS NO OTHER USES BESIDE IT)
      • Global Position - Of type Trk::GlobalPosition. It is calculated from detEl and locpos.

The package MuonRdoToPrepData Transforms RDO into PRD. It has the four classes: CscRdoToCscPrepData, MdtRdoToMdtPrepData, RpcRdoToRpcPrepData and TgcRdoToTgcPrepData.

-- OhadSilbert - 06 Dec 2007

ESD/AOD Data

I found the following image. This was taken from an old talk given by AmirFarbin DataFlowESDAOD.jpg

Basically, The reconstruction produces ESD files with containers that associate the hit clusters in the detectors to particle track. The ESD size is ~500k/event.
The AOD is produced out of the ESD by an AOD builder. The AOD builder rearrange the particles in "physical" containers such as electrons, muons, taujet etc, and trim unrelevant information on the detector itself. There is a way to go back from the AOD to the ESD to find more information about each element. The AOD size is ~100k/event.
Ther Event Tag consist only a small fraction of event data, in order to classify the events according to important final state particles. It is build out of the AOD (In this diagram it doesn't look like this, but all the refferences I found showed that the data is coming from the AOD) and its size is ~1k/event.
ling to AOD and ESD keys

-- OhadSilbert - 02 Dec 2007

Open issues

-- OhadSilbert - 06 Dec 2007

Topic attachments
I Attachment History Action Size Date Who Comment
JPEGjpg DataFlowESDAOD.jpg r1 manage 157.1 K 2007-11-21 - 15:46 OhadSilbert data flow diagram for analysis
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r13 - 2007-12-10 - RazAlon
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback