Difference between revisions of "LBNE Far Detector Software Data Model"
DavidAdams (talk | contribs) |
DavidAdams (talk | contribs) |
||
Line 1: | Line 1: | ||
This page documents D. Adams attempts to understand the LBNE EDM (event data model), i.e. the classes describing the data share by modules via the event data store and written to event data files. | This page documents D. Adams attempts to understand the LBNE EDM (event data model), i.e. the classes describing the data share by modules via the event data store and written to event data files. | ||
− | == Simulation == | + | == Simulation data products == |
The following table lists the EDM classes used in the simulation. | The following table lists the EDM classes used in the simulation. | ||
{| class="wikitable" style="text-align:left;" | {| class="wikitable" style="text-align:left;" | ||
Line 13: | Line 13: | ||
|} | |} | ||
− | == Reconstruction == | + | == Reconstruction data products == |
The following table lists the EDM classes used in the reconstruction. | The following table lists the EDM classes used in the reconstruction. | ||
Line 41: | Line 41: | ||
[[LBNE_code_repositories | LBNE code repositories and their browsers]] | [[LBNE_code_repositories | LBNE code repositories and their browsers]] | ||
− | == Monte Carlo | + | == Reconstruction of Monte Carlo for the LBNE 35 ton prototype == |
The above data model is used for the MC (Monte Carlo) samples produced for the 35-ton prototype detector. Six different reconstruction paths are followed: standard reconstruction without use of MC, with full cheat that makes extensive use of MC information, cheat using MC only to resolve TPC ambiguities, and fast hit finding. In addition, Pandora is run in standard and disambiguation cheat modes. | The above data model is used for the MC (Monte Carlo) samples produced for the 35-ton prototype detector. Six different reconstruction paths are followed: standard reconstruction without use of MC, with full cheat that makes extensive use of MC information, cheat using MC only to resolve TPC ambiguities, and fast hit finding. In addition, Pandora is run in standard and disambiguation cheat modes. |
Revision as of 14:28, 23 April 2015
This page documents D. Adams attempts to understand the LBNE EDM (event data model), i.e. the classes describing the data share by modules via the event data store and written to event data files.
Simulation data products
The following table lists the EDM classes used in the simulation.
Class | Location | Description |
---|---|---|
MCTruth | nutools/SimulationBase | ID, PDG ID, status code and starting and ending position and momentum for each input MC particle |
MCParticle | nutools/SimulationBase | ID, PDG ID, status code and starting and ending positions and momenta for each MC particle |
SimChannel | larsim/Simulation | Energy deposited by each MC particle in the volume for each readout channel |
Reconstruction data products
The following table lists the EDM classes used in the reconstruction.
Class | Location | Description |
---|---|---|
RawDigit | lardata/RawData | Raw (convoluted) ADC signals in time slices. Unpack with raw::Decompress in RawData/raw.h |
Wire | lardata/RecoBase | Deconvoluted signal for each channel. |
Hit | lardata/RecoBase | Peaks on wire signals. |
Cluster | lardata/RecoBase | Associated hits in a TPC plane, i.e. 2D tracks. Association to hit. |
SpacePoint | lardata/RecoBase | Space point formed by combining hits from different planes. Association to hit. |
Track | lardata/RecoBase | Trajectory with momentum. Association to space point, hit, cluster |
PFParticle | lardata/RecoBase | Particle-flow description of a particle. Used by Pandora. |
Vertex | lardata/RecoBase | Vertex position. Association with PFParticle. Used by Pandora. |
Calorimetry | lardata/AnalysisBase | Vertex position. Association with PFParticle. Used by Pandora. |
Plans to update the reconstruction model are described in a talk by Gianluca.
LBNE code repositories and their browsers
Reconstruction of Monte Carlo for the LBNE 35 ton prototype
The above data model is used for the MC (Monte Carlo) samples produced for the 35-ton prototype detector. Six different reconstruction paths are followed: standard reconstruction without use of MC, with full cheat that makes extensive use of MC information, cheat using MC only to resolve TPC ambiguities, and fast hit finding. In addition, Pandora is run in standard and disambiguation cheat modes.
The following tables list the reconstruction paths and the types of data products they produce. The name and type can be used to retrieve each data product. The entries in all but the first row are the instance names of producer modules. Details for these are given in the table at the end of this section.
Path | Wire | Hit | Cluster | Track | SpacePoint | Calorimetry(?) |
---|---|---|---|---|---|---|
Standard (no cheat) | caldata | gaushit, hit35t | dbcluster | costrk, stitch | costrk, stitch | calo |
Standard full cheat | caldata | hitcheat | clustercheat | trackcheat | ||
Standard with disambiguation cheat | caldata | gaushit, dcheat | dbclusterdc | costrkdc, stitchdc | costrkdc, stitchdc | calodc |
Fast hit finding plus disambiguation cheat | caldata | fasthit, fasthitdc |
Path | Wire | Hit | Cluster, See, SpacePoint, PFParticle, Vertex | PFParticle |
---|---|---|---|---|
No cheat | caldata | gaushit, hit35t | pandora | particlestitcher |
Disambiguation cheat | caldata | gaushit, dcheat | pandoradc | particlestitcherdc |
The next table lists all the producer instances. The first row is the process and the second column provides a link to the top-level fcl file where most of the producer instance names are assigned. The second column gives the names used in lower-level fcl files along with links to those files. The third column gives the names of the producers for the input data. The fourth provides the names of the output data types along with links to the class headers. The last column is the producer class name with a link to its source code.
The producer instance names and mapping to output types were obtained from a data file from the second round of MC production for 35-ton running. The low-level producer names and links between input and output producer names were obtained by (tediously) searching fcl files in the develop branches of larsoft and lbnecode April 21-22 2015.