anatree.fcl
Go to the documentation of this file.
1 BEGIN_PROLOG
2 
3 
4 
5 standard_anatree_spyv3:
6 {
7  module_type: anatree
8 
9 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
10 # If it is missing, then the anatree module will look for all MCTruth data products
11 # in the event
12 
13 # GeneratorLabels: [ "generator" ]
14 
15 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
16 # products, which are made only by GENIE. Often a generator module label will have to
17 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
18 # information stored in the analysis tree. Omit this argument if you want anatree_module
19 # to look for all GTruth data products in the event.
20 
21 # GENIEGeneratorLabels: [ "generator" ]
22 
23  InstanceLabelCalo: "ECAL"
24  InstanceLabelMuID: "MuID"
25  GEANTLabel: "geant"
26  RawCaloHitLabel: "daqsipm"
27  RawMuIDHitLabel: "daqsipmmuid"
28  HitLabel: "hit"
29  CaloHitLabel: "sscalohit"
30  MuIDHitLabel: "sscalohitmuid"
31  TPCClusterLabel: "tpccluster"
32  TrackLabel: "track"
33  TrackTrajectoryLabel: "track"
34  VertexLabel: "vertex"
35  ClusterLabel: "calocluster"
36  MuIDClusterLabel: "caloclustermuid"
37  ECALAssnLabel: "trkecalassn"
38  VeeLabel: "veefinder1"
39 
40 # What to save? ==============================================
41 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
42 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
43 # (WriteMCCaloInfo && WriteMCinfo).
44 # Write momenta associated with MC trajectories only if the trajectory is also written
45  WriteMCinfo: true
46  WriteMCPTrajectory: false
47  WriteMCPTrajMomenta: false
48  WriteMCCaloInfo: true
49 # The origin of an MCParticle might be a short distance from the MCTrue interaction
50 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
51 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
52  MatchMCPtoVertDist: 0.001
53 
54 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
55 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
56 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
57  WriteHits: false
58  WriteTPCClusters: true
59  WriteTracks: true
60  WriteTrackTrajectories: false
61  WriteVertices: true
62  WriteVees: true
63 
64 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
65 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
66 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
67  WriteMuID: true
68  WriteCaloDigits: false
69  WriteCaloHits: true
70  WriteCaloClusters: true
71  WriteMatchedTracks: true
72 
73 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
74 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
75 # also needs WriteMCinfo.
76  IonizTruncate: 1.00
77  WriteCohInfo: false
78 }
79 
80 
81 
82 standard_anatree_spyv3_edep:
83 {
84  module_type: anatree
85 
86 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
87 # If it is missing, then the anatree module will look for all MCTruth data products
88 # in the event
89 
90 # GeneratorLabels: [ "generator" ]
91 
92 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
93 # products, which are made only by GENIE. Often a generator module label will have to
94 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
95 # information stored in the analysis tree. Omit this argument if you want anatree_module
96 # to look for all GTruth data products in the event.
97 
98 # GENIEGeneratorLabels: [ "generator" ]
99 
100  InstanceLabelCalo: "ECAL"
101  InstanceLabelMuID: "MuID"
102  GEANTLabel: "edepconvert"
103  RawCaloHitLabel: "daqsipm"
104  RawMuIDHitLabel: "daqsipmmuid"
105  HitLabel: "hit"
106  CaloHitLabel: "sscalohit"
107  MuIDHitLabel: "sscalohitmuid"
108  TPCClusterLabel: "tpccluster"
109  TrackLabel: "track"
110  TrackTrajectoryLabel: "track"
111  VertexLabel: "vertex"
112  ClusterLabel: "calocluster"
113  MuIDClusterLabel: "caloclustermuid"
114  ECALAssnLabel: "trkecalassn"
115  VeeLabel: "veefinder1"
116 
117 # What to save? ==============================================
118 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
119 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
120 # (WriteMCCaloInfo && WriteMCinfo).
121 # Write momenta associated with MC trajectories only if the trajectory is also written
122  WriteMCinfo: true
123  WriteMCPTrajectory: false
124  WriteMCPTrajMomenta: false
125  WriteMCCaloInfo: true
126 # The origin of an MCParticle might be a short distance from the MCTrue interaction
127 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
128 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
129  MatchMCPtoVertDist: 0.001
130 
131 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
132 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
133 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
134  WriteHits: false
135  WriteTPCClusters: true
136  WriteTracks: true
137  WriteTrackTrajectories: false
138  WriteVertices: true
139  WriteVees: true
140 
141 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
142 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
143 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
144  WriteMuID: true
145  WriteCaloDigits: false
146  WriteCaloHits: true
147  WriteCaloClusters: true
148  WriteMatchedTracks: true
149 
150 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
151 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
152 # also needs WriteMCinfo.
153  IonizTruncate: 1.00
154  WriteCohInfo: false
155 }
156 
157 
158 
159 standard_anatree_dayone:
160 {
161  module_type: anatree
162 
163 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
164 # If it is missing, then the anatree module will look for all MCTruth data products
165 # in the event
166 
167 # GeneratorLabels: [ "generator" ]
168 
169 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
170 # products, which are made only by GENIE. Often a generator module label will have to
171 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
172 # information stored in the analysis tree. Omit this argument if you want anatree_module
173 # to look for all GTruth data products in the event.
174 
175 # GENIEGeneratorLabels: [ "generator" ]
176 
177  InstanceLabelCalo: "TrackerSc"
178  InstanceLabelMuID: "MuID"
179  GEANTLabel: "geant"
180  RawCaloHitLabel: "daqsipm"
181  RawMuIDHitLabel: "daqsipmmuid"
182  HitLabel: "hit"
183  CaloHitLabel: "sscalohit"
184  MuIDHitLabel: "sscalohitmuid"
185  TPCClusterLabel: "dayone"
186  TrackLabel: "trackpass1"
187  TrackTrajectoryLabel: "trackpass1"
188  VertexLabel: "vertex"
189  ClusterLabel: "calocluster"
190  MuIDClusterLabel: "caloclustermuid"
191  ECALAssnLabel: "trkecalassn"
192  VeeLabel: "veefinder1"
193 
194 # What to save? ==============================================
195 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
196 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
197 # (WriteMCCaloInfo && WriteMCinfo).
198 # Write momenta associated with MC trajectories only if the trajectory is also written
199  WriteMCinfo: true
200  WriteMCPTrajectory: true
201  WriteMCPTrajMomenta: true
202  WriteMCCaloInfo: true
203 # The origin of an MCParticle might be a short distance from the MCTrue interaction
204 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
205 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
206  MatchMCPtoVertDist: 0.001
207 
208 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
209 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
210 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
211  WriteHits: false
212  WriteTPCClusters: true
213  WriteTracks: true
214  WriteTrackTrajectories: true
215  WriteVertices: false
216  WriteVees: false
217 
218 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
219 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
220 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
221  WriteMuID: true
222  WriteCaloDigits: false
223  WriteCaloHits: false
224  WriteCaloClusters: false
225  WriteMatchedTracks: false
226 
227 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
228 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
229 # also needs WriteMCinfo.
230  IonizTruncate: 1.00
231  WriteCohInfo: false
232 }
233 
234 
235 
236 standard_anatree_dayone_edep:
237 {
238  module_type: anatree
239 
240 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
241 # If it is missing, then the anatree module will look for all MCTruth data products
242 # in the event
243 
244 # GeneratorLabels: [ "generator" ]
245 
246 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
247 # products, which are made only by GENIE. Often a generator module label will have to
248 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
249 # information stored in the analysis tree. Omit this argument if you want anatree_module
250 # to look for all GTruth data products in the event.
251 
252 # GENIEGeneratorLabels: [ "generator" ]
253 
254  InstanceLabelCalo: "TrackerSc"
255  InstanceLabelMuID: "MuID"
256  GEANTLabel: "edepconvert"
257  RawCaloHitLabel: "daqsipm"
258  RawMuIDHitLabel: "daqsipmmuid"
259  HitLabel: "hit"
260  CaloHitLabel: "sscalohit"
261  MuIDHitLabel: "sscalohitmuid"
262  TPCClusterLabel: "dayone"
263  TrackLabel: "trackpass1"
264  TrackTrajectoryLabel: "trackpass1"
265  VertexLabel: "vertex"
266  ClusterLabel: "calocluster"
267  MuIDClusterLabel: "caloclustermuid"
268  ECALAssnLabel: "trkecalassn"
269  VeeLabel: "veefinder1"
270 
271 # What to save? ==============================================
272 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
273 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
274 # (WriteMCCaloInfo && WriteMCinfo).
275 # Write momenta associated with MC trajectories only if the trajectory is also written
276  WriteMCinfo: true
277  WriteMCPTrajectory: true
278  WriteMCPTrajMomenta: true
279  WriteMCCaloInfo: true
280 # The origin of an MCParticle might be a short distance from the MCTrue interaction
281 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
282 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
283  MatchMCPtoVertDist: 0.001
284 
285 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
286 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
287 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
288  WriteHits: false
289  WriteTPCClusters: true
290  WriteTracks: true
291  WriteTrackTrajectories: true
292  WriteVertices: false
293  WriteVees: false
294 
295 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
296 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
297 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
298  WriteMuID: true
299  WriteCaloDigits: false
300  WriteCaloHits: false
301  WriteCaloClusters: false
302  WriteMatchedTracks: false
303 
304 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
305 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
306 # also needs WriteMCinfo.
307  IonizTruncate: 1.00
308  WriteCohInfo: false
309 }
310 
311 
312 
313 END_PROLOG
Generated by   doxygen 1.8.11