There are a number of data file types that we are using to store detector data, either real or MC generated. This page serves as a guide to those.
E906 SRawEvent
- Simple tree format that contains all hit information.
- The structure is defined in the E906 version of kTracker.
- One ROOT file had been created per E906 run.
File name example: digit_023431_009.root
E1039 SRawEvent
- Essentially the same as E906, with a few variable name changes.
The structure is defined in `
e1039-core/packages/reco/interface` .- One ROOT file is being created per spill (not run) by the E1039 Main-DAQ decoder.
File name example: run_004500_spill_000000001_sraw.root
E1039 DST
- Complex tree structure with specially defined classes for variables. Not readable except with Fun4All framework.
- The structure is defined in `e1039-core/interface_main`.
- One ROOT file is being created per run and also per 100 spills by the E1039 Main-DAQ decoder.
File name example: DST.root
E1039 Monte Carlo Output
Output of Fun4All MC generation of events. Includes MC truth for tracks, and both detectorID and elementID as well as individual elements for each detector.
Does not include TDC time of events.
File name example: track_QA_v2.ROOT
Notes: This file is not the primary output file. This file (and several others) is derived from the DST (primary output) using converter code which essentially is C++ content that load the library and output a light root file based on demand. If you need special or additional variables, let me know (za2hd@virginia.edu) and I will make the code.
