Difference between revisions of "LBNE Far Detector Software Data Model"

From DUNE
Jump to navigation Jump to search
Line 113: Line 113:
 
|-
 
|-
 
| gaushit  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_gaushitfinder], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl gaus_hitfinder] || caldata || Hit
 
| gaushit  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_gaushitfinder], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl gaus_hitfinder] || caldata || Hit
 +
|-
 +
| fasthit  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_fasthitfinder], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl standard_fasthitfinder] || caldata || Hit
 +
|-
 +
| hitcheat || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_hitcheater], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl standard_hitcheater]  || caldata, largeant|| Hit
 
|-
 
|-
 
| hit35t  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_hitfinder35t] || gaushit || Hit
 
| hit35t  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_hitfinder35t] || gaushit || Hit
 
|-
 
|-
| fasthit  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_fasthitfinder], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl standard_fasthitfinder] || caldata || Hit
+
| fasthitdc || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_disambigcheat], [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl standard_disambigcheat] || fasthit || Hit
 
|-
 
|-
| fasthitdc || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_disambigcheat], [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl standard_disambigcheat] || gaushit || Hit
+
| dcheat  || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_disambigcheat], [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl standard_disambigcheat] || gaushit || Hit
 
|-
 
|-
| hitcheat || [https://cdcvs.fnal.gov/redmine/projects/lbnecode/repository/revisions/master/entry/lbne/HitFinderLBNE/hitfindermodules_lbne.fcl lbne35t_hitcheater], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/HitFinder/hitfindermodules.fcl standard_hitcheater] || || Hit
+
| dbcluster || [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/ClusterFinder/cluster_lbne.fcl lbne35t_dbcluster], [https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/master/entry/ClusterFinder/clustermodules.fcl standard_dbcluster] || hit35t || Cluster
| hit35t
 
 
|}
 
|}

Revision as of 15:26, 22 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

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

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 Reconstructed particle? Association to cluster, space point, track, seed, vertex.
Seed lardata/RecoBase Space point with direction. Used by Pandora.
Vertex lardata/RecoBase Vertex position. Association with PFParticle. Used by Pandora.

Plans to update the reconstruction model are described in a talk by Gianluca.

Code browsing

DUNE
Repository
lbnecode Redmine git
LArSoft
Repository
larsoft Redmine LXR
larcore Redmine LXR
lardata Redmine LXR
larevt Redmine LXR
larsim Redmine LXR
larreco Redmine LXR
larana Redmine LXR
...
Supporting products
Repository
art Redmine LXR
nutools Redmine

For more LArSoft links, see the LArSoft core installation page.

Monte Carlo Production for 35 ton

This section is under construction.

The above data model is used for the MC (Monte Carlo) samples produced for the 35-ton prototype detector. Five different reconstruction paths are followed: standard reconstruction without use of MC, with full cheat that makes extensive use of MC information and half-cheat that uses MC only to resolve TPC ambiguities. In addition, Pandora is run in standard and half-cheat modes. The following table lists the names of the producers for these reconstruction paths and the types of data products they produce. The name and type can be used to retrieve each data product.

Reconstruction chains
Path Wire Hit Cluster Track SpacePoint Calorimetry(?)
Standard (no cheat) caldata gaushit, hit35t fuzzy (kalmanhit)
Standard (no cheat) gaushit, hit35t dbcluster costrk, stitch costrk, stitch calo
Standard full cheat hitcheat clustercheat trackcheat
Standard half cheat dcheat fuzzydc
Standard half cheat dcheat dbclusterdc costrkdc, stitchdc costrkdc, stitchdc calodc
Another half cheat? fasthit, fasthitdc
Reconstruction producers
Nickname Full name(s) Inputs Output types
Reco Reco All below
caldata lbne35t_calwire daq (RawDigits) Wire
gaushit lbne35t_gaushitfinder, gaus_hitfinder caldata Hit
fasthit lbne35t_fasthitfinder, standard_fasthitfinder caldata Hit
hitcheat lbne35t_hitcheater, standard_hitcheater caldata, largeant Hit
hit35t lbne35t_hitfinder35t gaushit Hit
fasthitdc lbne35t_disambigcheat, standard_disambigcheat fasthit Hit
dcheat lbne35t_disambigcheat, standard_disambigcheat gaushit Hit
dbcluster lbne35t_dbcluster, standard_dbcluster hit35t Cluster